SaphirePay MCP: Crypto payments, native to your AI client.

Setup

Up and running in minutes.

Pick your platform. One line does it. Or paste the connector URL straight into any MCP client.

https://mcp.saphirepay.org/mcp

thensaphirepay loginand ask Claude to pay.

Ask

Just ask. It runs the right tool.

Talk to your AI the way you’d brief an assistant. It picks the matching SaphirePay tool and does the work.

“Invoice Acme Co $400 in USDC, due Friday” “What did I earn this month?” “Start a $20/mo subscription for @lee” “Refund invoice #84”

Tools

150+ payment actions. 53 fast tools. One connection.

Everything SaphirePay does, exposed as MCP tools your AI can call in plain language: invoices and pay links, payments and refunds, subscriptions, customers, payouts, live prices.

fast tools

150+

payment actions

coins · BTC, ETH, XRP, SOL, LTC, XLM, HBAR + USDC/USDT

Capabilities

Payments your AI can run, safely.

Non-custodial by design

Funds settle straight to wallets you control. SaphirePay never holds a balance for you.

Plain-language workflows

Invoices, pay links, refunds, requests, subscriptions, payouts. Described in English, executed as tools.

Works in any MCP client

Claude Desktop, Claude on your phone via the hosted connector, Claude Code, Cursor. Anything that speaks MCP.

Guardrails on money

Every money-moving tool needs an explicit confirm, with thresholds, ceilings and per-recipient cooldowns.

Security

Built to never hold what isn’t yours.

Non-custodial at the core, with scoped keys and hard guardrails around anything that moves money.

Funds settle to your wallet

Every payment lands on-chain at addresses you own. No platform balance, ever.

Scoped access

Keys are minted with only the scopes your AI needs (read, write, or send) and revocable any time from your dashboard.

Encrypted local store

Credentials live encrypted on your machine, never in the model’s context or our logs.

You sign every transfer

Outbound sends are signed in your own wallet via WalletConnect. The server can’t move funds alone.

FAQ

Answers before you ask.

Is the SaphirePay MCP server really non-custodial?

Yes. The server authenticates with a scoped API key and forwards your instructions to SaphirePay. It never holds funds or private keys. Invoices and payouts settle straight to your own wallet on-chain, and outbound sends are signed in your wallet via WalletConnect.

Which AI clients does it work with?

Any MCP client over stdio: Claude Desktop, Claude Code, and Cursor are first-class. For mobile, multi-tenant or hosted setups, the same tools run over the HTTP connector at mcp.saphirepay.org/mcp with OAuth.

How does signing in work?

After installing, run saphirepay login. It opens SaphirePay in your browser. Sign in with your normal account and approve access. The server receives a scoped credential and stores it encrypted in ~/.saphirepay. There are no keys to copy or paste, and you can revoke access anytime from your dashboard.

Which coins and chains are supported?

Live prices and invoicing cover BTC, ETH, XRP, LTC, SOL, XLM, and HBAR, plus USDC / USDT stablecoins. Non-custodial wallet sends (send_crypto) currently cover EVM assets through WalletConnect.

Can it move money without my say-so?

No. Every money-moving tool requires an explicit confirm: true, and per-device guardrails add confirmation thresholds, a hard ceiling, and per-recipient cooldowns and daily caps. Read tools never move anything.