payme-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAYME_KEY | Yes | API key from Paycom dashboard | |
| PAYME_MERCHANT_ID | Yes | Merchant ID from Paycom dashboard |
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 |
|---|---|
| create_transactionC | Create a new Payme transaction (JSON-RPC). |
| perform_transactionC | Perform (confirm) a created transaction. |
| cancel_transactionC | Cancel a transaction with a reason code. |
| check_transactionC | Check transaction status. |
| get_statementC | Get transaction statement for a time period. |
| check_perform_transactionC | Validate if a transaction can be performed. |
| create_payment_linkC | Generate a Payme checkout payment link. |
| get_merchant_balanceB | Get merchant account balance. |
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 8 tools
Tools are mostly distinct in purpose, but 'check_perform_transaction' and 'check_transaction' could be confused if descriptions are not read carefully. Overall, each tool targets a specific action.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., cancel_transaction, create_payment_link). No mixing of conventions.
8 tools cover the essential payment lifecycle (create, validate, perform, cancel, status, balance, statement, payment link) without being excessive or insufficient.
Core payment operations are covered, but missing refund or void capabilities. The surface is functional for basic workflows but has minor gaps.