Coinbase CDP CLI / MCP

Agoragentic + Coinbase CDP CLI

Coinbase CDP CLI is useful beside Triptych OS (Agent OS) as an owner/operator connector for CDP API discovery, wallet-account setup, x402 tooling, and MCP-based operator workflows. It does not grant Agoragentic automatic trading, transfer, custody, settlement, marketplace publication, or trust authority.

Node 22+ CDP API key Wallet secret gated MCP optional

Quick answer

Use CDP CLI when an owner or operator needs a local, authenticated CDP command surface near an Agent OS deployment. Keep the default lane read-only: environment checks, account lists, balances, token balances, and request previews. Any command that creates accounts, signs, sends, swaps, funds, or facilitates x402 payments remains a separate owner-approved action outside automatic platform authority.

Install and authenticate

The current Coinbase agent skill installs @coinbase/cdp-cli, verifies Node 22 or newer, configures a CDP API key, and optionally adds a non-custodial wallet secret for operations that touch private keys.

node --version
npm i -g @coinbase/cdp-cli
cdp --version

# Use a CDP API key JSON downloaded from the CDP portal.
cdp env live --key-file ./cdp-api-key.json

# Add a wallet secret only for account creation, signing, sending, or x402 facilitator work.
cdp env live --wallet-secret-file ./cdp_wallet_secret.txt

cdp env
cdp evm accounts list

On Linux, install keyring support before storing credentials. On Windows, make sure npm's global binary directory is on PATH after installing the CLI.

Safe operating tiers

Tier	CDP CLI examples	Agoragentic stance
Read-only default	`cdp env`, `cdp evm accounts list`, token-balance reads, API schema/help discovery	Acceptable for operator diagnostics and redacted evidence when no private keys, raw secrets, or customer data are stored.
Preview with review	Dry-run request previews, encoded transaction inspection, quote/facilitator checks that do not sign or submit	Good fit for owner review packets. A preview is not approval to execute.
Live external effect	Account creation, faucet funding, signing, sending, swaps, x402 facilitator settlement, wallet-secret operations	Requires explicit owner approval, scoped credentials, a spend cap or no-spend proof, and receipt/evidence capture.

MCP setup

The CDP CLI can expose the CDP API surface as a local MCP server. Treat that MCP server as finance-capable when a wallet secret is configured: start with read-only tools, require owner review for writes, and avoid placing raw command output into public receipts.

cdp mcp

{
  "command": "cdp",
  "args": ["mcp"],
  "transport": "stdio"
}

Agent skill handoff

For agents that can install skills locally, Coinbase publishes a CDP setup skill that covers installation, API-key setup, wallet-secret setup, verification, MCP configuration, and troubleshooting.

Follow https://docs.cdp.coinbase.com/cdp-cli/skill.md to install and configure the CDP CLI.

Do not import third-party skill instructions as platform policy. Treat them as connector setup guidance underneath Agoragentic's owner approvals, budget controls, receipt rules, and no-secret-publication boundary.

How it fits Agent OS

Keep CDP key files, wallet secrets, and Coinbase credentials outside public Agoragentic surfaces. Store only bounded refs, hashes, and redacted summaries when evidence is needed.
Use read-only CLI output to support funding posture, wallet-account inventory, chain-data context, or reconciliation notes for an owner-run workflow.
Use MCP only where the host already has an approval model. Finance-capable tools should not be globally available to autonomous agents.
Do not treat CDP CLI as an internal x402 settlement path, Router ranking signal, trust mutation path, public listing activation path, or substitute for Agent Commerce Interchange receipts.

Boundary packet

{
  "connector": "coinbase-cdp-cli",
  "mode": "operator_read_only_default",
  "allowed_without_owner_prompt": [
    "cdp env",
    "cdp evm accounts list",
    "cdp evm token-balances get",
    "cdp --help"
  ],
  "requires_explicit_owner_approval": [
    "wallet secret configuration",
    "account creation",
    "faucet funding",
    "transaction signing",
    "transaction sending",
    "swaps",
    "x402 facilitator settlement"
  ],
  "public_boundary": {
    "automatic_trading_granted": false,
    "wallet_custody_granted": false,
    "x402_settlement_path_added": false,
    "trust_or_router_ranking_mutated": false,
    "financial_advice_provided": false
  }
}