Robokassa Mcp

io.github.theYahiaPublished by GitHub account theYahiav1.0.0Updated Oct 24, 2026

MCP server for Robokassa payment API — generate payment URLs, check invoice status. First MCP for R

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

Local MCP server for the Robokassa payment API that lets an assistant build signed payment URLs and check invoice status.

What you can do
  • Create invoices: build a Robokassa payment URL with an MD5 signature, optionally with a 54-FZ receipt
  • Check invoices: query invoice status through the OpStateExt XML interface
  • Run over stdio by default, or optionally start an HTTP transport with a JSON-RPC endpoint and a health check
When to use it
Useful when you work with Robokassa as a merchant and want an assistant to draft payment links or look up the state of existing invoices without leaving the chat.
Requirements
Runs locally via npx (Node.js). Needs a Robokassa merchant account and the environment variables ROBOKASSA_LOGIN, ROBOKASSA_PASSWORD1 and ROBOKASSA_PASSWORD2; ROBOKASSA_TEST can be set to true for test mode. Network access to the Robokassa API is required.
Before you install
The server needs your merchant login and both Robokassa signing passwords (ROBOKASSA_PASSWORD1, ROBOKASSA_PASSWORD2), which authorize payment signatures and status checks; store them only in the local environment. Creating an invoice produces a real payment link, so check amounts and test mode before sharing it. Invoice data is sent to Robokassa.

Installation

In SourceWeft

  1. Open Robokassa Mcp in the dashboard and add it to a workspace.
  2. 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

@theyahia/robokassa-mcp

MCP server for Robokassa payment API. 2 tools for invoice creation (with MD5 signature) and status checking.

[npm] [license]

Quick Start

Claude Desktop

json
{  "mcpServers": {    "robokassa": {      "command": "npx",      "args": ["-y", "@theyahia/robokassa-mcp"],      "env": {        "ROBOKASSA_LOGIN": "your-login",        "ROBOKASSA_PASSWORD1": "your-password1",        "ROBOKASSA_PASSWORD2": "your-password2"      }    }  }}

Claude Code

bash
claude mcp add robokassa -e ROBOKASSA_LOGIN=login -e ROBOKASSA_PASSWORD1=pass1 -e ROBOKASSA_PASSWORD2=pass2 -- npx -y @theyahia/robokassa-mcp

Cursor / Windsurf

json
{  "robokassa": {    "command": "npx",    "args": ["-y", "@theyahia/robokassa-mcp"],    "env": {      "ROBOKASSA_LOGIN": "your-login",      "ROBOKASSA_PASSWORD1": "your-password1",      "ROBOKASSA_PASSWORD2": "your-password2"    }  }}

Tools

ToolDescription
create_invoiceCreate payment URL with MD5 signature, optional 54-FZ receipt
check_invoiceCheck invoice status via OpStateExt XML interface

Auth

VariableRequiredDescription
ROBOKASSA_LOGINYesMerchant login
ROBOKASSA_PASSWORD1YesPassword 1 (for payment signature)
ROBOKASSA_PASSWORD2YesPassword 2 (for status check signature)
ROBOKASSA_TESTNoSet to "true" for test mode

HTTP Transport

bash
HTTP_PORT=3000 npx @theyahia/robokassa-mcp# ornpx @theyahia/robokassa-mcp --http 3000

Endpoints: POST /mcp (JSON-RPC), GET /health (status).

Skills

  • skill-create-invoice -- create a Robokassa payment URL with MD5 signature
  • skill-check-payment -- check invoice status via OpStateExt

License

MIT

Source: README.md at commit e393697

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 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