Skip to content

New paid orders and subscriptions are retired. Existing records, settlement and refunds remain available through your account.

Connect an MCP client: what the transport is and is not

Streamable HTTP with JSON responses and a static key; no OAuth; the stdio bridge is not on npm.

/api/mcp speaks the JSON-response form of MCP Streamable HTTP, revisions 2025-06-18 and 2025-11-25, with no event stream and no sessions. On 2026-11-11 @modelcontextprotocol/sdk 1.32.2 and @modelcontextprotocol/client 2.4.0 connected to it with a static bearer key, listed and called its tools and read a refusal, with the route run locally and its database, key lookup, rate limiter and tool handlers mocked. It has no OAuth, so a hosted chat app that connects only through OAuth cannot call its keyed tools. The stdio bridge in packages/mcp-server remains for clients that only speak stdio; @cambridge-tcg/mcp-server is not on npm (404, rechecked 2026-10-10), but the source repository is public, so it can be built from a clone. A client that can POST JSON-RPC 2.0, or the public REST routes, work too.

10 min· 3 steps· last verified 2026-07-12· revised 2026-11-11

Steps revised after the last walk-through; the revised steps have not been walked through yet.

Prerequisites

  • • An MCP client that speaks Streamable HTTP and lets you set a request header, or an HTTP client that can send JSON-RPC 2.0 POST requests
  • • Optional: a Cambridge TCG account to provision a bearer token at /account/agents

Steps

  1. 1

    Read the connection facts

    Fetch the discovery document. It names the transport (Streamable HTTP, JSON responses only, no event stream, no sessions, no OAuth), when and how it was checked, the vendored bridge, and a list of no-auth direct-API tools.

    Run this

    curl https://cambridgetcg.com/.well-known/mcp-config.json

    Expected response shape

    { "remote_json_rpc_endpoint": { "cambridge-tcg": { "url": "...", "transport": "streamable-http", "mcp_streamable_http": true, "streamable_http": { "revisions": ["2025-11-25", "2025-06-18"], "oauth": false, ... } } }, "stdio_bridge": { "status": "vendored-in-repository", "npm_published": false, ... }, "no_auth_alternative_tools": [{ "tool_name": "ctcg_get_card", "url_template": "...", ... }], "recommended_user_agent": "...", "first_request_guide": "..." }

    What to do with it

    Use direct REST endpoints for public structural reads. Continue only when your MCP client needs the typed tool palette or authenticated agent-owned reads.

  2. 2

    Point a client at the gate

    Give an MCP client that speaks Streamable HTTP the URL https://cambridgetcg.com/api/mcp, with an Authorization: Bearer header if you have a key; Claude Code's form is claude mcp add --transport http cambridge-tcg https://cambridgetcg.com/api/mcp --header "Authorization: Bearer <token>" (Claude Code itself was not run against the gate; the two SDKs named above were). Or send JSON-RPC 2.0 requests yourself, as below. initialize, tools/list and ping are public; other tool calls need a bearer token. Do not use npx @cambridge-tcg/mcp-server: the package is not on npm. A client that only speaks stdio needs the bridge built from a clone of the public repository.

    Run this

    curl -s https://cambridgetcg.com/api/mcp \
      -H 'Content-Type: application/json' \
      -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

    What to do with it

    The response lists the tools and their input schemas. Authenticated calls add an Authorization: Bearer header; see step 3.

  3. 3

    Provision a bearer token (optional — for authenticated tools)

    If you want authenticated tools for your own agent, a signed-in human can provision an operator-managed key at /account/agents for account-linked reads and bounded Coverage Hunt review submissions. New self-serve registration is paused; existing self-serve keys remain read-only. Choose when the key expires as you mint it (90 days is pre-selected). Send the token as Authorization: Bearer <token> on each authenticated request.

    What to do with it

    Test with agent.self. Account identifiers stay internal; the response states whether the key is operator-bound, whether it is read-only, and when it expires (key_expires_at; null means it has no expiry).

Common gotchas

  • A remote MCP URL works only where the client can send the key

    The gate speaks Streamable HTTP but has no OAuth. A client whose remote-server setting can carry a static Authorization header should be able to call keyed tools (two MCP SDK clients did); one that connects only through OAuth (hosted chat apps) may be able to list the tools (no hosted app was run against it), but cannot call keyed ones. It offers no event stream (a GET asking for one gets 405) and no HTTP+SSE.

  • Set User-Agent in MCP server config too

    Even when going through the MCP gate, our backend reads the User-Agent as ordinary request metadata. A contact in it is voluntary and does not create a promise of outreach. Do not put secrets or personal data in the header.

  • An agent key expires when its minter chose, or never

    Each key's expiry is chosen when it is minted at /account/agents: 7, 30 or 90 days, 1 year, a date, or never. Keys minted before that choice existed have no expiry. agent.self's key_expires_at and the X-Agent-Key-Expires header on each successful authenticated tool result (not agent.revoke_key's answers) say when; no reminder is sent. An expired key gets 401 key_expired and cannot be renewed: before then, mint a new key (or ask whoever minted this one), move to it, then revoke the old one. A key also stops working if it is revoked or its agent is suspended or archived. Any key's holder can end that key with agent.revoke_key (confirm: true; without it, a preview); operator-managed keys can also be revoked at /account/agents.

  • Public and bearer limits differ

    Bearer tools enforce per-key tiers. Public endpoints publish advisory freshness and crawl guidance, but do not currently share one uniform per-endpoint edge quota.

Next guide

Build a Discord bot using Cambridge TCG data →

Slash command → keyed structural lookup → honest embed.

See also