Connecting Claude

Claude reaches Zuse Bifrost as a connector: you give it the server URL, it sends you to Zuse Bifrost to sign in, and you approve the connection. Connectors are shared across claude.ai and Claude Desktop on the same account, so you set one up once. The server address is written as https://mcp.example.test below; use the one your administrator shares.

RequirementsCopy Anchor Link

• A Claude plan that allows custom connectors (Pro, Max, Team or Enterprise; on Team and Enterprise an admin may need to enable them).
• A Zuse Bifrost account. The connection acts as you, on the team you are working in.

Claude CodeCopy Anchor Link

From a terminal:

claude mcp add --transport http zusegenius https://mcp.example.test

Then run /mcp inside Claude Code and pick Authenticate next to zusegenius; the same browser sign-in and consent screen follow. A coding agent connected this way reads the project record beside the repository it is changing, which is where the planning and test tools will matter most as they land.

Using a personal access token insteadCopy Anchor Link

If you would rather the connection carry only the abilities you choose, read-only or one project, mint a token under Account Settings → API Tokens and configure Claude with it as a header instead of signing in.

In Claude Code:

claude mcp add --transport http zusegenius https://mcp.example.test \
  --header "Authorization: Bearer zg_live_YOUR_TOKEN"

In Claude Desktop through claude_desktop_config.json (macOS ~/Library/Application Support/Claude/, Windows %APPDATA%/Claude/), using the mcp-remote bridge, because the config file speaks stdio:

{
  "mcpServers": {
    "zusegenius": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.example.test",
        "--header",
        "Authorization:${AUTH_TOKEN}"
      ],
      "env": {
        "AUTH_TOKEN": "Bearer zg_live_YOUR_TOKEN"
      }
    }
  }
}

Fully quit and relaunch Claude Desktop after editing the file; MCP servers are loaded at launch. When the token rotates, mint a new one, replace the value, relaunch.

TroubleshootingCopy Anchor Link

• The connector will not connect: the URL must be the server's address with nothing after it. Claude compares it to the address the server publishes and refuses a mismatch.
• Sent to the application but no consent screen: you were asked to sign in first; complete the sign-in and Claude retries the authorization.
• Tools vanished after a while: Claude renews access silently; if the renewal failed, disconnect and connect again from Settings → Connectors.
• A refusal on one tool with a personal access token: it lacks that tool's ability; the error names it in error.context.required_ability.
• Logs: Claude Desktop keeps MCP logs under Developer → MCP → View logs.

Security tipCopy Anchor Link

An OAuth connection never puts a secret on your disk. A personal access token in a config file is plaintext: treat it as you would any credential file, with filesystem permissions, no screen recording while the config is open, and a rotation when the laptop changes hands.