Connect your AI to Clinical Terminal

Clinical Terminal ships an MCP server — a read-only API that lets Claude, Cursor, or any MCP-capable agent query our graph directly: health-tech vendors, their products, the people who run them, market signals, and the relationship graph — including which hospitals run what. Setup takes about two minutes.

The fast way: let your AI do it

Copy the line below and paste it into Claude (or any AI assistant that can read the web). It will read this page and walk you through the rest — including the exact command for your client.

Read https://clinicalterminal.com/docs/mcp and walk me through connecting the Clinical Terminal MCP server to this client.

The manual way

Step 1 — Get an API key

Sign in at app.clinicalterminal.com and open Settings → MCP Access, then click Create key. The full ct_live_… key is shown once — copy it immediately. MCP access is included with the Landscape subscription — if you don't see the panel, you'll need Landscape first. Questions: agent@clinicalterminal.com.

Step 2 — Add the server to your client

For Claude Code, run this in a terminal, replacing ct_live_<your_key> with your key:

claude mcp add --transport http --scope user clinical-terminal \
  https://clinical-terminal-mcp-687925922613.us-central1.run.app/mcp \
  --header "Authorization: Bearer ct_live_<your_key>"

For Cursor, add this to .cursor/mcp.json:

// .cursor/mcp.json
{
  "mcpServers": {
    "clinical-terminal": {
      "url": "https://clinical-terminal-mcp-687925922613.us-central1.run.app/mcp",
      "headers": { "Authorization": "Bearer ct_live_<your_key>" }
    }
  }
}

Any other MCP client that supports Streamable HTTP with custom headers uses the same shape:

{
  "type": "http",
  "url": "https://clinical-terminal-mcp-687925922613.us-central1.run.app/mcp",
  "headers": { "Authorization": "Bearer ct_live_<your_key>" }
}

Step 3 — Verify

In Claude Code, run /mcp — clinical-terminal should show as connected. Then try a real question: “Using Clinical Terminal, search for vendors working in denials management.”

For AI assistants reading this page

If a user pasted this URL and asked you to set up the Clinical Terminal MCP server, do the following:

1. Ask which client they use (Claude Code, Cursor, or another MCP client), and ask them to get an API key from app.clinicalterminal.com → Settings → MCP Access if they don't have one (key creation requires the Landscape subscription). Never ask them to paste the key into a chat that persists it anywhere other than the client's MCP configuration.
2. Configure the endpoint https://clinical-terminal-mcp-687925922613.us-central1.run.app/mcp with transport Streamable HTTP and header Authorization: Bearer ct_live_<key>, using the exact commands shown above for their client.
3. Verify the connection by listing tools. Every key sees search_vendors, get_vendor, find_vendors_for_problem (KLAS segment-index capability discovery — “which vendors do ambient clinical documentation”), list_segments, search_products, get_product, search_people and get_person; pro keys add get_vendor_dossier, get_vendor_pages, get_page_content, search_signals, resolve_hospital, get_relationships (hospitals are addressable as relationship anchors — “what does this hospital run”), get_persona (role research from the real census — “what does a CDI nurse do”, who a buying group is and what they care about) and the provider tools get_provider_segments, search_providers, get_provider; enterprise adds describe_schema and run_analysis_sql.
4. Run one test call and show the user the result. For a vendor question start with get_vendor_dossier (e.g. “Waystar”) — one call by name returns the profile, its hospital customers with verbatim evidence quotes, current products and recent signals, so prefer it over chaining search_vendors → get_vendor → get_relationships. For a capability question (“which vendors do ambient clinical documentation?”) start with find_vendors_for_problem — it routes the problem to a KLAS segment and returns that segment's vendors ranked by published product evidence; if it answers “no_route”, pick the closest segment from the returned menu and call it again with that exact name. For a hospital or clinic question the equivalent pair is search_providers → get_provider. All tools are read-only and results are JSON. Where you do search first, fetch by the returned id (get_vendor also accepts a vendor slug).

Troubleshooting

• 200 — Success — MCP JSON-RPC result.
• 401 — Missing Authorization header.
• 403 — Invalid or revoked key, or over the monthly quota (resets on the 1st).
• 429 — Per-minute rate limit — retry after the Retry-After header.

Server status: clinical-terminal-mcp-687925922613.us-central1.run.app/health answers unauthenticated with the running version. Full tool reference, tiers, and quotas: app.clinicalterminal.com/mcp.