Allows an AI agent to create Kaspi QR invoices, check payment statuses, process refunds, and manage subscriptions via the Qut Pay API.
Also known as kazprose/qutpay-docs, mcp, @qutpay/mcp
- Stars
- 0
- Tools
- 7
- Downloads, 30 days
- —
- Latest version
- 0.1.3
- Last commit
- Oct 26, 2026
- License
- MIT
What is Qut Pay MCP?
Qut Pay allows an AI agent to create Kaspi QR invoices, check payment statuses, process refunds, and manage subscriptions via the Qut Pay API. It exposes 7 tools, such as qutpay_account, qutpay_create_invoice, qutpay_get_invoice.
Summary generated from the project's README
About Qut Pay MCP server
Managing Kaspi QR payments for businesses in Kazakhstan is possible through this MCP server. It allows AI agents to interact with the Qut Pay API to generate invoices, check payment statuses, process full or partial refunds, and oversee recurring subscription schedules. Developers can use it locally via npx with an API key or connect to a remote hosted endpoint using Streamable HTTP.
Users must provide a QUTPAY_API_KEY from the Qut Pay cabinet to authenticate. The server supports a sandbox mode using keys starting with qp_test_ to simulate transactions without moving real money. Specific tools like qutpay_create_invoice allow for creating QR codes or pushing invoices directly to a customer's Kaspi.kz app using a phone number. The system also includes qutpay_simulate_payment for testing webhook delivery in sandbox environments.
What you can do with it
- 1Generate Kaspi QR invoicesCreate a new payment request with a QR code or a direct link for a customer.
- 2Verify payment statusCheck if a specific invoice has been paid or remains open.
- 3Process customer refundsIssue a full or partial refund for a completed transaction.
- 4Test payment flowsSimulate successful or failed payments in a sandbox environment to verify webhooks.
- 5Manage recurring billingRead and monitor existing subscription schedules.
Written from the project's README. Every use case is checked against a quote from it.
How to install Qut Pay MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Qut Pay MCP in Claude Code
$ claude mcp add --env 'QUTPAY_API_KEY=<YOUR_QUTPAY_API_KEY>' mcp -- npx -y @qutpay/mcpInstall Qut Pay MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@qutpay/mcp"
],
"env": {
"QUTPAY_API_KEY": "<YOUR_QUTPAY_API_KEY>"
}
}
}
}Install Qut Pay MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@qutpay/mcp"
],
"env": {
"QUTPAY_API_KEY": "<YOUR_QUTPAY_API_KEY>"
}
}
}
}Install Qut Pay MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@qutpay/mcp"],"env":{"QUTPAY_API_KEY":"<YOUR_QUTPAY_API_KEY>"}}'Install Qut Pay MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@qutpay/mcp"
],
"env": {
"QUTPAY_API_KEY": "<YOUR_QUTPAY_API_KEY>"
}
}
}
}Install Qut Pay MCP in Codex
$ codex mcp add mcp --env 'QUTPAY_API_KEY=<YOUR_QUTPAY_API_KEY>' -- npx -y @qutpay/mcpInstall Qut Pay MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp] command = "npx" args = ["-y", "@qutpay/mcp"] [mcp_servers.mcp.env] QUTPAY_API_KEY = "<YOUR_QUTPAY_API_KEY>"
Install Qut Pay MCP in Gemini CLI
$ gemini mcp add -s user -e 'QUTPAY_API_KEY=<YOUR_QUTPAY_API_KEY>' mcp npx -- -y @qutpay/mcpInstall Qut Pay MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@qutpay/mcp"
],
"env": {
"QUTPAY_API_KEY": "<YOUR_QUTPAY_API_KEY>"
}
}
}
}Needs a key before it starts
Started on 16 Nov 2026 with no keys, it stopped and asked for one, so a client sees no tools until you set the variables above.
Qut Pay MCP tools 7
Detected from the READMEqutpay_accountqutpay_create_invoicequtpay_get_invoicequtpay_list_invoicesqutpay_cancel_invoicequtpay_refund_invoicequtpay_simulate_payment
Configuration
QUTPAY_API_KEYRequiredSecretQut Pay API key (qp_test_… sandbox or qp_live_…), from the cabinet → Integrations → API keys
QUTPAY_BASE_URLAPI base URL, default https://api.qut.kz
Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSPass
- Destructive tools are labelledPass
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHub@qutpay/mcp — Qut Pay MCP server
Model Context Protocol server for Qut Pay: lets an AI agent (Claude Code, Claude Desktop, Cursor, Windsurf, VS Code Copilot, ChatGPT developer mode…) create Kaspi QR invoices, read their status, refund, and test the whole flow in sandbox through the Qut Pay API. Kazakhstan only, KZT only. Qut Pay is an independent service, not affiliated with Kaspi Bank.
Install
You need an API key from the Qut Pay cabinet (https://qut.kz/app → Integrations → API keys). Start with a sandbox key (qp_test_…) — no real money moves, payments are simulated.
Claude Code:
claude mcp add qutpay -e QUTPAY_API_KEY=qp_test_… -- npx -y @qutpay/mcp
Cursor one-click: Add to Cursor (then set your key). Cursor / Windsurf / Claude Desktop / VS Code (mcp.json, claude_desktop_config.json):
{
"mcpServers": {
"qutpay": {
"command": "npx",
"args": ["-y", "@qutpay/mcp"],
"env": { "QUTPAY_API_KEY": "qp_test_…" }
}
}
}
The key is read only from the environment and is never printed by the server. Optional QUTPAY_BASE_URL (default https://api.qut.kz).
Remote (hosted) endpoint
No install: https://api.qut.kz/mcp (Streamable HTTP), key in Authorization: Bearer qp_…. Claude Code: claude mcp add --transport http qutpay https://api.qut.kz/mcp --header "Authorization: Bearer qp_test_…"; Cursor/VS Code mcp.json: { "url": "https://api.qut.kz/mcp", "headers": { "Authorization": "Bearer qp_test_…" } }. Without a key the endpoint lists tools and serves docs; tool calls answer unauthorized.
Tools
| Tool | What it does |
|---|---|
qutpay_account |
Organization, mode (sandbox/live), tariff and limits, cashiers, provider status — call first |
qutpay_create_invoice |
Create an invoice (QR, or pushed to the customer's Kaspi.kz app with kind: "phone"); returns payUrl, qrImageUrl, deepLink, expiresAt. Pass idempotencyKey per order |
qutpay_get_invoice |
Status of one invoice (live: true asks Kaspi right now) |
qutpay_list_invoices |
List with filters: status, externalOrderId, from/to, limit ≤ 50 |
qutpay_cancel_invoice |
Close an open invoice |
qutpay_refund_invoice |
Full or partial refund (scope refunds:write); with a live key requires confirm: true |
qutpay_simulate_payment |
Sandbox only: mark an invoice paid / failed / expired, webhooks are delivered for real |
qutpay_list_subscriptions, qutpay_get_subscription |
Read recurring invoice schedules (scope subscriptions:manage) |
Resources: qutpay://skill (agent skill — the integration procedure), qutpay://docs/integration, qutpay://docs/webhook-verify, qutpay://docs/errors, qutpay://docs/openapi. Prompts: integrate-checkout (stack), verify-sandbox (amount).
API keys and webhook endpoints are deliberately not manageable from the MCP server: the merchant creates them in the cabinet, and the agent asks for them.
Typical session
qutpay_account→ mode is sandbox.qutpay_create_invoice { amount: 100, externalOrderId: "test-1", idempotencyKey: "test-1" }→payUrl.qutpay_simulate_payment { id }→paid; the merchant's webhook receivesinvoice.paid.qutpay_get_invoice { id }→paid.
Docs
- Agent skill: https://api.qut.kz/SKILL.md · integration guide: https://api.qut.kz/for-ai · OpenAPI: https://api.qut.kz/openapi.json
- Guide (ru/kk/en): https://api.qut.kz/docs/guide/mcp
- Status page: https://status.qut.kz · trust center: https://qut.kz/en/trust/
MIT.
Qut Pay MCP questions
How do I add Qut Pay MCP to Claude Code?
Run claude mcp add --env 'QUTPAY_API_KEY=<YOUR_QUTPAY_API_KEY>' mcp -- npx -y @qutpay/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Qut Pay MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Qut Pay MCP provide?
It exposes 7 tools, including qutpay_account, qutpay_create_invoice, qutpay_get_invoice, qutpay_list_invoices, qutpay_cancel_invoice.
Can I test payments without using real money?
Yes, you can use a sandbox key starting with 'qp_test_' to simulate payments where no real money moves.
Where do I get an API key?
API keys are obtained from the Qut Pay cabinet under Integrations.
Is Qut Pay affiliated with Kaspi Bank?
No, Qut Pay is an independent service and is not affiliated with Kaspi Bank.
What currencies and regions are supported?
The service is limited to Kazakhstan and uses KZT only.