YooKassa MCP
yookassa-mcp
YooKassa MCP server: payments, refunds, 54-FZ receipts, payouts and webhooks straight from an agent chat
Install
claude mcp add yookassa -e YOOKASSA_SHOP_ID=your-id -e YOOKASSA_SECRET_KEY=your-key -- npx -y @theyahia/yookassa-mcpUse test shop keys while trying it out.
This is third-party code. Review the repository files before installing.
What it does
The server connects the agent to the YooKassa v3 API. The agent can create payments, including SBP, marketplace split payments and recurring charges on a saved payment method, and capture or cancel two-stage payments. It also handles refunds, fiscal receipts, payouts to cards, YooMoney or SBP, webhook registration and removal, and a shop mode check. Every POST gets a stable idempotence key, so a retry after a network failure does not charge twice. Money-moving tools are marked destructive so the client asks for confirmation.
Who it is for. For developers and online shop owners who accept payments via YooKassa and want to handle payments and refunds through an agent.
Good fit when
- You need to find a payment and refund it
- You want to test an integration on a test shop without writing code
- You need a list of successful payments for a period
- You need to set up shop webhooks
Not a fit when
- You have no separate test shop and would be experimenting on the live one
- You need a full payment integration inside your product rather than manual operations via an agent
Example request
Show successful payments for the last 7 days and refund 2,500 rubles on the payment I point toLimitations
Requires a YooKassa shop ID and secret key. Payouts are a separate YooKassa product with their own gateway keys, and sending raw card numbers without PCI DSS certification is not allowed. On a live shop, payments, refunds and payouts are irreversible. YooKassa has no balance endpoint. HTTP mode requires a token and must not face the internet without an authenticating proxy. Community project, not a YooKassa product.
How to disable. Run claude mcp remove yookassa in Claude Code or delete the yookassa block from your MCP client config. Rotating the secret key in the YooKassa dashboard afterwards is a good idea.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| YOOKASSA_SHOP_ID required | YooKassa shop ID |
| YOOKASSA_SECRET_KEY required, secret | Shop API secret key |
| YOOKASSA_PAYOUT_AGENT_ID | Payout gateway ID, only for payouts |
| YOOKASSA_PAYOUT_SECRET_KEY secret | Payout gateway secret key |
| MCP_AUTH_TOKEN secret | Required in HTTP mode, Bearer token for clients |
Security check
- Creates payments, refunds and payouts with real money
- Requires the shop secret key
- Recurring charges run without the buyer's involvement
README in short
The README gives npx configs for Claude Desktop, Claude Code, VS Code, Cursor and Windsurf, plus an HTTP mode with a token. It lists environment variables, including separate payout keys, and explains how to work against a test shop. Tools are grouped into payments, refunds, receipts, payouts, webhooks and account. The architecture section covers idempotence keys, timeouts and retries. Part of the author's WWmcp series, MIT license.
FAQ
How do I avoid moving real money while testing?
Create a test shop in YooKassa, use its keys and confirm with get_shop_info that the response has test set to true.
Can the server run remotely?
Yes, there is a Streamable HTTP mode with a Bearer token. It listens on localhost by default and must not be exposed without an authenticating proxy.
Related
Stripe's official MCP server, plugins and skills: the agent searches the API and docs, reads and changes account data
The official CCXT MCP server and skills: market data, balances and opt-in trading across crypto exchanges and prediction markets
Skill plugins for analyzing stocks, earnings, options and startups, plus readers for social feeds and market data
Skills and an MCP server for options traders: quotes, technical analysis, Greeks, spreads, scanners and Interactive Brokers portfolio