https://mcp.abacuslabs.ai/mcp (streamable HTTP; https://mcp.abacuslabs.ai works too).
Auth: the header Authorization: Bearer <key>, with the same key as the REST API. Get one with POST /v1/keys (Keys and limits). Every client must send this header: there is no OAuth sign-in yet, so connectors that only sign in with OAuth (claude.ai, the ChatGPT app) cannot connect today.
Tools
Arguments are the REST body fields, at the top level of the tool call, with these differences:
abacus_commit takes idempotency_key as a required argument (the REST header) and has no on_stale; abacus_analyze, abacus_propose, abacus_check_trades and abacus_create_account take an optional idempotency_key (a retry with the same key returns the first result with idempotent_replay: true and credits_charged: 0; a key used over REST and over MCP counts as two requests); abacus_get_proposal returns at once (no wait), so pause a few seconds between polls; abacus_create_account takes the POST body as account; abacus_patch_account takes the PATCH body as changes; ids that are in the REST path (proposal_id, commit_id, account_id) are arguments. Results are the REST JSON. Credits are the same as REST; read credits_charged in the result (MCP has no response headers).
Errors. An API error is a tool result with isError: true. Its text is Error executing tool <name>: followed by the REST error JSON, so parse the JSON from the first {:
request_id is null. A missing or wrong argument type is caught by the MCP layer first: its text is a plain validation message, not JSON (1 validation error for abacus_get_commitArguments commit_id Field required ...).
Claude Code
claude mcp list then shows abacus: https://mcp.abacuslabs.ai/mcp (HTTP) - ✔ Connected.
Claude API (MCP connector)
OpenAI Responses API
"require_approval": "always" (or approve abacus_commit yourself) if a person must confirm each commit.
Cursor
In~/.cursor/mcp.json (or .cursor/mcp.json in a project):
Claude Desktop and claude.ai
Custom connectors in claude.ai and the Claude apps sign in with OAuth, which Abacus Labs does not offer yet, so claude.ai cannot connect today. In Claude Desktop, use themcp-remote bridge (needs Node.js) in claude_desktop_config.json, then restart Claude Desktop:
ChatGPT
ChatGPT connectors also sign in with OAuth, so the ChatGPT app cannot connect yet. From code, use the OpenAI Responses API above.Verified on 2026-11-14: Claude Code, the Claude API MCP connector and the OpenAI Responses API. The MCP Python SDK example below was run again on 2026-11-15 (SDK 2.3.0). Not verified by us: Cursor and the Claude Desktop bridge (both follow those tools’ documented formats).
Your own MCP client
Any streamable HTTP client works. With the official Python SDK:result.is_error == True.
GET https://api.abacuslabs.ai/mcp.json returns the tool list and a client config snippet: use its hosted entry. (Its stdio and start_http entries are for running the server from the Abacus Labs source, which is not public.)