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

MCP serverRussian stack

artgas1/robokassa-mcpAuthor:artgas1

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/robokassa-mcp

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

This entry is high risk, so there is no one-click install. Review the code and add the config by hand.

Run in a terminal

claude mcp add --transport stdio --env 'ROBOKASSA_LOGIN=<ROBOKASSA_LOGIN value>' robokassa-mcp -- uvx robokassa-mcp==0.1.2

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "robokassa-mcp": {
      "command": "uvx",
      "args": [
        "robokassa-mcp==0.1.2"
      ],
      "env": {
        "ROBOKASSA_LOGIN": "<ROBOKASSA_LOGIN value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

ROBOKASSA_LOGINrequired: Merchant login identifier for the Robokassa shop.
ROBOKASSA_PASSWORD1secret, optional: Shop's Password #1 — used for checkout URL signing, SuccessURL signature verification, CalcOutSumm, fiscal receipts, and SMS.
ROBOKASSA_PASSWORD2secret, optional: Shop's Password #2 — used for OpStateExt payment status checks and ResultURL signature verification.
ROBOKASSA_PASSWORD3secret, optional: Shop's Password #3 — used for Refund API (JWT HS256). Refund API access must be enabled in the cabinet.

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.cursor/mcp.json, for all projects

{
  "mcpServers": {
    "robokassa-mcp": {
      "command": "uvx",
      "args": [
        "robokassa-mcp==0.1.2"
      ],
      "env": {
        "ROBOKASSA_LOGIN": "<ROBOKASSA_LOGIN value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.

Keys and settings

ROBOKASSA_LOGINrequired: Merchant login identifier for the Robokassa shop.
ROBOKASSA_PASSWORD1secret, optional: Shop's Password #1 — used for checkout URL signing, SuccessURL signature verification, CalcOutSumm, fiscal receipts, and SMS.
ROBOKASSA_PASSWORD2secret, optional: Shop's Password #2 — used for OpStateExt payment status checks and ResultURL signature verification.
ROBOKASSA_PASSWORD3secret, optional: Shop's Password #3 — used for Refund API (JWT HS256). Refund API access must be enabled in the cabinet.

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

code --add-mcp '{"name":"robokassa-mcp","type":"stdio","command":"uvx","args":["robokassa-mcp==0.1.2"],"env":{"ROBOKASSA_LOGIN":"<ROBOKASSA_LOGIN value>"}}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "robokassa-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "robokassa-mcp==0.1.2"
      ],
      "env": {
        "ROBOKASSA_LOGIN": "<ROBOKASSA_LOGIN value>"
      }
    }
  }
}

If the file already exists, add the server inside the servers key.

Keys and settings

ROBOKASSA_LOGINrequired: Merchant login identifier for the Robokassa shop.
ROBOKASSA_PASSWORD1secret, optional: Shop's Password #1 — used for checkout URL signing, SuccessURL signature verification, CalcOutSumm, fiscal receipts, and SMS.
ROBOKASSA_PASSWORD2secret, optional: Shop's Password #2 — used for OpStateExt payment status checks and ResultURL signature verification.
ROBOKASSA_PASSWORD3secret, optional: Shop's Password #3 — used for Refund API (JWT HS256). Refund API access must be enabled in the cabinet.

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

codex mcp add robokassa-mcp --env 'ROBOKASSA_LOGIN=<ROBOKASSA_LOGIN value>' -- uvx robokassa-mcp==0.1.2

Or add to the file ~/.codex/config.toml, for all projects

[mcp_servers.robokassa-mcp]
command = "uvx"
args = ["robokassa-mcp==0.1.2"]
env = { ROBOKASSA_LOGIN = "<ROBOKASSA_LOGIN value>" }

If the file already exists, append the block to the end.

Keys and settings

ROBOKASSA_LOGINrequired: Merchant login identifier for the Robokassa shop.
ROBOKASSA_PASSWORD1secret, optional: Shop's Password #1 — used for checkout URL signing, SuccessURL signature verification, CalcOutSumm, fiscal receipts, and SMS.
ROBOKASSA_PASSWORD2secret, optional: Shop's Password #2 — used for OpStateExt payment status checks and ResultURL signature verification.
ROBOKASSA_PASSWORD3secret, optional: Shop's Password #3 — used for Refund API (JWT HS256). Refund API access must be enabled in the cabinet.

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Run in a terminal

gemini mcp add -s user -e 'ROBOKASSA_LOGIN=<ROBOKASSA_LOGIN value>' robokassa-mcp uvx robokassa-mcp==0.1.2

Or add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "robokassa-mcp": {
      "command": "uvx",
      "args": [
        "robokassa-mcp==0.1.2"
      ],
      "env": {
        "ROBOKASSA_LOGIN": "<ROBOKASSA_LOGIN value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

ROBOKASSA_LOGINrequired: Merchant login identifier for the Robokassa shop.
ROBOKASSA_PASSWORD1secret, optional: Shop's Password #1 — used for checkout URL signing, SuccessURL signature verification, CalcOutSumm, fiscal receipts, and SMS.
ROBOKASSA_PASSWORD2secret, optional: Shop's Password #2 — used for OpStateExt payment status checks and ResultURL signature verification.
ROBOKASSA_PASSWORD3secret, optional: Shop's Password #3 — used for Refund API (JWT HS256). Refund API access must be enabled in the cabinet.

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/devin/mcp_config.json, for all projects

{
  "mcpServers": {
    "robokassa-mcp": {
      "command": "uvx",
      "args": [
        "robokassa-mcp==0.1.2"
      ],
      "env": {
        "ROBOKASSA_LOGIN": "<ROBOKASSA_LOGIN value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.

Keys and settings

ROBOKASSA_LOGINrequired: Merchant login identifier for the Robokassa shop.
ROBOKASSA_PASSWORD1secret, optional: Shop's Password #1 — used for checkout URL signing, SuccessURL signature verification, CalcOutSumm, fiscal receipts, and SMS.
ROBOKASSA_PASSWORD2secret, optional: Shop's Password #2 — used for OpStateExt payment status checks and ResultURL signature verification.
ROBOKASSA_PASSWORD3secret, optional: Shop's Password #3 — used for Refund API (JWT HS256). Refund API access must be enabled in the cabinet.

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Formerly Windsurf.

Add to the file cline_mcp_settings.json, for all projects

{
  "mcpServers": {
    "robokassa-mcp": {
      "command": "uvx",
      "args": [
        "robokassa-mcp==0.1.2"
      ],
      "env": {
        "ROBOKASSA_LOGIN": "<ROBOKASSA_LOGIN value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.

Keys and settings

ROBOKASSA_LOGINrequired: Merchant login identifier for the Robokassa shop.
ROBOKASSA_PASSWORD1secret, optional: Shop's Password #1 — used for checkout URL signing, SuccessURL signature verification, CalcOutSumm, fiscal receipts, and SMS.
ROBOKASSA_PASSWORD2secret, optional: Shop's Password #2 — used for OpStateExt payment status checks and ResultURL signature verification.
ROBOKASSA_PASSWORD3secret, optional: Shop's Password #3 — used for Refund API (JWT HS256). Refund API access must be enabled in the cabinet.

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .roo/mcp.json, in the project

{
  "mcpServers": {
    "robokassa-mcp": {
      "command": "uvx",
      "args": [
        "robokassa-mcp==0.1.2"
      ],
      "env": {
        "ROBOKASSA_LOGIN": "<ROBOKASSA_LOGIN value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

ROBOKASSA_LOGINrequired: Merchant login identifier for the Robokassa shop.
ROBOKASSA_PASSWORD1secret, optional: Shop's Password #1 — used for checkout URL signing, SuccessURL signature verification, CalcOutSumm, fiscal receipts, and SMS.
ROBOKASSA_PASSWORD2secret, optional: Shop's Password #2 — used for OpStateExt payment status checks and ResultURL signature verification.
ROBOKASSA_PASSWORD3secret, optional: Shop's Password #3 — used for Refund API (JWT HS256). Refund API access must be enabled in the cabinet.

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

A fork of Roo Code, same .roo folders.

Add to the file opencode.json, in the project

{
  "mcp": {
    "robokassa-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "robokassa-mcp==0.1.2"
      ],
      "environment": {
        "ROBOKASSA_LOGIN": "<ROBOKASSA_LOGIN value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcp key.

Keys and settings

ROBOKASSA_LOGINrequired: Merchant login identifier for the Robokassa shop.
ROBOKASSA_PASSWORD1secret, optional: Shop's Password #1 — used for checkout URL signing, SuccessURL signature verification, CalcOutSumm, fiscal receipts, and SMS.
ROBOKASSA_PASSWORD2secret, optional: Shop's Password #2 — used for OpStateExt payment status checks and ResultURL signature verification.
ROBOKASSA_PASSWORD3secret, optional: Shop's Password #3 — used for Refund API (JWT HS256). Refund API access must be enabled in the cabinet.

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file ~/.config/zed/settings.json, for all projects

{
  "context_servers": {
    "robokassa-mcp": {
      "command": "uvx",
      "args": [
        "robokassa-mcp==0.1.2"
      ],
      "env": {
        "ROBOKASSA_LOGIN": "<ROBOKASSA_LOGIN value>"
      }
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Keys and settings

ROBOKASSA_LOGINrequired: Merchant login identifier for the Robokassa shop.
ROBOKASSA_PASSWORD1secret, optional: Shop's Password #1 — used for checkout URL signing, SuccessURL signature verification, CalcOutSumm, fiscal receipts, and SMS.
ROBOKASSA_PASSWORD2secret, optional: Shop's Password #2 — used for OpStateExt payment status checks and ResultURL signature verification.
ROBOKASSA_PASSWORD3secret, optional: Shop's Password #3 — used for Refund API (JWT HS256). Refund API access must be enabled in the cabinet.

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

Add to the file .codeassistant/mcp.json, in the project

{
  "mcpServers": {
    "robokassa-mcp": {
      "command": "uvx",
      "args": [
        "robokassa-mcp==0.1.2"
      ],
      "env": {
        "ROBOKASSA_LOGIN": "<ROBOKASSA_LOGIN value>"
      }
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Keys and settings

ROBOKASSA_LOGINrequired: Merchant login identifier for the Robokassa shop.
ROBOKASSA_PASSWORD1secret, optional: Shop's Password #1 — used for checkout URL signing, SuccessURL signature verification, CalcOutSumm, fiscal receipts, and SMS.
ROBOKASSA_PASSWORD2secret, optional: Shop's Password #2 — used for OpStateExt payment status checks and ResultURL signature verification.
ROBOKASSA_PASSWORD3secret, optional: Shop's Password #3 — used for Refund API (JWT HS256). Refund API access must be enabled in the cabinet.

Replace the values in angle brackets with your own. Keys never go into install links and are not stored by us.

You will need: uv

Checked against the repository on Sep 25, 2026, commit 5f2ae1f.

Text for your agent

Install the server with uvx robokassa-mcp, set ROBOKASSA_LOGIN, ROBOKASSA_PASSWORD1, ROBOKASSA_PASSWORD2 and ROBOKASSA_PASSWORD3 from the Robokassa merchant cabinet, and add it to claude_desktop_config.json or via claude mcp add robokassa -e ... -- uvx robokassa-mcp.

Other ways from the author

uvx robokassa-mcp

Installs and runs the MCP server via uvx; needs the ROBOKASSA_* variables set.

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 customer

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.

MCP

Transport: stdio, http, sse
Authentication: API key

Environment variables
Environment variables
ROBOKASSA_LOGIN required	Robokassa merchant login
ROBOKASSA_PASSWORD1 required, secret	Password 1: signs receipts, checkout, fiscal and SMS operations
ROBOKASSA_PASSWORD2 required, secret	Password 2: payment status checks and ResultURL signature verification
ROBOKASSA_PASSWORD3 secret	Password 3: initiating refunds via refund_create

Security check

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

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.

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.

AI Berkshire

Editors’ pick

A set of investment research skills for Claude Code and Codex built on four investors' methodologies. It is a research tool, not investment advice

SkillMedium riskNo VPN needed16.6K

Stripe AI

Official

Stripe's official MCP server, plugins and skills: the agent searches the API and docs, reads and changes account data

MCP serverHigh riskNeeds a VPN1.8K

Alpaca MCP Server

Official

Alpaca's official MCP server: orders for stocks, ETFs, crypto and options, position management and market data in plain language

MCP serverHigh risk995

inn-check-ru: counterparty risk traffic light

inn-check-ru

Editors’ pick

An open-source skill that checks a Russian company by tax ID across EGRUL, bailiffs, courts, bankruptcy and sanctions, and returns a dated risk verdict

SkillLow riskRussian stackNo VPN needed4

Install

What it does

Good fit when

Not a fit when

Example request

Limitations

MCP

Security check

README in short

FAQ

Related

AI Berkshire

Stripe AI

Alpaca MCP Server

inn-check-ru: counterparty risk traffic light