
Circle Agent Stack Mcp
- 1 repo stars
- Updated June 4, 2026
- kinance/circle-agent-stack-mcp
circle-agent-stack-mcp is an MCP server that lets agents manage Circle USDC wallets, enforce spend policies, send transfers, and use x402 nanopayments.
About
Circle Agent Stack MCP exposes Circle’s agent-oriented payments surface—USDC wallets, spend policies, transfers, and x402 nanopayments—to Claude Code, Cursor, and other MCP clients. developers shipping autonomous or semi-autonomous agents use it in Build when integrating real money movement instead of mock billing. The server ships as an npm stdio package at version 0.1.1 with a required secret CIRCLE_API_KEY, so setup is closer to fintech integration than a no-key demo. Intermediate complexity reflects policy design, testnet versus mainnet discipline, and compliance awareness. It fits agent marketplaces, paid API routers, and usage-based agent products more than static SaaS without on-chain or stablecoin flows. Register the server in your agent config, scope policies tightly, and test spend limits before any production agent loop.
- USDC wallet operations for AI agents via stdio MCP (npm package circle-agent-stack-mcp)
- Spend policies to cap autonomous agent spending
- Transfers and programmable money movement from the agent session
- x402 nanopayment support for machine-to-machine micropayments
- Requires CIRCLE_API_KEY from developers.circle.com
Circle Agent Stack Mcp by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --env CIRCLE_API_KEY=YOUR_CIRCLE_API_KEY circle-agent-stack-mcp -- npx -y circle-agent-stack-mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| repo stars | ★ 1 |
|---|---|
| Package | circle-agent-stack-mcp |
| Transport | STDIO |
| Auth | Required |
| Last updated | June 4, 2026 |
| Repository | kinance/circle-agent-stack-mcp ↗ |
What it does
Give coding agents programmatic USDC wallets, spend limits, transfers, and x402 nanopayments through Circle’s Agent Stack via MCP.
Who is it for?
Best when you're creating agents that must pay for APIs, settle micropayments, or operate custodied USDC with explicit spend caps.
Skip if: Products with no stablecoin or Circle stack requirement, or teams unwilling to manage API keys and financial compliance.
What you get
After registration with a Circle API key, your agent can execute policy-bound USDC wallet actions and nanopayments from the MCP tool surface.
- Agent-callable wallet, transfer, and policy tools via MCP
- x402 nanopayment-capable agent payment path
- Documented Circle API integration for agent runtimes
By the numbers
- Package version 0.1.1 with stdio transport via npm identifier circle-agent-stack-mcp
- One required secret environment variable: CIRCLE_API_KEY
README.md
circle-agent-stack-mcp
MCP server for Circle's Agent Stack. Create wallets, set spend policies, send USDC, and pay x402-priced endpoints — all from a tool call.
npx circle-agent-stack-mcp
Tools
| Tool | What it does |
|---|---|
circle_wallet_create |
Create an agent wallet (dev/hosted/smart) |
circle_wallet_list |
List wallets with USDC balances |
circle_balance |
Balance + last 10 txns for a wallet |
circle_policy_set |
Set daily cap, x402 cap, allow/block lists |
circle_transfer_usdc |
Send USDC to an on-chain address |
circle_x402_pay |
Pay an x402-priced endpoint and return its response |
Quickstart
You need the Circle CLI installed and authenticated:
npm install -g @circle-fin/circle-cli
circle login
export CIRCLE_API_KEY=your_key_here
Claude Desktop
{
"mcpServers": {
"circle": {
"command": "npx",
"args": ["-y", "circle-agent-stack-mcp"],
"env": {
"CIRCLE_API_KEY": "your_key_here"
}
}
}
}
Claude Code
claude mcp add circle -- npx -y circle-agent-stack-mcp
Example
You: Create a dev wallet called eva-treasury, set a $5 daily cap and $0.10 x402 cap,
then fetch today's BTC signal from the x402 endpoint at https://signals.example.co/btc
Claude:
→ circle_wallet_create("eva-treasury", type="dev")
{ wallet_id: "wal_abc123", address: "0x..." }
→ circle_policy_set("wal_abc123", daily_cap_usdc=5, x402_cap_usdc=0.10)
{ status: "applied" }
→ circle_x402_pay("wal_abc123", "https://signals.example.co/btc", max_price_usdc=0.10)
{ signal: "LONG", confidence: 0.72, price_paid_usdc: 0.05 }
Today's BTC signal: LONG (72% confidence). Paid $0.05.
Self-hosting with x402 paywall
http-server.ts wraps the same tools behind an x402 paywall — agents pay per call in USDC rather than using an API key. Useful if you want to expose Circle tooling as a paid service.
CIRCLE_PAYOUT_ADDRESS=0x... npm run start:http
To test the x402 flow locally, run the toy demo server in examples/x402-demo-server.mjs.
How it works
v0.1 shells out to the Circle CLI for all operations. This keeps auth handling out of this repo and avoids reimplementing the API client before the tool surface is validated. v0.2 will switch to direct HTTP via @circle-fin/circle-sdk.
Security
Your Circle API key has spend authority. Always:
- Set
daily_cap_usdcbefore enabling automated payments - Start on
type="dev"wallets, not mainnet - Review the
allowlistbefore moving to production - Don't commit
CIRCLE_API_KEY
Roadmap
-
circle_nanopayment_stream— streaming x402 payments for per-token billing -
circle_skills_list/circle_skills_call— Circle Skills marketplace - Direct HTTP API mode (v0.2) — remove CLI dependency
- Multi-chain — EURC, CCTP cross-chain transfers
Related
Recommended MCP Servers
How it compares
Payments and wallet MCP integration, not a generic Stripe checkout skill or internal doc RAG.
FAQ
Who is circle-agent-stack-mcp for?
Developers and small teams building AI agents that need real USDC wallets, transfers, and spend policies through Circle’s Agent Stack.
When should I use circle-agent-stack-mcp?
Use it during Build when integrating agent payments, x402 nanopayments, or policy-limited spending—not for offline product research alone.
How do I add circle-agent-stack-mcp to my agent?
Install the npm package circle-agent-stack-mcp, set CIRCLE_API_KEY in your MCP server environment, and add the stdio server block to Claude Code, Cursor, or your MCP host config.