All guides

RoboWrite MCP: Connect Your AI Assistant

Bring your brand context, SEO and GEO content plans, briefs, and saved drafts into your AI assistant. RoboWrite exposes these workflows through a hosted Model Context Protocol (MCP) server, with browser sign-in and workspace access checks.

MCP server URL

https://mcp.robowrite.ai/mcp

Connecting this URL adds MCP tools. Reusable workflow skills come from the installed RoboWrite plugin package.

Choose Your Setup

Use the hosted connection for tools today. A plugin adds workflow skills only when its package includes them and they are enabled. The public repository ships version 0.2.3, which points to the retired endpoint. Use the hosted setup below for a new connection. As of November 21, 2026, OpenAI is reviewing RoboWrite 0.3.4 for ChatGPT. Public installation from the ChatGPT directory is pending.

Already connected? Keep your existing RoboWrite entry. Running the MCPServers.org install command again can replace the sign-in settings in your Cursor, Claude Code or Codex project. If you already ran it, restore just the RoboWrite entry from your client’s example below. Then check which workspace is connected.

ClientConnection pathSkills and availability
Claude web / DesktopDirectory entry or custom remote connectorCheck whether the entry says Connector or Connector & skill.
Claude CodeProject MCP configuration and browser OAuthDirect MCP adds tools; installed plugin skills are separate.
CodexProject MCP configuration and OAuth loginSign in, then choose an eligible workspace in Codex chat.
ChatGPT webCustom MCP plugin, where permittedCustom connection is separate from public-directory approval and bundled skills.
CursorProject .cursor/mcp.jsonProject connection and packaged plugin have different acceptance results.
Grok BuildRemote HTTP server in the Grok CLIManual setup adds tools. Native sign-in and reconnect are under test.

What Can You Do With the RoboWrite MCP Server?

Use your existing brand voice and content strategy when preparing briefs, find previous work before starting again, and read saved Markdown drafts. When you ask for new content, RoboWrite runs the generation job in your workspace so you can return to its status and saved result later.

  • Find brands, briefs, content items, and previous jobs.
  • Plan content and prepare briefs with the selected brand.
  • Request drafts, follow their jobs, and read saved Markdown.
  • Review a held Content Kit before approving its draft.

Learn how Content Kits organize an article's evidence and requirements.

Not ready to connect a workspace? Start with our guide to setting up a ChatGPT or Claude project for blog writing, which also covers what a project still leaves to you.

Before You Connect

  1. Create a RoboWrite account or sign in to your existing account, then create or select a workspace. Return to this guide after setup, then connect or reconnect your assistant.
  2. Choose an AI client that supports remote MCP over Streamable HTTP and browser OAuth. Your client plan or workspace policy may control custom-server access.
  3. Use the full server URL above, including /mcp. Opening it as a web page does not install the connection.

Sign in through the browser when prompted and review the requested permissions before allowing access. Do not paste passwords, API keys, or access tokens into a chat. Before creating or generating content, check your workspace's plan, remaining allowance, and overage settings. Connecting an assistant does not establish generation eligibility or add an allowance. See current plans.

Using More Than One Workspace

When multi-workspace access is available in your connection, one clearly disclosed consent combines workspace discovery and content access across all eligible workspaces you belong to now or join later. Publication permission stays separate. Existing selected-workspace connections keep working with their original consent. If the organization tools are absent, the capability has not been enabled for that connection; repeated sign-in will not add them.

  1. Ask RoboWrite to list your workspaces with list_organizations and show your role and access with get_organization_access.
  2. Choose the intended workspace explicitly. The assistant uses switch_organization to verify it, then checks the account with that organization_id.
  3. Every later content call must carry the same workspace ID. Recover that workspace's brands, briefs and drafts before continuing; selections from another workspace do not carry over.

Pause pending writes while choosing a workspace. The access report shows consent and workspace eligibility separately from checks still required for reading, editing, generation and publication. It does not promise allowance or authorize an action. Switching does not change your browser's workspace or start content work or billing. Canceling a selection preserves your prior intent without taking action. Access is checked again on every action. A removed membership or an unverified workspace security policy can make a workspace unavailable; reconnect only for an expired token or missing consent. See the Public API guide for the versioned workspace endpoints.

ChatGPT Setup

  1. On ChatGPT web, open Plugins, select the plus button, then Add custom MCP server. Your workspace must permit this setup.
  2. Name the connection RoboWrite and enter the full MCP server URL.
  3. Choose OAuth authentication. If offered, choose Client ID Metadata Documents (CIMD) for client registration, then follow the browser sign-in and workspace consent steps.
  4. Install the resulting custom plugin, start a new conversation, and select RoboWrite before trying the account check below.

See the official ChatGPT MCP setup guide for current controls and workspace requirements. Use @ to choose the installed custom plugin in a conversation. A custom connection is separate from approval in ChatGPT's directory and does not import the repository's skill files.

Cursor Setup

For a project connection, add this configuration to your project's .cursor/mcp.json. The client ID is a public application identifier; no client secret is required. This example requests the disclosed multi-workspace consent. Choose your intended workspace in chat after connecting. Existing working single-workspace grants keep their original access; you do not need to replace them just to keep using that workspace.

Use this example only when multi-workspace access is enabled on the server. For a deployment managed by your team, that requires ROBOWRITE_MCP_ENABLE_MULTI_ORG=true. When it is off, use that deployment's advertised single-workspace permissions instead; changing requested scopes does not enable the feature.

{
  "mcpServers": {
    "robowrite": {
      "url": "https://mcp.robowrite.ai/mcp",
      "auth": {
        "CLIENT_ID": "UDGKiiooDBzdYmDp",
        "scopes": [
          "robowrite:organizations:read",
          "robowrite:content:all_orgs",
          "offline_access"
        ]
      }
    }
  }
}

Enable RoboWrite in Cursor's MCP controls, sign in through the browser, and review the tool list. Follow the Cursor MCP documentation if your interface differs. Project MCP configuration adds tools. Installing a marketplace plugin is a separate path that can bundle skills; RoboWrite's new-endpoint package remains held. Keep the normal per-tool approval controls enabled.

Claude Web and Desktop Setup

If Claude offers RoboWrite 0.2.2, use the custom connector steps to connect to https://mcp.robowrite.ai/mcp. That directory version includes robowrite-content-ops and points to the retired server. If you already have a connection to the current URL, use it for the read-only account check below.

Directory: Connector or Connector & Skill?

  1. Open Plugins in Claude's sidebar and search for RoboWrite. Accounts with the older interface use Customize.
  2. Read the entry type. You may see separate RoboWrite entries labeled Connector and Connector & skill; similar names do not mean identical contents.
  3. Open the intended entry and check its connector URL, included skills and version before adding it. For an entry using the current server, follow Connect and browser OAuth for workspace access.
  4. For a skill-bearing entry, confirm its skill is enabled in Your plugins. Type / or use + in chat to find it.

Check the version in your installed entry. The private Claude 0.3.4 package includes robowrite-setup, robowrite-onboarding and robowrite-content-ops. Onboarding helps you choose a workspace, set up your first brand or resume a setup you already started. The directory may offer an earlier version. A connector-only entry supplies the hosted tools. See Claude's Plugins page guidance for the interface rollout and organization controls.

Add a Custom Connector for Hosted Tools

  1. In Plugins, open Your plugins and look for RoboWrite. If its connector already uses the MCP URL above, open it and check its connection, then skip to the read-only first task below. Claude allows one registration per URL in an organization.
  2. On a personal account, open Plugins in Claude's sidebar, then choose Add > Add custom connector. If that option is disabled on Free, check Your plugins for the custom connector using your one slot. Team and Enterprise admins can use Organization settings > Connectors > Add > Custom > Web.
  3. Enter RoboWrite and the full MCP URL above. Review detected OAuth settings and use Claude's published identity when offered; automatic DCR registration is not supported by RoboWrite.
  4. Complete browser sign-in and consent, enable the connection in your chat, then run the read-only first task below.

Claude supports custom remote connectors on all plans. Packaged plugins require a paid plan. Organization policy may restrict either path. See the custom connector instructions and plugin requirements. Reconnecting a URL does not install missing skill files.

Claude Code Setup

For a tools-only project connection, merge this entry into the project's .mcp.json, preserving other servers. It uses a public client with no secret and the registered local callback on port 8787. Only one login can use that port at a time.

{
  "mcpServers": {
    "robowrite": {
      "type": "http",
      "url": "https://mcp.robowrite.ai/mcp",
      "oauth": {
        "clientId": "UDGKiiooDBzdYmDp",
        "callbackPort": 8787,
        "scopes": "robowrite:organizations:read robowrite:content:all_orgs offline_access"
      }
    }
  }
}

This example requests multi-workspace access; use it only when that capability is enabled. Approve the project configuration only if you trust it. Start Claude Code in that project, open /mcp, select RoboWrite and authenticate in the browser. Check server status before the first task. The official Claude Code MCP guide covers project approval, OAuth scopes and recovery.

If you enabled RoboWrite on claude.ai, sign into Claude Code 2.1.273 or later with the same account. At startup, Claude Code checks for new and updated account plugins in the background. When it reports a change, run /reload-plugins or start a new session to load the updated skills. API-key sessions do not sync account plugins. How Claude Code syncs account plugins

Update RoboWrite installed from a Claude Code marketplace

Open /plugin, choose Installed, and select RoboWrite. When your marketplace offers a newer version, choose Update now. Keep the marketplace shown on your existing installation. Adding RoboWrite from a second source can give you two copies of the same skill.

For a third-party Git marketplace, automatic updates are off by default. To receive future skill updates, open Marketplaces in the same menu, choose that marketplace and turn on auto-update. This setting applies to plugins from that marketplace. When Claude Code reports an update, run /reload-plugins or start a new session. Check RoboWrite under Installed for the updated version and its skills. Claude Code plugin update instructions

Codex Setup

For tools, connect directly to the hosted server using the project configuration below. For guided setup and content workflows, use the plugin installation instructions.

Install or update the RoboWrite skills in Codex

Use the Git marketplace instructions below once the package with the hosted endpoint is on the default branch of the RoboWrite repository. For a first installation, run:

codex plugin marketplace add RoboAdApp/robowrite-plugin
codex plugin add robowrite@robowrite

If you already installed RoboWrite from that Git marketplace, update it in place:

codex plugin marketplace upgrade robowrite

Check the installed version with codex plugin list. In a new Codex session, look for robowrite:robowrite-setup, robowrite:robowrite-onboarding and robowrite:robowrite-content-ops in the skills list. The setup skill walks you through checking the connected account.

Connect through project configuration

For a tools-only connection in a trusted project, merge this into.codex/config.toml, keeping existing settings. If this entry already uses the old address, update its URL in place. The scopes below request access to your eligible workspaces.

[mcp_servers.robowrite]
url = "https://mcp.robowrite.ai/mcp"
scopes = ["robowrite:organizations:read", "robowrite:content:all_orgs", "offline_access"]

From that project, run:

codex mcp login robowrite --oauth-client-registration cimd

Before running the login command above, check that codex mcp login --help lists --oauth-client-registration. If that flag is missing, upgrade Codex first. Then sign in to RoboWrite and review the permissions shown for Codex. Run codex mcp list, then open a new Codex session. Ask for your available RoboWrite workspaces. Choose one by name and ask Codex to check its connected account before opening content. If you already have a working single-workspace connection, you can check that account directly.

If login reports invalid_client with Client ID Metadata Document could not be resolved, contact RoboWrite support with your Codex version and the error text before reinstalling. The official Codex MCP guide covers project trust and OAuth setup.

Grok Build Setup

In the project where you use Grok Build, run grok mcp list --json. If RoboWrite is missing, add the hosted server from your terminal:

grok mcp add --transport http robowrite https://mcp.robowrite.ai/mcp

If RoboWrite is already listed, check its active address with grok inspect --json. An old manual entry can override the plugin and return HTTP 410. For a manual entry, edit the listed configuration file (~/.grok/config.toml for user scope or .grok/config.toml for project scope). Change only its URL to https://mcp.robowrite.ai/mcp.

Open /mcps in Grok Build, select RoboWrite and press i to sign in. On returning to Grok, try the read-only account check. If prompted, choose an eligible workspace and repeat the check. We have verified the CLI configuration. Native sign-in and reconnect are still under test. See Grok Build’s MCP controls.

Check the Connection Without Creating Content

After connecting, ask your assistant:

Use RoboWrite to check my account and show my available brands. Do not create, generate, edit, or publish anything.

The assistant should check the account first, then list brands for the selected workspace. Confirm the workspace is correct. Next, try recovering existing work:

Find my existing briefs and saved drafts for this brand. Show what is already available before suggesting new content.

When you are ready to create a draft, select the brand, review the brief and sources, and explicitly approve generation. Inspect the job before retrying; a slow response does not prove the job failed. Review the saved result before any publication decision.

Example: Prepare an SEO/GEO Brief for Review

Choose your workspace and brand, then replace the URL placeholders with the competitor pages and supporting sources you want to use:

Prepare a reviewable SEO/GEO brief for my selected workspace and brand about choosing a content operations platform. Target keywords: content operations platform; AI content workflow. Competitor URLs: [paste competitor URLs]. Supporting source URLs: [paste source URLs]. First recover any existing brief and read the saved brand voice. Inspect relevant library document summaries; where workspace retrieval is enabled and evidence is actually returned, identify the document IDs and context used. If context is unavailable, say so and ask me for it. Separate supplied URLs from sources actually read; do not claim fresh keyword or competitor research. Propose search intent, reader questions, an outline, source URLs, library attachments and evidence gaps for my review. Do not save the brief or start generation until I approve.

Library tools expose document metadata and structured summaries, not the full extracted text. Use only context actually available to the workflow; retrieval depends on workspace settings and the operation. Review the proposal and evidence gaps before asking to save or approve the brief. Check allowance again before generation.

Current Connection Checks

On November 19, 2026 (UTC), a reviewer signed in with Codex CLI 0.169.0, selected an eligible workspace and read its account. A second Codex process reused the saved connection and read the same account. Public plugin installation is still awaiting verification.

On November 17, 2026, a Claude Desktop custom connector completed connection to the canonical MCP host and its details identified it as a tools-only connection with no skills. This verifies the custom connection, not the directory bundle's installed version, skill delivery or picker-free workspace sign-in.

On November 21, 2026, an existing Grok Build test installation discovered 74 hosted tools, up from 68, with the same plugin files. Refresh tool discovery to pick up hosted tools. To get a new bundled skill, update the plugin through your client.

As of November 12, 2026, live checks found 63 tools on the hosted endpoint. Browser OAuth followed by authenticated account calls passed, including repeated and concurrent calls. The client-specific results below cover these historical checks only; they are not the date or results of the setup-instruction refresh.

  • Cursor: project connection, sign-in, and tool discovery verified. The packaged plugin's account call returned Unauthorized; packaged authentication remains unresolved.
  • Claude Code: browser sign-in and authenticated account calls passed with the prerelease plugin, including repeated and parallel calls. This does not establish the full workflow or managed plugin updates.
  • Native Claude: later read-only account, brand, brief, saved-draft and job checks passed during the November 16 acceptance campaign. These do not verify the owner's installed directory version, bundled skill visibility or picker-free multi-workspace sign-in.
  • Full installation, new-user signup, reconnect, and managed plugin-update acceptance checks remain pending across the supported clients. Account checks do not establish directory approval.
  • Packaged plugin endpoint update: held for remaining acceptance checks.

Troubleshooting and Updates

  • Website or HTML appears: check that the server URL ends in /mcp. The bare domain serves a website.
  • Old connection stopped working: replace the former www endpoint with the URL above, then reconnect and complete OAuth again. Old grants cannot be reused for the new resource address.
  • Organization setup requested: finish creating or selecting your workspace in RoboWrite, then reconnect.
  • Client registration fails: RoboWrite supports CIMD and registered public clients. It does not offer dynamic client registration (DCR). Use the setup for your client.
  • Skills are missing: inspect the installed entry's type, version and enabled skills. A successful account call proves tool access, not skill installation. Do not reinstall an old package or repeatedly reconnect to obtain missing files.
  • New tools are missing: refresh the connection and start a new conversation. Hosted changes do not require a local server install; client configuration or bundled skill changes may still require a plugin update.

Need help? Contact RoboWrite with your client name, version, and the error message, leaving out passwords and tokens. Developers can also use the public API reference.