Connect ContextBolt to your AI agent

Connect ContextBolt Bookmarks or SEO by adding its server URL to your AI app, signing in, and allowing the connection. This is OAuth. Your app gets permission to use your account without putting a personal key in its configuration.

Already connected with a personal URL? Leave it as it is. Existing connections keep working, and this change does not move or delete your data.

What you need

You need an account with access to the product you are connecting. Signing in does not start a subscription or activate a license.

• Bookmarks: Sign in to the extension with your email code and activate Pro. Add https://api.contextbolt.app/mcp to your AI app.
• SEO: Start a trial or subscription, then add https://seo.contextbolt.app/mcp. Sign in with the email on that SEO account.

These two shared URLs are not secret. Your email codes and access tokens are. Your SEO Dashboard is separate. You sign in to it with your SEO account email and a code.

Name your connection

Give the connection a clear name so your agent knows which one to reach for. We recommend matching the product.

• contextbolt-bookmarks
• contextbolt-seo

The examples below use Bookmarks. For SEO, change the name to contextbolt-seo and the URL to https://seo.contextbolt.app/mcp.

Claude Code

Add the server in your terminal.

claude mcp add --transport http contextbolt-bookmarks https://api.contextbolt.app/mcp

Open Claude Code, run /mcp, select the connection and authenticate. Complete the ContextBolt sign-in page in your browser, then allow the connection.

Claude Desktop and claude.ai

Open Settings, then Connectors, then Add custom connector. Give it a name and paste the shared URL.

Leave every option below the URL as you find it. Claude reads our settings and marks them Detected, so there is no header or client ID to add. One deserves a mention. Claude offers Use Anthropic’s hosted client metadata and labels it Recommended, but our server does not support it, so keep whichever option Claude selected.

Press Add. On the ContextBolt page, enter your email, enter the code we send, and choose Allow connection. Custom connector availability can depend on your workspace settings.

Use the connector settings for a remote server. Claude Desktop’s local JSON configuration is not a substitute for this browser sign-in.

ChatGPT

Use the custom MCP connection option available in your ChatGPT account or workspace. Add the shared URL for your product and choose OAuth authentication. Complete the ContextBolt email-code and permission steps in your browser. If custom connections are not available, check your plan or ask your workspace administrator. A public directory listing is not required for a custom connection.

Cursor

Add the server to your mcp.json under mcpServers.

{
  "mcpServers": {
    "contextbolt-bookmarks": {
      "url": "https://api.contextbolt.app/mcp"
    }
  }
}

In Cursor’s MCP settings, use the connection’s sign-in option and complete the ContextBolt browser flow. Saving the URL alone does not sign you in.

Codex

Run both commands in your terminal.

codex mcp add contextbolt-bookmarks --url https://api.contextbolt.app/mcp
codex mcp login contextbolt-bookmarks

Finish sign-in in the browser and allow the connection. In the Codex IDE extension, use Authenticate on the MCP connection instead.

Other clients and existing personal URLs

For a client that supports remote MCP with OAuth, add the shared URL and follow its authentication prompt. Client support varies. A URL-only client or automation that cannot complete OAuth can still use the personal-URL compatibility setup.

• Bookmarks: On Pro, open the extension’s Settings → MCP Integration. Newer versions keep it under Older clients.
• SEO: Your welcome email includes a personal URL as a compatibility option. An existing URL from an older email still works.

A personal URL has a secret after /mcp/. Treat the whole URL like a password. Do not commit it to Git, share it with a team, or send it to support. These warnings apply to personal URLs, not to the two shared OAuth URLs above.

Using OAuth? Check that the sign-in page is on api.contextbolt.app for Bookmarks or seo.contextbolt.app for SEO before entering a code. Review the app name and requested access before allowing it.

Check it worked

Ask, “What ContextBolt tools do you have?” Once connected, try a bookmark search or an SEO question. SEO research calls use your normal credits; signing in does not change your allowance.

If it is not working

• No code: Check spam first. For Bookmarks, use the email your extension is signed in with, and if no code arrives there, try the email you paid with. The code goes to whichever address you entered. For SEO, use your SEO account email. Bookmarks MCP needs Pro; SEO needs a current trial or subscription. Wait before requesting again if you hit the send limit.
• Wrong or expired code: Codes last 10 minutes. Start the connection again for a new code. A code for extension sign-in is not a code for connecting your AI app.
• Cancelled the permission screen: Nothing was connected. Start again from your AI app when you are ready.
• Disconnected or asked to sign in again: Authenticate from your AI app’s MCP settings. In Codex, run codex mcp login with your connection name again. This does not delete your data.
• Bookmarks extension signed out: Open Settings → Account and verify your email again. Your Pro access follows the account while the plan is active. Cloud bookmarks can then sync back; keep the extension open and allow time for syncing.
• Access ended: Resolve your plan or payment in the billing portal. Reconnecting does not bypass an ended plan.
• Personal URL not working: Check that the full secret URL was copied and the plan still has access.
• Still stuck: Email hello@contextbolt.com with the app name and error message. Never send a code, token or personal URL.

To remove OAuth access, disconnect ContextBolt in your AI app. Disconnecting is separate from cancelling your subscription.