An agent can now generate a payment link: YooKassa launches an MCP server with 7 tools

YooKassa has opened an MCP server: an AI agent connects to the payment service like any other tool. The API changelog entry is dated 16 September 2026.

Previously, accepting payments meant developer work: SDKs, keys, webhooks, and handling statuses. Now a store owner creates a token and puts it into the agent configuration.

How to connect. The token is created in the dashboard, on the “Integration — Store access” page, in the “Tokens for the MCP server” block. Its default lifetime is 3 months, with a maximum of 3 years. The token is shown once, and only an Owner or Manager can create one.

The agent then connects to mcp.yookassa.ru via Streamable HTTP with the Authorization: Bearer header. An active store is required; a test store also works. The docs include a ready-made configuration only for Claude Code. Other agents, including Koda, require a manually assembled configuration following the general instructions for external MCP servers.

What the agent can do. There are seven tools: create a payment, view a payment, list payments, create an invoice, view an invoice, view a refund, and list refunds. The agent can only read refunds; they are processed in the YooKassa dashboard or via API.

An invoice created through MCP lives for no more than 30 days, and invoices cannot be created in a test store at all. MCP does not support receipts, autopayments, or two-stage payments, nor payouts, splitting, or “Safe Deal”. Sending receipts to the tax authority must be disabled.

You verify the amount. YooKassa does not store a product catalogue and does not check what an agent billed for or how much. The amount is checked before the link is sent to the customer.

YooMoney's Director of Corporate Products Dmitry Gnilitsa calls the server a first step toward agentic commerce, where entrepreneurs share ready-made agents with one another.