RoboWrite
Planifiez du contenu adapté à la marque, examinez des briefs et récupérez des brouillons Markdown enregistrés depuis RoboWrite.
Serveur MCP hébergé
npx add-mcp 'https://mcp.robowrite.ai/mcp'S’installe dans Claude Code, Codex, Cursor et plus
Documentation
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 is still version 0.2.3 and points to the retired endpoint. Its 0.3.0 endpoint update is held; do not install that older package expecting the connection below.
| Client | Connection path | Skills and availability |
|---|---|---|
| Claude web / Desktop | Directory entry or custom remote connector | Check whether the entry says Connector or Connector & skill. |
| Claude Code | Project MCP configuration and browser OAuth | Direct MCP adds tools; installed plugin skills are separate. |
| Codex | Project MCP configuration and OAuth login | Known native reconnect failure; see the Codex troubleshooting note before retrying. |
| ChatGPT web | Custom MCP plugin, where permitted | Custom connection is separate from public-directory approval and bundled skills. |
| Cursor | Project.cursor/mcp.json | Project connection and packaged plugin have different acceptance results. |
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
- 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.
- 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.
- 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.
- Ask RoboWrite to list your workspaces with
list_organizationsand show your role and access withget_organization_access. - Choose the intended workspace explicitly. The assistant uses
switch_organizationto verify it, then checks the account with thatorganization_id. - 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
- On ChatGPT web, open Plugins, select the plus button, then Add custom MCP server. Your workspace must permit this setup.
- Name the connection RoboWrite and enter the full MCP server URL.
- Choose OAuth authentication. If offered, choose Client ID Metadata Documents (CIMD) for client registration, then follow the browser sign-in and workspace consent steps.
- 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
Directory: Connector or Connector & Skill?
- Open Plugins in Claude's sidebar and search for RoboWrite. Accounts with the older interface use Customize.
- Read the entry type. You may see separate RoboWrite entries labeled Connector and Connector & skill; similar names do not mean identical contents.
- Open the intended entry and check its connector URL, included skills and version before adding it. Follow Connect and browser OAuth for workspace access.
- For a skill-bearing entry, confirm its skill is enabled in Your plugins. Type
/or use+in chat to find it.
Directory visibility does not establish which version you installed. The held 0.3.0 package contains robowrite-setup and robowrite-content-ops; delivery of that version through the directory is not yet verified. A Connector-only entry supplies tools, not those bundled skills. See Claude's Plugins page guidance for the interface rollout and organization controls.
Custom URL: Tools Without Bundled Skills
- From the connector controls, choose Add, then Custom and Web. In the older interface, open Customize > Connectors first.
- 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.
- Complete browser sign-in and consent, enable the connection in your chat, then run the read-only first task below.
Claude documents custom remote connectors on all plans, with one custom connector on Free; 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.
A plugin installed in your Claude account can also sync to Claude Code 2.1.273 or later when signed in with that same account; API-key sessions do not sync it. Sync support does not prove RoboWrite's current directory package is installed or updated. Avoid adding a second connection if a working synced connector already exists.
Codex Setup
Known reconnect issue: native OpenAI/Codex reconnect has returned invalid_client with Client ID Metadata Document could not be resolved. If you see this exact error, contact RoboWrite support with your client version and the error text. Do not repeatedly reinstall the plugin or repeat login to work around it.
Native Codex uses its own OAuth client identity, separate from ChatGPT web's custom-plugin connection. Its public Client ID Metadata Document is reachable, but that does not verify Clerk's fetch or establish whether callback-port matching is involved. A working ChatGPT web connection does not certify native Codex reconnect. The recipe below remains documented configuration, not a verified workaround for this failure.
For a tools-only connection in a trusted project, merge this into.codex/config.toml, keeping existing settings. It uses the same conditional multi-workspace permissions as the examples above. This is a client configuration recipe, not a verified RoboWrite Codex sign-in or packaged-install result.
[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
Follow browser sign-in, review consent, then check codex mcp list and start a new session for the first task. Use a current Codex version whose login help includes this option. If registration is rejected, stop and contact support; do not replace it with DCR or paste a token. The official Codex MCP guide explains project trust, shared local-client settings and OAuth. This configuration does not install RoboWrite's plugin skills.
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 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.
Separately, the November 16 hosted inventory contained 66 tools. That is a dated catalog count, not a fresh count measured during the November 17 custom-connector handshake or proof that every tool passed end-to-end testing. Public plugin version 0.2.3 and the held 0.3.0 bundle are separate from the hosted catalog.
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.
- Codex: setup syntax is documented above; a native reconnect failure is described in the Codex section. End-to-end sign-in and packaged installation remain unverified.
- 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.