1. Conduid
  2. RAG
  3. io.github.artgas1/robokassa-mcp
MCP server · RAG

io.github.artgas1/robokassa-mcp

Comprehensive MCP server for the Robokassa payment gateway (18 tools, full API coverage).

Unclaimed last commit 6 months ago rag
37Low

Scored 6 months ago · breakdown

About io.github.artgas1/robokassa-mcp

io.github.artgas1/robokassa-mcp is an MCP server published by artgas1 in the RAG category: comprehensive MCP server for the Robokassa payment gateway (18 tools, full API coverage).

The repository has 1 stars and 0 forks, with the last commit 6 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

uvx
uvx robokassa-mcp
pip
pip install robokassa-mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Tools (11)

build_split_invoiceMarketplace multi-recipient checkout.

Parameters not published.

calc_out_sumCompute amount credited to shop for a given payment.

Parameters not published.

check_paymentGet current state of a payment by InvId (via OpStateExt).

Parameters not published.

create_invoiceBuild a signed checkout URL (optional 54-ФЗ receipt).

Parameters not published.

list_currenciesList payment methods available to the shop.

Parameters not published.

partner_refundAlternative refund path for partner integrators.

Parameters not published.

refund_createInitiate a refund (requires Refund API access).

Parameters not published.

refund_statusPoll refund progress by requestId.

Parameters not published.

send_smsPaid SMS service.

Parameters not published.

verify_result_signatureValidate a ResultURL webhook.

Parameters not published.

verify_success_signatureValidate a SuccessURL redirect.

Parameters not published.

Ask AI

✦

Ask AI about io.github.artgas1/robokassa-mcp

Powered by Claude · Grounded in docs

I know everything about io.github.artgas1/robokassa-mcp. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.

5 checks have not been run yet.

README


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)

# As an MCP server for Claude Desktop / Claude Code / Cursor / Windsurf
uvx robokassa-mcp

# As a Python library
pip install robokassa-mcp

Use as a Python library

import asyncio
from decimal import Decimal
from robokassa import create_invoice, RobokassaClient

# Build a signed checkout URL (no HTTP — just URL construction).
invoice = create_invoice(
    merchant_login="my-shop",
    out_sum=Decimal("599.00"),
    inv_id=12345,
    password1="...",
    description="Premium subscription",
    email="user@example.com",
)
print(invoice.url)  # https://auth.robokassa.ru/Merchant/Index.aspx?...

# Check the state of a payment (hits the OpStateExt XML endpoint).
async def check() -> None:
    async with RobokassaClient("my-shop", password2="...") as client:
        state = await client.check_payment(inv_id=12345)
        print(state.is_paid, state.info.op_key)

asyncio.run(check())

Full refund flow

from robokassa import RobokassaClient

async def refund_flow(inv_id: int) -> None:
    async with RobokassaClient("my-shop", password2="p2", password3="p3") as client:
        # 1. Fetch the payment state to get its OpKey.
        state = await client.check_payment(inv_id)
        assert state.info.op_key, "payment not complete yet"

        # 2. Initiate a refund.
        created = await client.refund_create(state.info.op_key)
        print("refund requestId:", created.request_id)

        # 3. Poll status until finished / canceled.
        while True:
            status = await client.refund_status(created.request_id)
            if status.is_terminal:
                print("final:", status.state)
                break

Webhook signature verification (FastAPI example)

from fastapi import FastAPI, Request, HTTPException, PlainTextResponse
from robokassa import verify_result_signature, build_ok_response

app = FastAPI()

@app.post("/robokassa/result")
async def result_url(req: Request) -> PlainTextResponse:
    form = dict(await req.form())
    if not verify_result_signature(form, password2="..."):
        raise HTTPException(status_code=403, detail="Bad signature")
    # ... persist the notification, mark invoice paid ...
    return PlainTextResponse(build_ok_response(form["InvId"]))

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):

{
  "mcpServers": {
    "robokassa": {
      "command": "uvx",
      "args": ["robokassa-mcp"],
      "env": {
        "ROBOKASSA_LOGIN": "your-shop-login",
        "ROBOKASSA_PASSWORD1": "password1",
        "ROBOKASSA_PASSWORD2": "password2",
        "ROBOKASSA_PASSWORD3": "password3"
      }
    }
  }
}

Claude Code

claude mcp add robokassa \
  -e ROBOKASSA_LOGIN=my-shop \
  -e ROBOKASSA_PASSWORD1=... \
  -e ROBOKASSA_PASSWORD2=... \
  -e ROBOKASSA_PASSWORD3=... \
  -- uvx robokassa-mcp

Cursor

Edit ~/.cursor/mcp.json:

{
  "mcpServers": {
    "robokassa": {
      "command": "uvx",
      "args": ["robokassa-mcp"],
      "env": {
        "ROBOKASSA_LOGIN": "your-shop-login",
        "ROBOKASSA_PASSWORD1": "password1",
        "ROBOKASSA_PASSWORD2": "password2",
        "ROBOKASSA_PASSWORD3": "password3"
      }
    }
  }
}

VS Code (GitHub Copilot)

In user or workspace settings.json:

{
  "github.copilot.chat.mcp.servers": {
    "robokassa": {
      "command": "uvx",
      "args": ["robokassa-mcp"],
      "env": {
        "ROBOKASSA_LOGIN": "your-shop-login",
        "ROBOKASSA_PASSWORD1": "password1",
        "ROBOKASSA_PASSWORD2": "password2",
        "ROBOKASSA_PASSWORD3": "password3"
      }
    }
  }
}

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "robokassa": {
      "command": "uvx",
      "args": ["robokassa-mcp"],
      "env": {
        "ROBOKASSA_LOGIN": "your-shop-login",
        "ROBOKASSA_PASSWORD1": "password1",
        "ROBOKASSA_PASSWORD2": "password2",
        "ROBOKASSA_PASSWORD3": "password3"
      }
    }
  }
}

HTTP transport (MCP Inspector, remote clients)

uvx robokassa-mcp --transport http --port 8000

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.).

Tool Purpose Auth
create_invoice Build a signed checkout URL (optional 54-ФЗ receipt). Password#1
check_payment Get current state of a payment by InvId (via OpStateExt). Password#2
list_currencies List payment methods available to the shop. —
calc_out_sum Compute amount credited to shop for a given payment. Password#1
refund_create Initiate a refund (requires Refund API access). Password#3 JWT
refund_status Poll refund progress by requestId. —
verify_result_signature Validate a ResultURL webhook. Password#2
verify_success_signature Validate a SuccessURL redirect. Password#1
hold_init / hold_confirm / hold_cancel Two-step card pre-authorization. Password#1
init_recurring_parent / recurring_charge Subscription auto-charges. Password#1
build_split_invoice Marketplace multi-recipient checkout. —
send_sms Paid SMS service. Password#1
second_receipt_create / second_receipt_status 54-ФЗ final receipt after advance. Password#1
partner_refund Alternative refund path for partner integrators. Partner JWT

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:

Group Coverage Module
Merchant Checkout ✅ create_invoice (+ 54-ФЗ) robokassa.checkout
XML Interfaces ✅ check_payment, list_currencies, calc_out_sum robokassa.xml_interface
Refund API ✅ refund_create, refund_status robokassa.refund
Holding / Pre-auth ✅ init / confirm / cancel robokassa.holding
Recurring ✅ parent + child robokassa.recurring
Fiscal 54-ФЗ ✅ second receipt create / status robokassa.fiscal
Partner API 🟡 partner_refund only — see coverage notes robokassa.partner
Auxiliary ✅ send_sms, webhook signatures, split payments robokassa.sms, robokassa.webhooks, robokassa.split

Environment variables

Most high-level entry points fall back to these env vars when credentials aren't passed explicitly:

Variable Required for
ROBOKASSA_LOGIN All operations
ROBOKASSA_PASSWORD1 Checkout, webhook SuccessURL verification, CalcOutSumm, fiscal, SMS
ROBOKASSA_PASSWORD2 check_payment (OpStateExt), webhook ResultURL verification
ROBOKASSA_PASSWORD3 refund_create

Signature algorithms

All signature-producing helpers accept algorithm= with "md5" / "sha256" / "sha384" / "sha512" — match whatever is configured in your Robokassa cabinet.

Development

git clone https://github.com/artgas1/robokassa-mcp.git
cd robokassa-mcp
uv sync --all-extras --dev
uv run pytest            # 107+ unit tests
uv run ruff check .
uv run pyright

License

MIT — see LICENSE. Drop-and-forget maintenance; PRs welcome but not guaranteed to be reviewed promptly.

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About io.github.artgas1/robokassa-mcp

How do I install io.github.artgas1/robokassa-mcp?

Run uvx robokassa-mcp, then add the server to your MCP client's configuration.

Is io.github.artgas1/robokassa-mcp safe to use with an AI agent?

Its trust score is 37 out of 100 (low). It passes 1 of the 1 static security checks run so far. It has no ConduID identity yet, so agent calls to it are not receipted.

Is io.github.artgas1/robokassa-mcp still maintained?

The last commit was 6 months ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.