@conto_finance/mcp-server package gives one payment agent tools to check balances, request payments, read transactions, and query analytics in Claude Desktop, Claude Code, and other MCP clients.
Conto checks each payment request against the agent’s policies, then approves it, denies it, or holds it for a person. Conto sends an approved payment from a managed wallet. External wallets use approve, your own transfer, then confirm, and sandbox payments are simulated. See wallet custody and MCP tools.
Sign in to manage your agents
Use the account connection to manage agents across a workspace with your own Conto permissions. Add the hosted server, then sign in through the browser, complete MFA if enabled, select your workspace, and review the requested access. No agent registration or SDK key is needed.- Codex
- Claude Code
agent_id. A change returns a Conto review link, and the client checks
the result after an eligible person confirms the exact change in the browser.
- Scopes:
conto:read, plusconto:proposeto propose changes.offline_accessrefreshes tokens without a new sign-in. - Lifetimes: access tokens last one hour. A connection lasts 30 days.
- Checked on each request: your current membership and role. Role changes apply on the next request.
- Access ends when the member is removed, the account is suspended, the password is reset, or the app is disconnected. It also ends when the organization starts requiring SSO or two-step verification that the approving session did not meet. Approve it again from a session that does.
- Disconnect at Settings → Profile → Connected apps.
Let a client pay as one agent
Hosted pay is rollout-controlled. If the pay endpoint returns 404, use the agent SDK connection for payments. The paying connection has its own address, so adding the account connection never asks for payment access. Add it as a second server, sign in, and choose the agent it pays as. Owners, Admins and Managers can connect a paying agent. Owners and Admins can also create a new agent on the same screen.- Codex
- Claude Code
- Payments: wallet payments only. Each one runs through the agent’s policies, limits, budgets and approvals, exactly as with that agent’s SDK key. A payment held for review waits for a person in Conto. The connection can’t approve or confirm payments.
- Scopes:
conto:readandconto:pay.offline_accessrefreshes tokens without a new sign-in. - Lifetimes: access tokens last one hour. A paying connection lasts 7 days, then you connect again.
- Checked on each request: your current role, the agent’s status, and the connection’s key. The connection ends if your role can no longer change agents.
- On the agent’s page: the connection shows as an SDK key named after the client, with its usage and last use. Revoke it there to disconnect, or at Settings → Profile → Connected apps.
- Not included: cards, store checkout, x402, MPP, agent-to-agent payments and bill pay. Use the agent SDK connection for those.
untrustedFields so the client’s model treats it as data. See paying tools.
Dashboard alternatives
To work in the dashboard instead of an MCP client, use the dashboard assistant or Conto Pay.Agent SDK connection prerequisites
- An MCP client, such as Claude Desktop or Claude Code
- A Conto agent SDK key (
conto_agent_...). In the dashboard, open Agents, select the agent, open the Connect tab, and choose Generate SDK key. - Node.js 20.19+, with Node.js 22 requiring 22.12+ and Node.js 23 requiring 23.2+, because the server runs through
npx
Add the server
In each config below, replaceconto_agent_xxx... with your SDK key.
- Claude Code
- Claude Desktop
Configuration reference
Leave the
CONTO_BROWSER_* settings unset unless you run a guarded browser runtime. See
guarded browser checkout for the tools they add.
The CONTO_LINK_* settings add no tool and never make the server issue cards. They let
checkout_checkpoint_cancel close a request made through Conto’s integration with
Stripe Link. Install link-cli on the server’s PATH and sign it in with
link-cli auth login. If CONTO_LINK_WALLET is set and link-cli is missing, the server logs a
warning at startup. From MCP server 0.7.2, a cancel that cannot reach Link keeps the spend held.
Guarded browser runtime settings
Guarded browser runtime settings
CONTO_BROWSER_RUNTIME_URL and CONTO_BROWSER_RUNTIME_TOKEN enable guarded_browser_checkout.
Set both or neither. With only one set, the server exits at startup. The token must contain at
least 32 characters and be a dedicated service credential. Conto API keys are rejected. The
observation and sessions URLs must be on the same origin as the runtime URL and distinct from it.
The browser runtime must own the page and must be the agent’s only route to payment-sensitive
click or submit actions. Use createGuardedPlaywrightCheckoutHttpHandler from
@conto_finance/sdk/playwright to mount the authenticated endpoint the MCP server calls around
your guarded Playwright runtime.Next steps
MCP tools
Full tool list, parameters, and responses
Set up with the CLI
Create an agent, wallet, and SDK key in one command