Skip to content

Connect Claude to a Voozeo MCP server

Updated October 24, 2026

To connect Claude to your Voozeo MCP server, add a custom connector in claude.ai or Claude Desktop with the URL that contains your key, or run one command in Claude Code.

What you need

  • A Voozeo server in the "active" state, which means at least one source is ready. See getting started.
  • The MCP key of that server. It is shown only once, when the server is created or the key is regenerated. If you lost it, regenerate it.
  • If your server uses OAuth 2.0, there is no key: add the server URL alone, then each person signs in with their own account at the API provider on the first call. See servers using OAuth.
  • A Claude plan that allows custom connectors. On a Team or Enterprise plan, an Owner adds the connector from the organization settings.

Which URL for which Claude app

Claude appURL to useWhere to paste it
claude.aiURL that contains the keyCustomize, Connectors, Add custom connector
Claude DesktopURL that contains the keySame screen: connectors belong to your Claude account
Claude CodeURL with the key in the Authorization headerTerminal command or .mcp.json file

The URL that contains the key is a secret: do not share it. See the two URL forms.

Add the connector in claude.ai or Claude Desktop

  1. In Voozeo, open your server, go to the "Connection" tab and choose your Claude app. The real URL and key are already filled in right after creation or regeneration. Otherwise the blocks show <YOUR_KEY>: replace it with your key.
  2. In Claude, open Customize, then Connectors, then Add custom connector.
  3. Enter the server name and the URL that contains your key, and choose no authentication.
  4. Save the connector.

claude.ai

Customize > Connectors > Add custom connector
Name: my-server
Remote MCP server URL: https://mcp.example.com/k/<your-key>/mcp
Authentication: No sign-in

Add the server in Claude Code

Run the command in your terminal. To share the configuration with a team, use the project's .mcp.json file instead: it reads the key from an environment variable, so the key is not written in the file.

Claude Code

claude mcp add --transport http my-server https://mcp.example.com/s/<server-id>/mcp --header "Authorization: Bearer <your-key>"

Claude Code · .mcp.json

{
  "mcpServers": {
    "my-server": {
      "type": "http",
      "url": "https://mcp.example.com/s/<server-id>/mcp",
      "headers": {
        "Authorization": "Bearer ${VOOZEO_KEY}"
      }
    }
  }
}

Check the connection

  1. Ask Claude to list the tools of the server, or ask a question that needs one.
  2. Open the "Log" tab of the server in Voozeo: every tool call appears there.
  3. If in doubt, try the tool first in the "Test" tab. See testing in the sandbox.

Troubleshooting

Claude reportsLikely causeWhere to look
Authentication error (401)Key missing, wrong, from another server, or regenerated401 on the AI side
Access denied (403)Server not "active", or workspace suspended403 on the AI side
Quota messageThe monthly call limit of your plan is reachedQuota reached

Menus change between Claude versions: see the official Claude documentation on custom connectors and, for the command line, the Claude Code documentation on MCP.

Next steps

Get started