Point your AI at us. Go make coffee.

1. Install and sign in (first time only) — the CLI keeps its own login even if you use the desktop app.

   Copynpm install -g @anthropic-ai/claude-code
   claude /login

2. Register the connector. User scope means it works from any directory. Keep it on one line — a wrapped paste can mangle the key.

   Copyclaude mcp add --scope user --transport http converse https://wtfapi.serviceproof.net/mcp --header "Authorization: Bearer YOUR_API_KEY"

3. Skip the per-tool prompts (optional, recommended — there are hundreds of tools). One server-level rule allows them all:

   Copy// ~/.claude/settings.json
   { "permissions": { "allow": ["mcp__converse"] } }

4. Say hello.

   Copyclaude "You're connected to Listrak Converse over MCP. Call docs_index, read Getting-Started and Conventions, then call get_entity_dictionary and list_contexts and tell me what this tenant's world looks like."

WSL: the Windows and WSL CLIs keep separate configs. Register — and log in — in the environment your sessions actually run in, or in both.

1. Open a terminal — PowerShell on Windows, Terminal on macOS — and run the Claude Code steps above (claude /login, then the one-line claude mcp add --scope user).
2. Add the allow rule to ~/.claude/settings.json — on Windows that is C:\Users\<you>\.claude\settings.json.
3. Restart the app. Every new session — and every Cowork task on that machine — now has the tools. Type /mcp in a session to browse them.

Register once, use everywhere: you do not repeat this per project. User scope is machine-wide.

Copy{
  "tools": [{
"type": "mcp",
"server_label": "converse",
"server_url": "https://wtfapi.serviceproof.net/mcp",
"headers": { "Authorization": "Bearer YOUR_API_KEY" }
  }]
}

Zero client code — the model gets the tool surface on the request. Same role gating, same audit trail.

Run Claude Code inside the Repl. In the Repl shell, the identical walk-through — npm install -g @anthropic-ai/claude-code, claude /login, then the one-line claude mcp add --scope user. Your in-Repl assistant now drives the platform.

Or the agent you are BUILDING — anywhere you call the Anthropic API, the Messages API has a native MCP connector:

Copyimport anthropic
client = anthropic.Anthropic()
response = client.beta.messages.create(
model="claude-sonnet-5",
max_tokens=2048,
betas=["mcp-client-2025-04-04"],
mcp_servers=[{
    "type": "url",
    "url": "https://wtfapi.serviceproof.net/mcp",
    "name": "converse",
    "authorization_token": "YOUR_API_KEY",
}],
messages=[{"role": "user", "content":
    "Study this Listrak Converse tenant and summarize what it can do."}],
)

Cursor, LangChain and LlamaIndex MCP adapters, the Agent SDKs, a client you wrote yourself — the contract is the URL plus the Authorization: Bearer header, and nothing else.

Protocol notes for client authors. Stateless Streamable HTTP: POST /mcp with a JSON-RPC 2.0 message returns application/json; notifications get 202 with no body; GET returns 405 (no server-initiated stream) and DELETE returns 204 (no session to end). No Mcp-Session-Id is issued or required. Methods: initialize, tools/list, tools/call, ping — and initialize echoes whatever protocolVersion you ask for.

Errors are split deliberately. Protocol problems are JSON-RPC errors; tool failures are not — tools/call returns isError: true with a readable message, so the model can read it and self-correct. Auth failures are plain HTTP 401.

HTTP/1.1 401 Unauthorized
WWW-Authenticate: Bearer realm="Listrak Converse MCP",
              resource_metadata=".../.well-known/oauth-protected-resource"

That pointer resolves to an unauthenticated RFC 9728 Protected Resource Metadata document, so a connector UI can tell “send a bearer key” apart from “this wants OAuth” and from “your key is wrong” — and say something useful to the person instead of just failing.

authorization_servers is deliberately absent: we do not run an authorization server yet, and advertising one would send an OAuth-capable client into a dead end rather than letting it fall back to the bearer key that works. When the OAuth flow ships, that one field appears and the same clients begin negotiating with no other change.