Skip to main content
Adapter exposes a Model Context Protocol server on two transports:
TransportEndpointUse when
Streamable HTTP (recommended)https://api.adapter.com/v1/mcp/httpAny client built for MCP 1.0+
SSE (legacy)https://api.adapter.com/v1/mcp/sseClients that don’t yet support streamable HTTP
Auth: Every request requires a pk_live_… API key in the Authorization: Bearer header. See API keys.

Claude Desktop

Claude Desktop uses mcp-remote as a local proxy.
1

Find your config file

Open or create ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows).
2

Add the Adapter server

{
  "mcpServers": {
    "adapter": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.adapter.com/v1/mcp/http",
        "--header",
        "Authorization: Bearer ${ADAPTER_API_KEY}"
      ],
      "env": {
        "ADAPTER_API_KEY": "pk_live_..."
      }
    }
  }
}
Replace pk_live_... with your key, or set ADAPTER_API_KEY in your shell environment and omit the env block.
3

Restart Claude Desktop

Quit and reopen the app. A hammer icon in the chat toolbar confirms the server connected.

Claude Code

Claude Code supports streamable HTTP natively.
claude mcp add --transport http adapter https://api.adapter.com/v1/mcp/http \
  --header "Authorization: Bearer $ADAPTER_API_KEY"
Run /mcp inside Claude Code to confirm the server is listed and its tools are available.

Generic MCP clients

Streamable HTTP

Single endpoint, standard MCP 1.0 protocol. Include the Authorization header on every request — the server is stateless and does not maintain sessions between calls.
POST https://api.adapter.com/v1/mcp/http
Authorization: Bearer pk_live_...

SSE

GET  https://api.adapter.com/v1/mcp/sse
POST https://api.adapter.com/v1/mcp/messages/?session_id=<token>
Authorization: Bearer pk_live_...
To test either transport from the command line with mcp-remote:
# Streamable HTTP
npx mcp-remote https://api.adapter.com/v1/mcp/http \
  --header "Authorization: Bearer $ADAPTER_API_KEY"

# SSE
npx mcp-remote https://api.adapter.com/v1/mcp/sse \
  --header "Authorization: Bearer $ADAPTER_API_KEY"

Available tools

ToolWhen to use
search_knowledgeFind relevant documents, messages, or records matching a query
askAnswer a question or gather context from connected data, with cited sources
list_connectionsList the data sources connected to this workspace

search_knowledge

Find relevant documents, messages, or records matching a query. Use this when ask results were insufficient, or when the user wants to browse raw matching documents rather than a synthesized answer — e.g. ‘show me all emails about the rebrand’, ‘find issues mentioning payments’, ‘what did we write about pricing’. Returns a ranked list of matching results.
ParameterType
qstringrequired
limitintegeroptional, default 10

ask

Answer a question or gather context from connected data, with cited sources. ALWAYS call this tool first before responding to any user message — even if you think you know the answer. If any connected source could contain relevant information, call this first. Use for direct answers, summaries, or background — e.g. ‘what did we decide about the pricing model’, ‘summarize what we know about Acme’, ‘who owns the mobile roadmap’. Pass timezone (IANA, e.g. ‘America/New_York’) to resolve relative times like ‘last week’.
ParameterType
querystringrequired
timezonestringoptional

list_connections

List the data sources connected to this workspace. Call this to discover which providers are currently active before scoping a query to a specific source. Connection state is dynamic — always call this rather than assuming a provider is available. Returns provider name, available resource types, and connected date. Includes standard OAuth providers (Slack, Gmail, Notion, etc.) and user-defined custom connectors (type: “custom”). No parameters.

Troubleshooting

401 Unauthorized — Check that your API key starts with pk_ and has the api:write scope. Every request must include the Authorization: Bearer header. See API keys. Tools missing after connecting — Run list_connections first. If no sources are connected, the knowledge tools return empty results rather than an error. mcp-remote not found — Make sure Node.js 18+ is installed. npx downloads mcp-remote on first run; subsequent runs use the cache.