Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Circle Agent Stack for AI agents: USDC wallets, spend policies, transfers, and x402 nanopayments.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
CIRCLE_API_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"circle-agent-stack": {
"command": "npx",
"args": [
"-y",
"circle-agent-stack-mcp"
],
"env": {
"CIRCLE_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add circle-agent-stack --env CIRCLE_API_KEY=your-value -- npx -y circle-agent-stack-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"circle-agent-stack": {
"command": "npx",
"args": [
"-y",
"circle-agent-stack-mcp"
],
"env": {
"CIRCLE_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"circle-agent-stack": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"circle-agent-stack-mcp"
],
"env": {
"CIRCLE_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified with the GitHub account kinance, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: CIRCLE_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 5 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, dotnet-mcp
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
MCP server for .NET symbols, XAML, source generators, and restricted workspace edit
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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
| 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 |
You need the Circle CLI installed and authenticated:
npm install -g @circle-fin/circle-cli
circle login export CIRCLE_API_KEY=your_key_here
{
"mcpServers": { "circle": { "command": "npx", "args": ["-y", "circle-agent-stack-mcp"], "env": { "CIRCLE_API_KEY": "your_key_here" } } } }
claude mcp add circle -- npx -y circle-agent-stack-mcp
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.
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.
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.
Your Circle API key has spend authority. Always:
daily_cap_usdc before enabling automated paymentstype="dev" wallets, not mainnetallowlist before moving to productionCIRCLE_API_KEYcircle_nanopayment_stream — streaming x402 payments for per-token billingcircle_skills_list / circle_skills_call — Circle Skills marketplace