Claude Code

What you're setting up

Claude Code speaks Streamable HTTP. The Talaria URL is https://api.newtalaria.com/mcp.

Why use this

An entry that has url and no type is skipped: Claude Code reads that shape as a local stdio server.

Before you start

Claude Code starts OAuth when the server answers tools/list with HTTP 401. Sign in to Talaria and allow install scopes (mcp:read mcp:write mcp:keys). A personal token from Workspace › Integrations is the fallback when OAuth stalls.

Never send a monitor token to MCP.

Steps

1. Add the server

From a terminal, outside a Claude Code session:

claude mcp add --transport http --scope user Talaria https://api.newtalaria.com/mcp

--scope user registers Talaria for every project. Omit it to keep the server in the current project only. Then run claude mcp list and confirm Talaria is connected.

The same entry in .mcp.json (project) or the user config:

{
  "mcpServers": {
    "Talaria": {
      "type": "http",
      "url": "https://api.newtalaria.com/mcp"
    }
  }
}

type may be streamable-http. It may not be omitted.

Check it worked

Call get_connection and announce identity before creating projects or minting keys. Install and investigation follow Add Talaria with an agent and Triage issues with an agent.

Troubleshooting

Personal token (if OAuth stalls)

Cause: OAuth stalls.

Fix:

1. Dashboard Workspace › Integrations → Create personal token. Choose 30 days, 90 days, or until you revoke it.
2. Add the header. The dashboard Copy Cursor mcp.json button is the Cursor file and is missing type, so do not paste it here.

claude mcp add --transport http --scope user Talaria https://api.newtalaria.com/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"

{
  "mcpServers": {
    "Talaria": {
      "type": "http",
      "url": "https://api.newtalaria.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

The token is an opaque single-segment base64url JSON payload (starts with eyJzdWIi…), not a three-part JWT. One space after Bearer.

Never send a monitor token to MCP.

Next steps

• MCP overview
• Cursor