Public beta · MCP 1.0 · OAuth 2.1

Coinpay,
now agent-native.

An MCP server for every side of crypto commerce — let merchants run their account from Claude, give buyer-side agents a way to pay, and ship Coinpay integrations from Cursor in one prompt.

Connect your AI See it in action
3 servers · merchant · agent · dev OAuth 2.1 · scoped, revocable SSE + stdio transports
Claude · merchant
Buyer-agent · spending
Cursor · building
Three MCP servers

One protocol.
Three audiences.

MCP isn't one product. We ship a server tuned for each side of the table — what your AI is allowed to do depends on whose keys it's holding.

Live · GA

Merchant MCP

Run Coinpay from your AI of choice. Generate links, refund a charge, check yesterday's BTC volume, push a payout to your bank — all with the same scopes you'd give a teammate.

› "Refund the £24 charge from yesterday."
› "Send a payment link for £180 to acme@…"
› "What did I take in crypto last week?"
Beta · agent commerce

Agent Wallet MCP

The buyer-side rail. Give an agent a Coinpay wallet, a spend ceiling, and a policy — it pays for SaaS, APIs, and physical goods on your behalf. Receipts come back signed and reconciled.

spend.cap £500 / day
policy whitelist · receipts · 2FA > £50
settle USDC · instant
Free · public

Developer MCP

Our public API spec, examples, error codes, and recipe library — exposed as MCP resources. Point Cursor or Claude Code at it and ship a Coinpay integration in one conversation.

$ claude mcp add coinpay-dev
✓ 84 endpoints indexed
✓ 312 examples ready
→ "Add Coinpay checkout to this Next.js app"
Live demo · merchant MCP

Watch an AI run a refund.

Real prompts, real tools, real signed responses. Switch the prompt to see how the agent picks tools, asks for confirmation on writes, and emits an audit trail.

Conversation Claude · merchant.acme
Audit trace
Tool catalogue · merchant server

What your AI can actually do.

37 tools, grouped into seven domains. Read scopes are granted per-session; write scopes require explicit user approval and a fresh OAuth challenge.

read

Payment links & invoices

Mint shareable links, draft and send invoices, attach line items, expire stale links.

links.createlinks.listinvoices.draftinvoices.send
read

Balances & payments

Query balances per-asset, look up charges, filter by date or customer, expand line items.

balance.getcharges.listcharges.retrieve
write · payouts

Payouts

Trigger payouts to a connected bank, exchange, or self-custody wallet. 2FA challenge over £500.

payouts.createpayouts.estimatedestinations.list
read

Products & catalog

List, create, and update SKUs. Bulk-edit prices, attach images, sync to Shopify or Woo.

products.listproducts.upsertprices.update
write

Refunds & voids

Issue partial or full refunds, void uncaptured charges. Idempotency keys auto-attached.

refunds.createcharges.void
read

Analytics

Revenue by day, top customers, asset mix, conversion funnel. Returns CSV or structured.

reports.revenuereports.customersreports.assets
write · admin

Sub-accounts & teammates

Create sub-accounts, invite teammates, scope permissions per-role. Full audit log.

accounts.createmembers.inviteroles.set
read

Customers & sessions

Look up customers, replay a payment session, inspect risk score and chain provenance.

customers.getsessions.replay
write · keys

API keys & webhooks

Rotate API keys, register/test webhook endpoints, replay missed events with proof.

keys.rotatewebhooks.createwebhooks.replay
Connect your client

Three commands. Then talk.

Pick your client, paste the snippet, finish the OAuth handshake. The MCP server discovers itself — no manual tool wiring.

1
Open your client's MCP config

In Claude Desktop, hit ⌘ , → Developer → Edit Config.

~/Library/Application Support/Claude/claude_desktop_config.json
2
Paste the Coinpay server entry

Copy the snippet on the right. The transport, URL, and OAuth callback are all wired up — you only need a Coinpay account.

3
Authorise & pick scopes

Restart the client. It opens mcp.coinpay.com/authorize. Tick the scopes you want — read, write, payouts, admin — and approve.

4
Talk to your business

Try: "What did I take in BTC last week, and which products drove it?"

claude_desktop_config.json
Agent Wallet · beta

Buyer-side agentic commerce.

When the AI is the customer. Coinpay issues a programmable wallet; you keep the rules; the agent transacts within them.

For your agent

Spend with policy,
not panic.

  • Per-day, per-merchant, and per-category caps.
  • Whitelist domains and merchant IDs; auto-2FA above thresholds.
  • Pay in USDC, BTC, or fiat-rail — settle in your reporting currency.
Read the agent docs
For your storefront

Accept agent traffic.
Reconcile cleanly.

  • An x-agent-receipt header on every charge.
  • Verified agent identity, signed by Coinpay's KMS.
  • Higher conversion: agents fail fast, retry deterministically.
Enable agent payments
FAQ

Questions, answered.

The technical edges. If anything's missing, ask mcp@coinpay.com.

What is MCP, exactly?
Model Context Protocol — an open standard from Anthropic for connecting AI assistants to external tools and data. Clients (Claude, ChatGPT, Cursor) speak MCP; servers expose tools, resources, and prompts. Coinpay runs three servers, each scoped for a different audience.
How is auth handled?
OAuth 2.1 with PKCE. Tokens are short-lived (15 min) and refresh-rotated. Scopes are explicit: read, write, payouts, admin. You can revoke any session from the Coinpay dashboard, and any tool call above £500 triggers a fresh user challenge.
Which transports are supported?
SSE over HTTPS for hosted clients (default), stdio for local development, and streamable HTTP for clients that prefer it. Heartbeats every 15s; reconnect with exponential backoff.
What are the rate limits?
120 tool calls/min per token (read), 30/min (write), 6/min (payouts). Headers: x-ratelimit-remaining, x-ratelimit-reset. Bursts up to 2× allowed for 10s. Hard caps lift on request for verified merchants.
Are tool calls audit-logged?
Every call is signed (HMAC-SHA256), append-only, and surfaced in the dashboard with the originating client, scope, parameters, and response status. Webhooks fire on every write. Logs export to S3 or your SIEM.
Can the AI act without me approving?
Read-only tools, yes. Any write requires explicit approval at session start; payouts and admin always prompt for a fresh OAuth challenge per call. You can also pre-approve specific tools for a session.
How does the Agent Wallet differ from a normal wallet?
It's a sub-account with policy attached: spend caps, merchant whitelist/blacklist, category controls, and signed receipts on every charge. The agent never sees your master credentials — only its own scoped key.
What does it cost?
All three MCP servers are free — you pay the standard Coinpay processing fee on transactions (0.5% in). Agent Wallet has no monthly minimum during beta.
Is the dev MCP server self-hostable?
Yes. The developer server is open-source on GitHub — fork it, point it at our spec mirror, run it inside your firewall. Merchant and Agent servers stay hosted (they hold keys).
What's on the roadmap?
Q2: dispute & chargeback tools, Slack & Linear notifiers, fine-grained per-tool quotas. Q3: streaming subscription tools, multi-merchant agent wallets, on-device MCP for POS hardware.

Hand the boring half of your business to your AI.

Connect Claude, ChatGPT, or Cursor to Coinpay in under two minutes. Free during public beta — no card required.

Start the handshake Read the docs