paytabs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAYTABS_PROFILE_ID | Yes | Merchant profile ID | |
| PAYTABS_SERVER_KEY | Yes | Server key from PayTabs 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_payment_pageB | Create a hosted payment page via PayTabs. |
| query_transactionB | Query transaction details by reference. |
| refund_transactionB | Refund a completed transaction. |
| create_tokenB | Tokenize a card for recurring payments. |
| charge_tokenB | Charge a saved card token. |
| list_transactionsB | List transactions by date range. |
| void_transactionC | Void a pending transaction. |
| get_payment_methodsB | Get available payment methods for a currency. |
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
Each tool targets a distinct action: creating payment pages, querying, refunding, voiding, tokenization, charging tokens, listing, and fetching methods. No overlap exists.
All tool names follow a consistent verb_noun pattern (create_, query_, refund_, void_, list_, get_, charge_). The naming convention is uniform and predictable.
With 8 tools, the set is well-scoped for a payment processing server, covering core payment operations without being bloated or sparse.
The surface covers the main payment lifecycle: creation, querying, refund, void, tokenization, and charging tokens. A minor gap is the lack of a capture/settlement operation, but most workflows are supported.