Robokassa Mcp
Expose the full Robokassa payment gateway to your agent with 18 MCP tools for checkout, status, refunds, and fiscal flows.
Overview
robokassa-mcp is an MCP server for the Build phase that exposes 18 Robokassa payment gateway tools for checkout, status, receipts, and refunds.
What is this MCP server?
- 18 MCP tools with full Robokassa API coverage per server description
- PyPI package robokassa-mcp, stdio transport, version 0.1.2
- Env: ROBOKASSA_LOGIN, PASSWORD1–3 for signing, status, refunds (JWT)
- Supports checkout URL signing, SuccessURL/ResultURL verification patterns
- Refund API requires Password3 and cabinet-enabled refund access
- 18 MCP tools advertised with full API coverage
- Package robokassa-mcp version 0.1.2 on PyPI
- Three merchant passwords: signing (1), status/ResultURL (2), refunds JWT (3)
What problem does it solve?
Hooking Robokassa’s multi-password signing and refund APIs into an agent project is tedious and error-prone without structured tools.
Who is it for?
Indie SaaS or ecommerce builders targeting Robokassa who want agent-assisted payment integration and debugging.
Skip if: Stripe-only stacks, merchants outside Robokassa support, or teams unwilling to manage three separate shop passwords.
What do I get? / Deliverables
Your agent can call typed MCP operations against Robokassa while you keep merchant credentials in env vars.
- Agent-accessible Robokassa API operations across documented tool surface
- Signed payment URLs and verified callback patterns implemented with agent help
- Refund and status flows testable from the IDE via MCP
Recommended MCP Servers
Journey fit
Payment gateway wiring is core backend work when you monetize a SaaS or shop aimed at CIS/Russia-facing Robokassa merchants. The server maps merchant API operations—not landing-page pricing strategy—into agent-callable tools.
How it compares
Robokassa payment MCP with 18 tools, not a generic Stripe skill or storefront theme generator.
Common Questions / FAQ
Who is robokassa-mcp for?
Solo developers integrating Robokassa into backends who use MCP agents for API calls, signatures, and refund testing.
When should I use robokassa-mcp?
Use it during Build backend work when implementing invoices, webhooks, fiscal receipts, or refunds on Robokassa.
How do I add robokassa-mcp to my agent?
Install robokassa-mcp from PyPI, set ROBOKASSA_LOGIN and ROBOKASSA_PASSWORD1–3 per cabinet roles, and add the stdio MCP server to your agent.