PaySovra MCP server

Run your PaySovra store from Claude, or any MCP client.

What PaySovra is

PaySovra is a non-custodial crypto payment gateway for businesses. Customers pay in Bitcoin, Ethereum, Solana, USDC, USDT and more across ten networks, and funds settle straight to wallets you control — no processor balance, no payout hold, no waiting on a window.

On-chain payments are final once confirmed, so there are no chargebacks to defend. Stablecoins settle at the price you charged, so accepting crypto does not mean holding volatility. You price in USD, EUR, GBP, CAD, AUD, PLN or INR, and the exchange rate is locked when the customer commits.

What you can do with it

Take payments. Create a payment for any amount and asset and get back a hosted checkout link. Payments are watched on-chain and confirmed automatically, including the awkward cases — underpaid, overpaid, and late arrivals.

Sell products without a storefront. Every product gets a hosted page with its own link: images, video, benefit bullets, variants, quantity limits and stock. Sell physical goods, digital downloads or services. Digital products carry a delivery link the buyer receives on payment.

Send invoices. Build a line-item invoice, email it, and get paid in crypto. Mark it paid, or let the chain do it for you.

Track orders. Full order history with the transaction hash, the amount expected, the amount actually received, and the status — settled, pending, underpaid, expired.

Keep your customers. A customer record per buyer with order history and lifetime spend, importable and exportable as CSV.

Everything above is available through this MCP server, so an assistant can do it in conversation instead of you clicking through a dashboard.

Setup

You need a PaySovra account and a secret integration key.

1. In PaySovra, open Integrations and create a secret integration key. It starts with sk_live_ and is shown once.

2. Add the server to your MCP client's config. For Claude Desktop that is ~/Library/Application Support/Claude/claude_desktop_config.json on macOS, or %APPDATA%\Claude\claude_desktop_config.json on Windows:

   {
     "mcpServers": {
       "paysovra": {
         "command": "npx",
         "args": ["-y", "paysovra-mcp"],
         "env": {
           "PAYSOVRA_SECRET_KEY": "sk_live_..."
         }
       }
     }
   }

3. Restart the client, then try: "Create a product for a ceramic mug, $14, with two benefits and an image from <url>."

Because the server runs on your own machine, upload_image can read a file from disk — local images work, not only public URLs.

Tools

• Products — list, get, create, update, delete
• Invoices — list, get, create, update, set status (mark paid), delete
• Payments — list, get, create
• Customers — list, create, import (array, CSV, or local file), export
• Images — upload_image, from a local filePath or a public sourceUrl

Notes

update_product and update_invoice replace the record rather than patching it, so send the full definition. Ask the assistant to fetch the item first if you only mean to change one field.

For a digital product, set deliveryConfig.linkUrl — that link is what the buyer receives after paying. Without it they receive nothing.

Your secret key can create charges and read customer data. Keep it in the MCP client's config, not in a shared file, and rotate it from the Integrations page if it is ever exposed.

Configuration

| Variable | Required | Default | | --- | --- | --- | | PAYSOVRA_SECRET_KEY | yes | — | | PAYSOVRA_API_URL | no | https://paysovra.com |

PAYSOVRA_API_URL only needs setting to point at a non-production instance.

Links

• PaySovra
• Documentation

License

MIT