This MCP server lets AI assistants create CigalPay crypto checkout links and inspect payment, order, active-payment, coin, and refund data.
Create a payment link priced in USD or EUR (amount > 0, max 5,000) with a description and optional order reference, checkout language, notify URL, and return URL.
Retrieve a payment's status, coin, amounts, and transaction by payment ID; paid means confirmed or finished.
Find all payments tied to a specific order reference.
List payments still waiting for customer funds.
List coins accepted directly by CigalPay.
List refunds for a payment, newest first, with status.
Note: the README mentions an optional destructive create_refund tool, but it is not present in this server schema.
Supports accepting Bitcoin payments: create checkout links priced in USD or EUR where the customer pays in BTC at a rate locked for 30 minutes, check whether the payment was confirmed, list pending payments, and issue refunds in crypto.
Supports accepting Ethereum payments: create checkout links priced in USD or EUR where the customer pays in ETH at a rate locked for 30 minutes, check whether the payment was confirmed, list pending payments, and issue refunds in crypto.
Supports accepting Litecoin payments: create checkout links priced in USD or EUR where the customer pays in LTC at a rate locked for 30 minutes, check whether the payment was confirmed, list pending payments, and issue refunds in crypto.
Supports accepting Solana payments: create checkout links priced in USD or EUR where the customer pays in SOL at a rate locked for 30 minutes, check whether the payment was confirmed, list pending payments, and issue refunds in crypto.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@CigalPay MCP Server Create a 49 EUR payment link for invoice 1042, logo design."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Let Claude, Cursor, VS Code and other AI assistants use your CigalPay account: create crypto payment links, check whether a payment arrived, and follow refunds, by asking in plain language.
"Create a 49 EUR payment link for invoice 1042, logo design." "Has the payment for order 1042 been confirmed?"
Prices are in USD or EUR. Your customer picks the coin on the CigalPay checkout (Bitcoin, USDT on Tron, Ethereum, Solana, Litecoin and more), with the rate locked for 30 minutes.
Tool | What it does |
| Create a payment priced in USD or EUR and return the checkout link (up to 5,000 per payment). |
| Status, coin and amounts of a payment. Paid means |
| Every payment created for one of your order references |
| Payments still waiting for the customer |
| Coins accepted directly |
| Refunds of a payment and their status |
| Refund a payment in crypto. Off by default: set |
create_refund moves money out of your CigalPay balance, so it is only available when you turn it on, and it is
marked as destructive so your assistant asks before using it.
Related MCP server: Yolfi MCP Server
Get your Account ID and API key in the CigalPay dashboard, Settings → API credentials. Node.js 18 or later is needed.
Variable | |
| Required to create payment links |
| Required to read payments and refunds. Keep it secret |
| Public HTTPS URL that receives signed payment notifications. Needed by |
| Where customers go after paying (default: cigalpay.com) |
|
|
claude mcp add cigalpay \
-e CIGALPAY_ACCOUNT_ID=your-account-id \
-e CIGALPAY_API_KEY=your-api-key \
-e CIGALPAY_NOTIFY_URL=https://your-site.com/cigalpay/notify \
-- npx -y cigalpay-mcpAdd to the client's MCP configuration (claude_desktop_config.json, .cursor/mcp.json, ...):
{
"mcpServers": {
"cigalpay": {
"command": "npx",
"args": ["-y", "cigalpay-mcp"],
"env": {
"CIGALPAY_ACCOUNT_ID": "your-account-id",
"CIGALPAY_API_KEY": "your-api-key",
"CIGALPAY_NOTIFY_URL": "https://your-site.com/cigalpay/notify"
}
}
}
}CigalPay sends a signed notification to your notify URL when a payment's status changes. Check the
x-cigalpay-sig signature before trusting it, with the JavaScript SDK
(CigalPay.verifyWebhook) or the PHP SDK. See the
developer docs.
Bump the version in package.json, server.json (twice) and CHANGELOG.md, then push a tag vX.Y.Z. GitHub
Actions stages the package on npm; approve it on npmjs.com, then run the MCP Registry workflow.
Create a payment priced in USD or EUR and return the CigalPay checkout link to send to the customer. The customer chooses the coin on the checkout page; the rate is locked for 30 minutes. Maximum 5,000 per payment.
Inputs: amount (required), currency (required), description (required), lang, +4 more.
Status, coin, amounts and transaction of a payment by its id. Paid means status confirmed or finished.
Inputs: payment_id (required).
Every payment created for one of your order references (the order_id of create_checkout).
Inputs: order_id (required).
Payments created on the account that are still waiting for the customer to pay.
Inputs: no named parameters.
Refunds of a payment, newest first, with their status.
Inputs: payment_id (required).
The coins CigalPay accepts directly (other coins are converted automatically at checkout).
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 6 tools
Each tool has a distinct action scope: create, single-payment lookup by id, lookups by order reference, coin listing, pending listing, and refund listing. The three payment-reading tools (get_payment, get_payments_by_order, list_active_payments) are close in purpose, but the descriptions make the lookup key explicit enough that an agent can pick correctly.
All six tools follow a strict snake_case verb_noun pattern (create_checkout, get_payment, list_supported_coins, etc.) with consistent use of get_ for single lookups and list_ for collections. The only minor quirk is create_checkout naming the outcome 'checkout' rather than 'payment', which is still predictable and readable.
Six tools is tightly scoped to the payment-gateway domain: one create path, three read paths, and two reference-data/list tools. Nothing feels redundant or padded.
Core flow (create checkout, check status, track by order, list pending, list coins) is covered, but there is no way to create or cancel a refund or cancel a payment—only list_refunds exists. These are notable lifecycle gaps that would force an agent to fall back to the web dashboard.
Crypto pay links and API for people and AI agents. BTC, Lightning, USDC, USDT, EURC, SOL, ETH.
Non-custodial crypto payments for AI assistants: balances, payments, and create payment links.
Stripe payments for AI agents. Create links, verify, manage customers.
Non-custodial crypto payments: charges, invoices and refunds in BTC, XRP, USDC and more.
