Comprehensive MCP server for the Robokassa payment gateway (18 tools, full API coverage).
Comprehensive MCP server for the Robokassa payment gateway (18 tools, full API coverage). Exposed over MCP by the robokassa mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
📚 Documentation · PyPI · Docker · MCP Registry
robokassa-mcp on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Everything the assistant can do here goes through one of these:
create_invoice — Build a signed checkout URL (optional 54-ФЗ receipt)check_payment — Get current state of a payment by InvId (via OpStateExt)list_currencies — List payment methods available to the shopcalc_out_sum — Compute amount credited to shop for a given paymentrefund_create — Initiate a refund (requires Refund API access)refund_status — Poll refund progress by requestIdverify_result_signature — Validate a ResultURL webhookverify_success_signature — Validate a SuccessURL redirectbuild_split_invoice — Marketplace multi-recipient checkoutsend_sms — Paid SMS servicepartner_refund — Alternative refund path for partner integratorsGroup — CoverageYou will need 4 environment variables: ROBOKASSA_LOGIN, ROBOKASSA_PASSWORD1, ROBOKASSA_PASSWORD2, ROBOKASSA_PASSWORD3. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Robokassa's toolset — create_invoice, check_payment, list_currencies and 11 more — is a fair guide to whether it matches your workflow. It is maintained by artgas1; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| create_invoice | Build a signed checkout URL (optional 54-ФЗ receipt). |
| check_payment | Get current state of a payment by InvId (via OpStateExt). |
| list_currencies | List payment methods available to the shop. |
| calc_out_sum | Compute amount credited to shop for a given payment. |
| refund_create | Initiate a refund (requires Refund API access). |
| refund_status | Poll refund progress by requestId. |
| verify_result_signature | Validate a ResultURL webhook. |
| verify_success_signature | Validate a SuccessURL redirect. |
| build_split_invoice | Marketplace multi-recipient checkout. |
| send_sms | Paid SMS service. |
| partner_refund | Alternative refund path for partner integrators. |
| Group | Coverage |
| Recurring | ✅ parent + child |
| Auxiliary | ✅ send_sms, webhook signatures, split payments |
{
"mcpServers": {
"robokassa": {
"command": "uvx",
"args": ["robokassa-mcp"],
"env": {
"ROBOKASSA_LOGIN": "your-shop-login",
"ROBOKASSA_PASSWORD1": "password1",
"ROBOKASSA_PASSWORD2": "password2",
"ROBOKASSA_PASSWORD3": "password3"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| ROBOKASSA_LOGIN | Configuration value read at startup. | Optional |
| ROBOKASSA_PASSWORD1 | Configuration value read at startup. | Optional |
| ROBOKASSA_PASSWORD2 | Configuration value read at startup. | Optional |
| ROBOKASSA_PASSWORD3 | Configuration value read at startup. | Optional |
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.