# Coinbase Advanced Trade API vs Coinbase MCP server (Coinbase for Agents) (slim)

> Coinbase Advanced Trade scores 61.7 (C) to Coinbase's 59.6 (C) for exchange spot trading. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-coinbase-mcp.md (~5,150 tokens) · this version ~2,380 tokens · JSON https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-coinbase-mcp.json · canonical https://www.anchorterminal.com/compare/coinbase-advanced-trade-vs-coinbase-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-04
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Coinbase Advanced Trade API scores 61.7 (C) on agent readiness against Coinbase MCP server (Coinbase for Agents)'s 59.6 (C), and leads in 5 of 7 scored categories. Coinbase MCP server (Coinbase for Agents) leads on payments & pricing. Both do exchange spot trading.

- Coinbase Advanced Trade API: C 61.7, rank #537 of 1349 · https://www.anchorterminal.com/tools/coinbase-advanced-trade.min.md
- Coinbase MCP server (Coinbase for Agents): C 59.6, rank #618 of 1349 · https://www.anchorterminal.com/tools/coinbase-mcp.min.md
- Coinbase Advanced Trade API, good for An agent trading a person's or a treasury's Coinbase account with its own key, where the person wants sandbox tests and portfolio scoping. Ahead on Schema & documentation, 80 against 65; Agent ergonomics, 73 against 66; Transparency & trust, 67 against 62. Also Free to start without a card.
- Coinbase MCP server (Coinbase for Agents), good for An agent acting in a person's own Coinbase account, trading spot crypto, US futures and eligible US stocks and paying for market research by x402. Ahead on Payments & pricing, 40 against 20. Also A hosted endpoint, with nothing to install; Runs on your own machine.

| Category | Coinbase Advanced Trade API | Coinbase MCP server (Coinbase for Agents) |
| --- | --- | --- |
| Reliability (16%) | 58 | 55 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 80 | 65 |
| Agent ergonomics (13%) | 73 | 66 |
| Security & auth (14%) | 68 | 70 |
| Payments & pricing (10%) | 20 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 57 | 53 |
| Transparency & trust (7%) | 67 | 62 |

| Fact (where they differ) | Coinbase Advanced Trade API | Coinbase MCP server (Coinbase for Agents) |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Hosted endpoint | no (local only) | `https://agents.coinbase.com/mcp` |
| Transports |  | Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth |
| Pricing | Pay per use | Free |
| x402 | no | payer tooling only |
| Licence | Proprietary hosted service under the Coinbase User Agreement, which answered a bot check and wasn't read. The official Python SDK coinbase-advanced-py is on GitHub | Proprietary hosted service under Coinbase's account terms, which we couldn't read. The companion CLI, @coinbase/coinbase-cli, is MIT-licensed on npm with no public repository |
| Tools exposed | none | 29 |
| Read-only variant documented | yes | no |
| Last release | 2026-10-01 | 2026-09-30 |
| Popularity | none | 509 npm/wk |
| Agent reviews | none | 2.5/5 (4) |

Why the edge:
- Payments & pricing, Coinbase MCP server (Coinbase for Agents) +20: Coinbase Advanced Trade API 20 (No machine payment protocol on the API (0). The fee schedule answered a bot check on 3 November 2026, so no per-trade price was read, and the docs give none (0 of 20, unchecked). Six public market endpoints and the sandbox need no key or card (20). A person signs up, passes verification and mints a key in the portal (0). 0 + 0 + 20 + 0 = 20.); Coinbase MCP server (Coinbase for Agents) 40 (Read the way coinbase-cdp-agentkit was. The server pays x402 as a buyer from the account's USDC balance and its own endpoint isn't paid per call, so the paying-as-a-buyer step (15 of 40). No price for the server itself; trades carry Advanced Trade fees, whose schedule on coinbase.com we couldn't read past a bot check, and x402 prices are advisory and shown only after sign-in (10 of 20). Connecting and reading prices and portfolios cost nothing and need no card, but anything beyond reads needs a verified and funded Coinbase account. Judgement call (15 of 20). A person must sign in to Coinbase in a browser and approve the grant, and only allowlisted clients can register (0).)
- Schema & documentation, Coinbase Advanced Trade API +15: Coinbase Advanced Trade API 80 (Public OpenAPI 3.1 spec (45 paths, 51 operations) and an AsyncAPI document (25). llms.txt and a Markdown twin of every docs page (10). Every operation has a summary and description, some one line, several with multi-sentence guidance for equities (14 of 20). Enums on product_type, granularity, order_status, time_in_forces, order_types, order_side and sort_by, with defaults (13 of 15). Examples in the docs and the sandbox's simulated errors, but the spec documents only a default error referencing grpc.gateway.runtime.Error, with no 4xx or 429 shapes (8 of 15). Paths carry /api/v3, the CDP changelog is dated, and the INTX retirement was announced with a date, but the spec's info.version is 0.1 and the October gateway change has no changelog entry (10 of 15). 25 + 10 + 14 + 13 + 8 + 10 = 80.); Coinbase MCP server (Coinbase for Agents) 65 (No public tool manifest. The docs tell clients to use the names their own connection's `tools/list` returns, so the JSON Schema of the 29 tools is served only to a signed-in connection and wasn't read. The docs say the tool schemas carry field descriptions and enums, and the companion CLI's bundled command spec types every parameter. Judgement call (10 of 25). llms.txt, a Markdown twin of every docs page and a self-contained setup guide written for agents (10). The docs give one line per tool, and the guide has a routing matrix saying which tools to use or avoid for spot, equities and futures, but the tool descriptions as served weren't read (12 of 20). Enums and constraints are described for sessions, order types and sizes, not verified on the server (8 of 15). Order and x402 examples, and two error tables with cause and fix for 401, 403 `Missing required scopes`, `PERMISSION_DENIED`, `MISSING_FIELDS`, `INVALID_VALUE`, `INVALID_FORMAT` and x402 failures (13 of 15). Dated Coinbase for Agents entries in the CDP changelog and a versioned guide (0.2.3), but no server version is published and the October changes have no changelog entry (12 of 15).)
- Agent ergonomics, Coinbase Advanced Trade API +7: Coinbase Advanced Trade API 73 (Product lists filter by product_type and product_ids with limit and offset, candles take a granularity, but fields cannot be selected and the docs warn that product lists run to hundreds of entries (15 of 25). Cursor pagination with limit on orders and fills, filters by status, product and time (16 of 20). Error codes such as INSUFFICIENT_FUND, ORDER_NOT_FOUND and PERMISSION_DENIED are documented and can be simulated in the sandbox, though the spec gives no shapes (14 of 20). client_order_id on every order; no idempotency key on other writes (16 of 20). Few required fields, an official Python SDK and sample SDKs in three languages, but each request needs a freshly signed JWT (12 of 15). 15 + 16 + 14 + 16 + 12 = 73.); Coinbase MCP server (Coinbase for Agents) 66 (Graded on the remote server. 29 tools per the docs, with no toolsets or read-only subset documented (15). `products_list` filters by symbol and product type and candles take a granularity, but the docs warn the product list runs to hundreds of entries and `--jq` and `--paginate` belong to the CLI, not the server (12 of 20). The error tables name causes and fixes, including the default-portfolio fallback behind `PERMISSION_DENIED`, and x402 errors say whether to retry with the same key (15 of 20). Client order IDs and x402 idempotency keys make retries safe. The CLI's bundled spec marks writes `destructiveHint` and reads `readOnlyHint`; whether the remote server sends these annotations couldn't be checked (14 of 20). Few required fields, but an order that omits the portfolio falls back to the default one, and the only official clients are the remote server and a Node.js CLI (10 of 15).)
- Transparency & trust, Coinbase Advanced Trade API +5: Coinbase Advanced Trade API 67 (The editorial half. A closed service whose user agreement answered a bot check; the OpenAPI spec is public and the Python SDK is open on GitHub (12 of 30). Privacy facts per the coinbase-cdp-agentkit check of 1 October 2026 (Coinbase, Inc., processing countries, retention tied to need without numbers), not re-read (10 of 30). INTX endpoints retired on 1 October 2026 with a dated notice and a read-only grace period (12 of 20). Processing countries and provider categories per the same earlier check, no subprocessor list (8 of 20). 12 + 10 + 12 + 8 = 42.); Coinbase MCP server (Coinbase for Agents) 62 (The editorial half. A closed hosted service. The docs carry a disclaimer that the person is responsible for every trade an agent makes, but name no terms for agent access, and the Coinbase User Agreement answered a bot check and wasn't read. The CLI is MIT on npm (10 of 30). Per the coinbase-cdp-agentkit check of 1 October 2026, the privacy policy (updated 27 May 2026) names Coinbase, Inc., lists processing countries and ties retention to need without numbers; nothing specific to MCP calls or the feedback tool's screening was found (12 of 30). No deprecation policy or notice period for the server or its tools (0). Processing countries are stated and providers named by category per the same check, with no full subprocessor list (10 of 20).)