Payme MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| cards_createA | 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' }) |
| cards_verifyA | Verify a card using the SMS code sent to the cardholder. Must be called after cards_create. Example: cards_verify({ token: '630e5e...', code: '666666' }) |
| cards_checkA | Check if a card token is valid and get card details (masked number, expiry, status). Example: cards_check({ token: '630e5e...' }) |
| cards_removeA | Remove a saved card token. The token will no longer be usable. Example: cards_remove({ token: '630e5e...' }) |
| receipts_create | Create a payment receipt (invoice). Amount is in tiyin (1 UZS = 100 tiyin). Example: 99,000 UZS = 9,900,000 tiyin. Example: receipts_create({ orderId: 'order-123', amount: 9900000 }) |
| receipts_payA | Pay a receipt using a verified card token. The card must be verified first. Example: receipts_pay({ receiptId: '63...', token: '630e5e...' }) |
| receipts_sendB | Send receipt notification to customer via SMS. Example: receipts_send({ receiptId: '63...', phone: '998901234567' }) |
| receipts_cancel | Cancel a receipt. Paid receipts may be refunded depending on merchant settings. Example: receipts_cancel({ receiptId: '63...' }) |
| receipts_check | Check receipt status. States: 0=created, 4=paid, 21=held, 50=cancelled. Example: receipts_check({ receiptId: '63...' }) |
| checkout_url | Generate a Payme checkout payment link. Redirects customer to Payme's hosted page. Amount is in tiyin. Example: checkout_url({ merchantId: '5e7...', orderId: 'order-123', amount: 9900000 }) |
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 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.