Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Payme MCP Server Generate a checkout link for 50,000 UZS"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server for Payme — the leading payment system in Uzbekistan. Enables AI agents (Claude, GPT, Cursor, etc.) to process payments, manage cards, and generate checkout links through the Model Context Protocol.
Stripe, PayPal, and Square all have MCP servers. Payme didn't — until now. If you're building AI agents for Uzbekistan's market, this is the missing piece.
Related MCP server: payme-mcp
Tool | Description |
| Tokenize a payment card (Uzcard, Humo) |
| Verify card with SMS code |
| Check if a card token is valid |
| Remove a saved card |
| Create a payment receipt (invoice) |
| Pay a receipt with a card token |
| Send receipt notification via SMS |
| Cancel/refund a receipt |
| Check receipt status |
| Generate a Payme checkout payment link |
npx payme-mcpThat's it. One command — downloads, installs, and runs automatically.
Get your credentials from merchant.paycom.uz, then add to your AI tool:
Add to claude_desktop_config.json:
{
"mcpServers": {
"payme": {
"command": "npx",
"args": ["-y", "payme-mcp"],
"env": {
"PAYME_ID": "your_merchant_id",
"PAYME_KEY": "your_merchant_key",
"PAYME_TEST": "true"
}
}
}
}Add to .mcp.json in your project root:
{
"mcpServers": {
"payme": {
"command": "npx",
"args": ["-y", "payme-mcp"],
"env": {
"PAYME_ID": "your_merchant_id",
"PAYME_KEY": "your_merchant_key",
"PAYME_TEST": "true"
}
}
}
}Add to MCP settings:
{
"payme": {
"command": "npx",
"args": ["-y", "payme-mcp"],
"env": {
"PAYME_ID": "your_merchant_id",
"PAYME_KEY": "your_merchant_key"
}
}
}Once connected, your AI agent can:
Create a payment link:
"Generate a Payme checkout link for order #1234, amount 99,000 UZS"
Process a card payment:
"Tokenize card 8600XXXXXXXXXXXX, verify it, then charge 50,000 UZS"
Check payment status:
"Check the status of receipt 63abc..."
Cancel a payment:
"Cancel receipt 63abc... and notify the customer"
Variable | Required | Description |
| Yes | Your Payme merchant ID |
| Yes | Your Payme merchant key |
| No | Set to |
Payme uses tiyin (1 UZS = 100 tiyin):
UZS | Tiyin |
1,000 | 100,000 |
9,900 | 990,000 |
99,000 | 9,900,000 |
990,000 | 99,000,000 |
State | Meaning |
0 | Created (waiting for payment) |
4 | Paid |
21 | Held (funds reserved) |
50 | Cancelled |
git clone https://github.com/sirliboyev-uz/payme-mcp.git
cd payme-mcp
npm install
npm run buildCard numbers are tokenized by Payme — tokens are safe to store
Never log or store raw card numbers
Use PAYME_TEST=true for development/testing
All API calls use HTTPS
MIT — see LICENSE
Built by SirliAI
Check if a card token is valid and get card details (masked number, expiry, status). Example: cards_check({ token: '630e5e...' })
Inputs: token (required).
Tokenize a payment card (Uzcard, Humo). Returns a reusable token. After creation, verify the card with SMS code using cards_verify. Example: cards_create({ cardNumber: '8600123456789012', expire: '0399' })
Inputs: expire (required), cardNumber (required), save.
Remove a saved card token. The token will no longer be usable. Example: cards_remove({ token: '630e5e...' })
Inputs: token (required).
Verify a card using the SMS code sent to the cardholder. Must be called after cards_create. Example: cards_verify({ token: '630e5e...', code: '666666' })
Inputs: code (required), token (required).
Pay a receipt using a verified card token. The card must be verified first. Example: receipts_pay({ receiptId: '63...', token: '630e5e...' })
Inputs: token (required), receiptId (required).
Send receipt notification to customer via SMS. Example: receipts_send({ receiptId: '63...', phone: '998901234567' })
Inputs: phone (required), receiptId (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 6 tools
Each tool has a clear, distinct purpose: card token lifecycle (create, check, verify, remove) and receipt actions (pay, send). No overlap or ambiguity.
All tools follow a consistent snake_case verb_noun pattern: cards_create, cards_check, cards_verify, cards_remove, receipts_pay, receipts_send.
6 tools is well-scoped for a payment card and receipt management server. Each tool earns its place without unnecessary bloat or deficiency.
Covers the full card token lifecycle and key receipt operations. Minor gap: no refund or receipt status query, but core workflow (tokenize, verify, pay) is complete.
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.
Agent Commerce Protocol MCP — bridges Stripe ACP + Google AP2 + Coinbase x402 for agent payments
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
