Start with Roami

What you're connecting

Roami is a CMS for you and your agent. You write the part that matters — the meaty, first-person stuff. The agent handles the boring 80%: SEO, internal links, metadata, alt text, drafts from your archive.

Two ways in: write directly in the CMS yourself, or connect an agent over MCP so it can draft from your live archive. Most people end up using both. Either way, publish stays yours.

Part 1 — Use the CMS

This is the fastest way to start, and it needs nothing but an email address. No key, no config, no agent required.

Sign up free, open Studio, and write your first post. Everything an agent can do later — SEO, tags, internal links — you can also do by hand here from day one.

Part 2 — Connect an agent

Once you have an account, connect Claude, Cursor, or Gemini so it can work from your archive too. API keys are founder-minted right now — there's no self-serve generate button yet. Email us with a short intro and we'll reply with your key.

Connect Claude

Add Roami as an MCP server in Claude Desktop (or Cursor). Paste your key where you see sk_...

{
  "mcpServers": {
    "roami": {
      "type": "sse",
      "url": "https://mcp.roami.xyz/sse",
      "headers": {
        "Authorization": "Bearer sk_..."
      }
    }
  }
}

Create your first draft

Ask Claude something concrete. Good first prompts:

• Create a draft post titled “Notes from [place]” with three short sections.
• Turn this outline into a Roami draft and attach the tag [your topic].
• Search my content for posts about [topic], then draft a follow-up.

Review & publish

Publish stays human-gated, always. Agents draft and update; you hit publish in the CMS.

Open Studio at https://app.roami.xyz, review the draft, and publish when it is ready. Direct publish via API or MCP returns 403 by design.

Troubleshooting / FAQ

My agent can't publish

That is intentional. Publish is hard-blocked for agents (API returns 403). Review the draft in the CMS and publish there. This is a permanent product safety commitment, not a temporary beta quirk.

Claude does not see Roami tools

Confirm the MCP URL is https://mcp.roami.xyz/sse, the Authorization header uses Bearer sk_..., and Claude Desktop was fully quit and restarted after editing the config.

I get 401 Unauthorized

Check that the key is pasted without extra spaces, and that you are sending either Authorization: Bearer sk_... or x-api-key: sk_... against api.roami.xyz.

Where do drafts show up?

In the Roami app/CMS for the project tied to your key: https://app.roami.xyz. Drafts are created in DRAFT status by default.