Connect an assistant

Shared connection

MCP address:

https://claim-continuity2.vercel.app/mcp

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

1. Sign in and open or create a brand you will recognize by name.
2. Add the MCP address in your assistant using the steps below. Choose dynamic registration and OAuth when the host asks how to authenticate. Leave client id and secret empty.
3. Approve Claim, then ask the assistant to load the brand guide before it writes copy.

1. ChatGPT and Codex

Connect Claim as a custom app. A public directory listing is not published yet.

1. On workspace plans, an admin enables developer mode under Workspace settings, then Permissions and roles, then Connected data developer mode. Personal accounts that already offer custom apps can skip that toggle.
2. Open Apps, then Create.
3. Enter the MCP address, choose OAuth, scan tools, and approve the Claim sign-in.
4. Enable the app in the conversation.

Codex can use this same MCP address. Request offline_access when the host offers refresh. Claim’s authorization server advertises that scope.

2. Claude

Claude.ai, Claude Desktop, and Claude Code call Claim from Claude’s servers. You do not install a local plugin.

1. Add a custom connector and paste the MCP address. On a team workspace, an owner adds it first, then each member connects.
2. Name it Claim.
3. Choose sign-in with OAuth. For the OAuth client, choose automatic registration. Leave client id and secret empty. Do not put a token in request headers.
4. Approve Claim in the browser, then turn the connector on for the chat.

Claude Code, from a terminal:

claude mcp add --transport http claim https://claim-continuity2.vercel.app/mcp

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

3. Gemini

Gemini Apps

Google’s Gemini Apps can add an MCP server URL in the Gemini web app, subject to Google’s eligibility limits. Connect on the web. The link then works in the Gemini mobile app too.

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

Gemini CLI

gemini mcp add --transport http --scope user claim https://claim-continuity2.vercel.app/mcp

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

Gemini API remote MCP and Gemini Enterprise custom MCP are not a supported Claim path. Do not paste a Claim access token into an API request. Enterprise forms that require a pre-registered client id are not published by this server.

4. Grok

Grok on the web

1. Open grok.com/connectors.
2. Choose New connector, then 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 Build

grok mcp add --transport http claim https://claim-continuity2.vercel.app/mcp

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

[mcp_servers.claim]
url = "https://claim-continuity2.vercel.app/mcp"

in ~/.grok/config.toml. Do not set an Authorization header.

The xAI API remote-MCP tool accepts a static bearer token. Claim does not issue API keys or long-lived tokens for that field. Use grok.com or Grok Build, which perform OAuth.

5. Cursor and other MCP clients

Cursor speaks remote Streamable HTTP with OAuth. In ~/.cursor/mcp.json or a project .cursor/mcp.json:

{
  "mcpServers": {
    "claim": {
      "url": "https://claim-continuity2.vercel.app/mcp"
    }
  }
}

Do not add headers or a static auth client id. Cursor registers a client and opens sign-in. Any other MCP client uses the same address when it supports Streamable HTTP, OAuth 2.0 with PKCE, and dynamic client registration. An unauthenticated tool 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 Claim and the assistant sites listed in the server allowlist.

After it connects

Ask the assistant to load the brand guide before it writes. Approved claims are the only guarantees it may repeat. Active offers are the only discounts and offers it may state. Proof is evidence for a saved claim. It does not approve new language. Banned phrases must not appear. Voice is how the brand sounds, not permission to invent a promise.

The assistant calls tools only when you and the host allow it. Disconnecting an application stops future access. It does not delete brands or cancel billing.