
Robokassa Mcp
io.github.artgas1Published by GitHub account artgas1v0.1.2Updated Oct 24, 2026
Comprehensive MCP server for the Robokassa payment gateway (18 tools, full API coverage).
Overview
MCP server for the Robokassa payment gateway that lets an assistant build signed checkout links, check payments, issue refunds and handle fiscal receipts.
- What you can do
- Build signed checkout URLs, including optional 54-ФЗ fiscal receipts, and split marketplace invoices
- Check payment state by invoice ID, list available payment methods and calculate the amount credited to the shop
- Create and poll refunds, plus an alternative partner refund path
- Run two-step card pre-authorization (hold init, confirm, cancel) and recurring subscription charges
- Verify ResultURL and SuccessURL webhook signatures and create or check second fiscal receipts
- Send paid SMS notifications
- When to use it
- Useful when you run a Robokassa shop and want an assistant to help with payment operations: generating checkout links, looking up payment status, starting or tracking refunds, handling pre-auth and recurring charges, or validating webhook signatures during integration work.
- Requirements
- Runs locally as a Python package (uvx robokassa-mcp) over stdio, or optionally over HTTP with transport flags. Needs a Robokassa merchant account and the environment variables ROBOKASSA_LOGIN, ROBOKASSA_PASSWORD1, ROBOKASSA_PASSWORD2 and ROBOKASSA_PASSWORD3. Refund API access must be enabled in the Robokassa cabinet. Network access to Robokassa endpoints is required.
Installation
In SourceWeft
- Open Robokassa Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
[robokassa-mcp — Robokassa payment gateway exposed to AI agents through MCP]
robokassa-mcp
[CI] [PyPI] [Python] [License] [Docs]
📚 Documentation · PyPI · Docker · MCP Registry
Comprehensive Python client and Model Context Protocol server for Robokassa — the Russian payment gateway.
Covers the full API surface: checkout, XML status interfaces, refunds, holding (pre-auth), recurring subscriptions, 54-ФЗ fiscal receipts, Partner API, and auxiliary endpoints.
Install (once published)
Use as a Python library
Full refund flow
Webhook signature verification (FastAPI example)
Use as an MCP server
Claude Desktop
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
Claude Code
Cursor
Edit ~/.cursor/mcp.json:
VS Code (GitHub Copilot)
In user or workspace settings.json:
Windsurf
Edit ~/.codeium/windsurf/mcp_config.json:
HTTP transport (MCP Inspector, remote clients)
Flags: --transport {stdio,http,streamable-http,sse}, --host, --port.
MCP tools exposed to agents
All 18 tools are wrapped as @mcp.tool() and available to any MCP-capable agent (Claude Desktop, Claude Code, Cursor, Windsurf, etc.).
Low-level signature helpers are available from Python only: compute_signature, op_state_signature, build_checkout_signature, build_refund_jwt, build_sms_signature, compute_result_signature, compute_success_signature, encode_fiscal_body.
API coverage
Mapped against the 8 public Robokassa API groups:
Environment variables
Most high-level entry points fall back to these env vars when credentials aren't passed explicitly:
Signature algorithms
All signature-producing helpers accept algorithm= with "md5" / "sha256" / "sha384" / "sha512" — match whatever is configured in your Robokassa cabinet.
Development
License
MIT — see LICENSE. Drop-and-forget maintenance; PRs welcome but not guaranteed to be reviewed promptly.
Source: README.md at commit 5f2ae1f
Tools
0Version history
1- v0.1.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts