Connect an assistant

Shared connection

MCP address:

https://continuitywriter.com/mcp

The earlier address https://continuity-snowy.vercel.app/mcp still reaches this server.

Transport: Streamable HTTP. Sign in with your own Continuity account when the assistant opens OAuth. Do not paste an API key, access token, or password into a header or chat. Revoke a host at any time from connected applications.

1. Sign in to the workspace and open or create a project you will recognize by name.
2. Add the MCP address in your assistant using the steps below. Choose dynamic registration / OAuth when the host asks how to authenticate.
3. Approve Continuity, then ask the assistant to retrieve canon and the latest checkpoint before drafting.

1. ChatGPT and Codex

The same server the ChatGPT/Codex plugin already uses. A public directory listing is not published yet, so connect it as a custom app.

1. On workspace plans, an admin enables developer mode under Workspace settings → Permissions & roles → Connected data developer mode / Create custom MCP connectors. Personal accounts that already offer custom apps can skip that toggle.
2. Open Apps → Create (workspace admins: Workspace settings → Apps → Create; other authorized users: Settings → Apps → Create).
3. Enter the MCP address, choose OAuth, scan tools, and approve the Continuity sign-in.
4. Enable the app in the conversation. Developer-mode apps are labeled Dev and are not OpenAI-verified.

Codex can install the plugin package in plugins/continuity from a personal marketplace as continuity@personal, or use this same MCP address. Request includes offline_access when the host offers refresh; Continuity’s authorization server advertises that scope.

2. Claude

Claude.ai, Claude Desktop, Cowork, and the mobile apps use a remote connector. Claude’s servers call Continuity; you do not install a local plugin.

1. Free, Pro, and Max: Customize → Connectors → Add custom connector. Team and Enterprise: an owner adds it under Organization settings → Connectors → Add → Custom → Web, then each member chooses Connect.
2. Name it Continuity and paste the MCP address.
3. Choose sign-in (OAuth). For the OAuth client, choose Register automatically (dynamic client registration). Leave client id and secret empty. Do not put a token in request headers.
4. Approve Continuity in the browser, then turn the connector on from the chat + menu → Connectors.

Claude Code, from a terminal:

claude mcp add --transport http continuity https://continuitywriter.com/mcp

Do not pass --header Authorization. Claude Code opens the same OAuth flow. In a JSON config, set "type": "http" next to url.

3. Gemini

Gemini Apps (supported, with Google’s eligibility limits)

Google’s Gemini Apps help documents custom connected apps: add an MCP server URL in the Gemini web app. Google requires you to be 18 or older, in the US, signed in with a personal Google Account, with Keep Activity on. Work and school accounts cannot use this path. Custom apps are English-only. Connect on the web; the link then works in the Gemini mobile app too.

1. On a computer, open gemini.google.com → Settings → Connected apps. If you do not see Connected apps, open Personal Intelligence → Connected apps first.
2. Under Custom apps, add a custom app and paste the MCP address.
3. Leave advanced credentials empty. Continuity supports dynamic client registration, so a client id is not required.
4. Finish Google’s sign-in, then type @ and choose Continuity when you want that chat to use it.

Gemini CLI (supported)

Gemini CLI can add a Streamable HTTP server and discover OAuth itself, including dynamic registration:

gemini mcp add --transport http --scope user continuity https://continuitywriter.com/mcp

That writes ~/.gemini/settings.json. Do not set an Authorization header. If the CLI reports a missing issuer (iss) on the callback, Google is enforcing RFC 9207 and the authorization server did not return that parameter. Continuity cannot add it from this app. Use Gemini Apps, or another host, until that redirect includes iss.

Not available yet

• Gemini API, including Gemini 3 in the Interactions API. Google’s Interactions API docs say Gemini 3 does not support remote MCP and that support is coming later. There is no Continuity function-calling schema to paste into AI Studio. A managed-agent mcp_server tool appears in Google’s agent materials without a Continuity OAuth sign-in; do not paste a Continuity access token into it.
• Gemini Enterprise custom MCP. The admin form (business.gemini.google, Add MCP server, OAuth 2.0) requires a client id and secret for an OAuth app whose redirect URL is https://vertexaisearch.cloud.google.com/oauth-redirect. Continuity does not publish that client. The public authorization and token URLs are on the Supabase issuer advertised at /.well-known/oauth-protected-resource/mcp, and the scopes are email and offline_access, but an owner has to register the Enterprise client in Supabase before that form can be saved.

4. Grok

Grok on the web

1. Open grok.com/connectors.
2. Choose New connector → Custom.
3. Paste the MCP address and finish the sign-in Grok presents.

On Grok Business and Enterprise, an admin provisions connectors before members can use them. The server must be reachable on the public internet. Grok discovers the tools after you connect.

Grok Build

grok mcp add --transport http continuity https://continuitywriter.com/mcp

OAuth runs in the browser on first use. The equivalent user config is:

[mcp_servers.continuity]
url = "https://continuitywriter.com/mcp"

in ~/.grok/config.toml. Do not set an Authorization header. In the Grok Build UI, /mcps then i starts sign-in.

xAI API

The xAI API remote-MCP tool accepts a static authorization bearer token. Continuity does not issue API keys or long-lived tokens for that field. Use grok.com or Grok Build, which perform OAuth, instead of pasting a session token into an API request.

5. Cursor and other MCP clients

Cursor speaks remote Streamable HTTP with OAuth. In ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "continuity": {
      "url": "https://continuitywriter.com/mcp"
    }
  }
}

Do not add headers or a static auth client id. Cursor registers a client and opens sign-in. Restart Cursor or enable the server under Customize → MCPs. A static OAuth client is only for servers that lack dynamic registration; Continuity has it, so registering Cursor’s redirect URLs by hand is unnecessary.

Any other MCP client uses the same address when it supports Streamable HTTP, OAuth 2.0 with PKCE, and dynamic client registration (RFC 7591). An unauthenticated call returns 401 with a WWW-Authenticate challenge pointing at /.well-known/oauth-protected-resource/mcp. Ask for the email scope. Add offline_access when the client can refresh tokens. Clients that call from their own servers should not send a browser Origin. Browser calls are accepted only from Continuity and the assistant sites listed in the server allowlist; other websites are rejected.

After it connects

“Use Continuity to resume my story [project name]. Retrieve its canon and latest checkpoint before drafting.”

“Keep concise checkpoints for this story when we finish a scene or pause. Keep unresolved ideas provisional, and ask before making new canon official.”

Canon holds facts you approve. Approved scenes hold summaries of accepted scenes. Checkpoints preserve story progress, open questions, and next steps separately from canon.

The assistant calls tools only when you and the host allow it. Continuity cannot watch every chat, run while the assistant is idle, or guarantee a save before context loss. Ask to save a checkpoint before switching chats. Disconnecting an application stops future access; it does not delete stories or cancel billing.