Robokassa MCP: full API coverage
robokassa-mcp
A Python client and MCP server for Robokassa: invoices, status checks, refunds, holds, recurring charges and 54-FZ receipts, 18 tools
- 1 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Tools create invoices, initiate refunds, hold and charge customer cards
- Keep Password#3 separate and enable Refund API access only when it is actually needed
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/robokassa-mcpDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Tools create invoices, initiate refunds, hold and charge customer cards
- Keep Password#3 separate and enable Refund API access only when it is actually needed
This is third-party code. Review the repository files before installing.
What it does
The project ships a Python library, robokassa, and an MCP server, robokassa-mcp, built on top of it, published to PyPI and the MCP registry. It covers eight groups of the official Robokassa API: building a signed checkout link with an optional 54-FZ receipt, checking payment status via the OpStateExt XML interface, calculating the amount credited to the shop, refunds and polling their status, two-step card pre-authorization (holding), parent and child recurring charges, multi-recipient split payments for marketplaces, paid SMS notifications, and verifying ResultURL and SuccessURL webhook signatures. That is 18 MCP tools in total, plus low-level signature helpers available from Python only. It runs via uvx, pip or Docker, and supports stdio, HTTP, streamable-http and SSE.
Who it is for. For developers of Robokassa-based stores and services who need full payment API coverage, not just invoice creation.
Good fit when
- You need to build checkout invoices with a 54-FZ receipt and check their status
- You need refunds, card holding or recurring charges through Robokassa
- You need to verify ResultURL and SuccessURL webhook signatures on your own server
Not a fit when
- You need only a basic invoice and status check: the simpler theYahia/robokassa-mcp server is smaller and easier to set up
- You need Partner API coverage beyond the single partner_refund tool: the rest of the Partner API is not implemented
Example request
Build a payment link for a 599-ruble subscription with a 54-FZ receipt and send it to the customerMCP
- Transport
- stdio, http, sse
- Authentication
- API key
Environment variables
ROBOKASSA_LOGINrequired- Robokassa merchant login
ROBOKASSA_PASSWORD1required, secret- Password 1: signs receipts, checkout, fiscal and SMS operations
ROBOKASSA_PASSWORD2required, secret- Password 2: payment status checks and ResultURL signature verification
ROBOKASSA_PASSWORD3secret- Password 3: initiating refunds via refund_create
Limitations
The README says install (once published), meaning PyPI publication was still treated as the final release step at README time, so check the package is live on PyPI before installing. Refunds and recurring charges require separate access enabled in the Robokassa merchant cabinet (Refund API, a JWT for the Partner API). The author describes maintenance as drop-and-forget: PRs are welcome but not guaranteed prompt review.
How to disable. Remove the robokassa server from your MCP client config, for example claude mcp remove robokassa.
FAQ
Do I need all three passwords at once?
No, each tool needs its own: Password#1 for receipts and checkout, Password#2 for status checks and ResultURL signatures, Password#3 for refunds.
Do refunds work right after installation?
No, refund_create requires Refund API access to be enabled in the Robokassa merchant cabinet first.
Discussion
No questions or reviews yet.
Related
MCP serversRobokassa MCP: payment link and status
@theyahia/robokassa-mcp
A compact two-tool Robokassa MCP server: a signed payment link with a 54-FZ receipt, and invoice status checks
YooKassa MCP
yookassa-mcp
YooKassa MCP server: payments, refunds, 54-FZ receipts, payouts and webhooks straight from an agent chat
YooKassa MCP server
MCP-сервер ЮKassa
YooKassa official MCP: an agent creates payment links and invoices, checks statuses and refunds, but cannot move money on its own
Sberbank business API MCP server
@theyahia/sber-mcp
An MCP server for the Sberbank Business API: accounts, balance, statements, payment orders and counterparties for an AI agent
RoboSystems graph MCP endpoint: an agent queries company financial data and SEC XBRL filings in a knowledge graph
Tochka Bank MCP server
MCP-сервер Точка Банка
Tochka Bank's official MCP: an agent checks accounts and balances, builds statements and drafts payments that you sign in online banking
README in short
The README gives usage examples both as a Python library and as an MCP server: building a signed checkout link, a full refund cycle with status polling, verifying a webhook signature in FastAPI, configs for Claude Desktop, Claude Code, Cursor, VS Code Copilot and Windsurf, a table of all 18 tools noting which password each needs, a coverage table for the eight official API groups, and the environment variables and their purpose.