All guides

RoboWrite MCP: Connect ChatGPT, Claude, and Cursor

Bring your brand context, 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 for your selected workspace.

MCP server URL

https://mcp.robowrite.ai/mcp

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. Publishing is a separate action; the default MCP connection does not enable publication tools.

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. Open ChatGPT's custom MCP server setup in Plugins.
  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. A custom connection is separate from approval in ChatGPT's directory.

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 keeps the existing single-workspace consent. For the separately consented multi-workspace flow, use the updated plugin configuration once that capability is enabled.

{
  "mcpServers": {
    "robowrite": {
      "url": "https://mcp.robowrite.ai/mcp",
      "auth": {
        "CLIENT_ID": "UDGKiiooDBzdYmDp",
        "scopes": [
          "user:org:read",
          "robowrite:content",
          "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 and installing a marketplace plugin are separate setup paths.

Claude and Claude Code Setup

In Claude's connector settings, use a custom remote connection with the full server URL and browser OAuth. Claude Code has a separate MCP configuration; use the client-specific configuration and instructions in the RoboWrite plugin repository when the endpoint migration is released. Do not reuse Cursor's configuration file as Claude's configuration.

The Claude Code MCP guide explains browser authentication and server status. Check the current verification status below before depending on this path.

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.

Current Connection Checks

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 checks only.

  • 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.
  • 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.
  • 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.