Your AI Agent,
Connected to Payments
The SatsRail MCP server is hosted and remote — 53 tools for orders, invoices, payment links, products, and webhooks over a single endpoint any MCP client can reach. Nothing to install. Connect with a URL and an API key.
A payment API for Bitcoin, on Lightning or on-chain (early access) — think Stripe, but non-custodial and agent-native.
One Endpoint. The Whole API.
The Model Context Protocol is the open standard for giving agents tools. This is ours.
Hosted, Not Installed
No npm package, no local process to run or keep updated. The server lives inside the API. You connect to a URL.
53 Tools
The full payment lifecycle — the same merchant API your dashboard uses, exposed as tools an agent can call directly.
Any MCP Client
Claude Code, Claude Desktop, Cursor, Windsurf, and any client that speaks Streamable HTTP. Stdio clients bridge in one line.
Three Steps
From zero to an agent that can take a payment.
Create an API Key
Generate a key in your dashboard. Use a test key while you build, a live key in production.
Paste One Config Block
Point your MCP client at the endpoint with your key as a header. That's the whole setup.
Your Agent Transacts
It creates orders, generates Lightning invoices or on-chain addresses (early access), and checks payment status. Lightning settles in seconds; on-chain is final once confirmed. Funds go to the merchant's own wallet.
Connect in Seconds
The full configuration for a native HTTP client.
{
"mcpServers": {
"satsrail": {
"type": "http",
"url": "https://app.satsrail.com/api/v1/mcp",
"headers": { "Authorization": "Bearer sk_live_your_key" }
}
}
}
Works in Claude Code, Claude Desktop, Cursor, Windsurf, and any Streamable-HTTP MCP client. Stdio-only clients bridge with mcp-remote.
No key to paste? A client that supports OAuth connects with the URL alone: you sign in, pick the business, and approve. Those connections manage your catalog only, and you can revoke them any time under Settings → AI Assistants.
What Agents Can Do
The full merchant surface, grouped.
Orders & Invoices
Build orders item by item with taxes and send one payment link or a branded email, generate Lightning invoices or on-chain addresses, check payment status live, and track delivery. See the order loop.
Checkout & Payment Requests
Spin up hosted checkout sessions and one-call payment requests, then track confirmed payments.
Products & Catalog
Manage products, product types, and the full catalog, and make payment links to send customers.
Webhooks
Create, update, and delete webhook endpoints so agents can react to events in real time.
Account & Usage
Read the merchant profile, connected wallets, documents, and API-token usage for self-service monitoring.
Access & Plans
Verify access tokens for gated content and read public subscription plans without authentication.
Send the Link, Not the Money
An agent buying something for you doesn’t need a wallet or your card. It sends you the merchant’s payment link, and you pay from your own wallet.
1. The agent gets the link
From the merchant, their site, or the merchant’s own agent. Adding .json to a SatsRail link tells the agent what it is for, the price and who is paid, without opening a checkout.
2. It sends the link to you
In the chat, email or app where you already talk to it. The link previews with the item, the price and the merchant’s name.
3. You pay from your wallet
You see the checkout, check the price and pay. The money goes straight to the merchant’s wallet. The agent never holds funds or card details.
Selling instead? Your own agent makes the link with create_payment_link and gives it back to send.
From a Conversation to a Delivered Order
Your agent builds the order, sends it, sees it paid and gets it delivered, with tools it already has.
-
1
Build the order
Tell your agent what the customer wants. It starts a draft with
create_orderand adds each item withadd_order_item: catalog products or one-offs, each with its quantity and price. Taxes are worked out per item from your catalog’s rules. -
2
Send one link
create_order_payment_linkreturns one link for the whole order, taxes included, to paste in a chat or a text. Orsend_order_payment_emailemails it for you, with your logo, the order summary and a Pay button. Replies come to you. -
3
The customer sees your prices and pays in bitcoin
The link opens the whole order priced in your currency. The bitcoin amount is set when they click Pay, at that moment’s rate, and the payment goes straight to your wallet. An order is paid once.
-
4
Your agent confirms it
get_orderreports the order paid as soon as the payment lands, so the agent can tell you, or the customer, right away. -
5
Then gets it delivered
list_unfulfilled_ordersanswers “what still needs to go out?”, andmark_order_fulfilledrecords each order shipped, with its tracking number, then delivered.
Example conversation
You: Ada wants two bags of the house blend and a grinder. Send her the bill.
Agent: Order ORD-7F2A: 2 × House blend $36.00, Grinder $60.00, tax $1.80, total $97.80. I emailed Ada the payment link. It’s good for 24 hours.
Agent, later: Ada paid $97.80. It’s waiting in your undelivered orders.
You: Shipped, UPS 1Z999. → marked shipped, with the tracking number.
You set the rules
Order expiry
Choose how long a link stays payable, from 1 hour to 7 days. After that it shows the order expired. Prices stay in your currency until Pay, so a long expiry never locks in an old rate.
Automatic reminders
None, one or two reminder emails to a customer who hasn’t paid: halfway to expiry, and shortly before it. Never once the order is paid, cancelled or expired. Your agent can send one when you ask, too.
Fulfillment tracking
Ask for a shipping address and a phone number before payment, and keep paid orders on an Undelivered list until you mark them shipped and delivered. Your agent sees the same list.
Connect Your Agent
Get an API key, paste one config block, and your agent can accept Bitcoin over Lightning or on-chain (early access).