Paytm MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAYTM_MID | Yes | Your Paytm Merchant ID | |
| PAYTM_KEY_SECRET | Yes | Your Paytm Key Secret |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_payment_linkA | |
| fetch_payment_linksA | |
| fetch_transactions_for_linkA | |
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 3 tools
Each tool has a distinct purpose: creating a payment link, fetching all payment links, and fetching transactions for a specific link. There is no overlap or ambiguity.
All names start with verbs (create, fetch) and use underscores, but the structure varies: singular vs plural and preposition 'for' in fetch_transactions_for_link. Mostly consistent but not perfectly uniform.
With only 3 tools, the server feels thin for a payment gateway, but it is scoped to payment link management. This is borderline; more tools would improve coverage.
Covers create and read operations for payment links and transactions, but misses essential update/delete functionalities for payment links, leaving gaps in the lifecycle.