Connect to Claude

The server URL

The Aims MCP server lives at a single streamable-HTTP endpoint:

• Server URL: https://useaims.com/api/mcp/mcp

• Transport: streamable HTTP (the modern remote-MCP transport)

• Auth (CLI clients): an Authorization header carrying your key as a Bearer token

• Auth (URL-only clients like ChatGPT / claude.ai): the key embedded in the URL as ?key=YOUR_KEY

Step 1 — Generate a key in Settings

1. 1

   In Aims, go to Settings → Claude / MCP.

2. 2

   Click "Generate key." Give it a name you'll recognise (e.g. "Claude Desktop" or "my laptop") so you can revoke the right one later.

3. 3

   Your key (it starts with aims_mcp_sk_live_) is shown with Reveal, Copy, and Rotate buttons. It is stored encrypted, so you can reveal or copy it again anytime. Use Rotate to replace it — the old key stops working immediately.

Two ways to connect

Settings → Claude / MCP has an Authentication toggle that generates the exact config for you. Pick whichever matches your client:

• Remote servers (ChatGPT, claude.ai) — copy the ready-made URL with your key already embedded (https://useaims.com/api/mcp/mcp?key=YOUR_KEY) and paste it as a custom connector. One paste, no separate header.

• CLI (Claude Code, Cursor, VS Code / Copilot, Windsurf, Codex, Gemini CLI) — choose your client and copy the generated command or config block, which uses the Authorization: Bearer header.

Step 2 (option A) — Add it on claude.ai

1. 1

   Open claude.ai and go to Settings → Connectors (or "Custom connectors" / "Add custom connector", depending on your plan).

2. 2

   Click "Add custom connector."

3. 3

   Name it "Aims" and paste the server URL https://useaims.com/api/mcp/mcp.

4. 4

   When prompted for authentication, paste your aims_mcp_sk_live_ key as the Bearer token / API key.

5. 5

   Save. Aims now appears in the connector list and its tools are available in new conversations.

Step 2 (option B) — Add it in Claude Desktop

Claude Desktop reads connectors from its claude_desktop_config.json file. Add an entry under mcpServers that points at the Aims endpoint and passes your key in the Authorization header:

{ "mcpServers": { "aims": { "type": "http", "url": "https://useaims.com/api/mcp/mcp", "headers": { "Authorization": "Bearer aims_mcp_sk_live_YOUR_KEY_HERE" } } } }

Replace aims_mcp_sk_live_YOUR_KEY_HERE with the key you copied in Step 1, save the file, and fully restart Claude Desktop. If your build of Claude Desktop does not support remote HTTP servers directly, use the mcp-remote bridge instead: set command to "npx" and args to ["mcp-remote", "https://useaims.com/api/mcp/mcp", "--header", "Authorization: Bearer aims_mcp_sk_live_YOUR_KEY_HERE"].

Step 3 — Test the connection

Start a new conversation and ask the assistant to "list my Aims brands." It should call aims_list_brands and return your brand profiles. That round-trip confirms the URL, the key, and the connector are all wired up correctly.

• If you get an "unauthorized" or "not bound to an Aims user" error, the key is missing, mistyped, or revoked — re-copy it from Settings and update the connector.

• If the assistant says it has no Aims tools, the connector did not load: re-check the URL and (in Claude Desktop) restart the app after saving the config.

• If a tool reports "Search embeddings are not configured for this workspace," your account does not yet have indexed inspiration — add a competitor or social source first.