@theyahia/yookassa-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTTP_PORT | No | Port for HTTP transport (default 3000) | 3000 |
| YOOKASSA_SHOP_ID | Yes | Shop ID from YooKassa settings | |
| YOOKASSA_SECRET_KEY | Yes | Secret key from YooKassa API keys |
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_paymentA | Create a payment in YooKassa. Returns a confirmation URL. Supports one-step and two-step payments, receipts, and metadata. MOVES REAL MONEY (the payer is charged) — irreversible. |
| get_paymentA | Get payment details by ID. Returns status, amount, payment method, confirmation URL, and metadata. |
| capture_paymentA | Confirm a two-step payment (capture held funds). Optionally capture a partial amount. MOVES REAL MONEY — irreversible. |
| cancel_paymentA | Cancel a payment (pending or waiting_for_capture). Releases any held funds. |
| list_paymentsA | List payments with filters by status, date range, and pagination cursor. |
| save_payment_methodA | Save a payment method for recurring charges. Creates a small real payment to bind the card/wallet (charged, then refundable). MOVES REAL MONEY — irreversible. |
| create_recurring_paymentA | Charge a saved payment method. Charges the card immediately WITHOUT any user interaction. MOVES REAL MONEY — irreversible. |
| create_sbp_paymentA | Create a payment via SBP (Russian fast payment system). Returns a confirmation URL / deep-link for the payer's banking app. MOVES REAL MONEY — irreversible. |
| create_split_paymentA | Create a split payment for marketplaces (distributes funds among partner shops). Requires the YooKassa-for-platforms product. MOVES REAL MONEY — irreversible. |
| create_refundA | Refund a payment (full or partial) by payment_id and amount. MOVES REAL MONEY (funds returned to the payer) — irreversible. |
| get_refundA | Get refund details by ID. Returns status, amount, and payment reference. |
| list_refundsA | List refunds with optional filter by payment_id. |
| create_receiptA | Create a standalone fiscal receipt (54-FZ). Supports payment and refund receipts with items, VAT codes, and customer contacts. |
| list_receiptsA | List receipts with filters by payment_id or refund_id. |
| create_payoutA | Create a payout to a bank card, YooMoney wallet, or SBP. Requires the separately-activated YooKassa Payouts product with its own credentials (see README/SECURITY). Asynchronous — the response may be 'pending'; poll get_payout for the final status. MOVES REAL MONEY — irreversible. |
| get_payoutA | Get payout details by ID. Returns status, amount, and destination. |
| create_webhookB | Register a webhook URL for YooKassa events (payment.succeeded, refund.succeeded, etc.). |
| list_webhooksA | List all registered webhooks for this shop. |
| delete_webhookA | Delete a webhook by ID. Stops sending notifications for that webhook. |
| get_shop_infoA | Get shop info: ID, status, test mode, fiscalization settings. (YooKassa has no balance endpoint; this returns shop configuration, not a monetary balance.) |
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 20 tools
Tools are largely distinct by resource and action, but the multiple 'create payment' variants (standard, SBP, split, recurring) could cause initial confusion. Descriptions clarify their unique purposes, so agents can differentiate with careful reading.
All tools follow a consistent verb_noun snake_case pattern (create_, get_, list_, capture_, cancel_, delete_, save_). The pattern is predictable and makes the function of each tool immediately clear.
20 tools covers a broad payment API surface, but each tool maps to a distinct operation (payments, refunds, receipts, payouts, webhooks, shop info). The count is slightly above the ideal 3-15 range, but justified by the domain's complexity.
The core payment lifecycle is well covered (create, get, list, capture, cancel), along with refunds, receipts, payouts, and webhooks. Missing list_payouts and a get_receipt are minor gaps, but agents can still perform essential workflows.