@theyahia/robokassa-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_PORT | No | Port for HTTP transport (can also be set with --http) | |
| ROBOKASSA_TEST | No | Set to "true" for test mode | |
| ROBOKASSA_LOGIN | Yes | Merchant login | |
| ROBOKASSA_PASSWORD1 | Yes | Password 1 (for payment signature) | |
| ROBOKASSA_PASSWORD2 | Yes | Password 2 (for status check signature) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_invoiceB | Создать счёт Robokassa. Возвращает ссылку на оплату с MD5-подписью. |
| check_invoiceA | Проверить статус счёта Robokassa по номеру (OpStateExt). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one creates an invoice, the other checks its status. No overlap or ambiguity.
Both tool names follow a consistent verb_noun pattern in snake_case: create_invoice, check_invoice.
With only 2 tools, the surface feels thin for a payment invoice service. While it covers basic operations, it is at the lower end of the acceptable range.
The set provides create and check (read) operations but misses other lifecycle actions like cancel or refund, resulting in notable gaps for a typical payment workflow.