razorpay-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAZORPAY_KEY_ID | Yes | Your Razorpay API key ID | |
| RAZORPAY_KEY_SECRET | Yes | Your Razorpay API 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_paymentA | Fetch details of a specific payment by ID |
| list_paymentsC | List payments with optional filters |
| get_payment_analyticsA | Analyze payments for a date range — total revenue, success rate, failure breakdown, payment method distribution |
| get_orderA | Fetch details of a specific order by ID |
| list_ordersC | List orders with optional filters |
| get_customerA | Fetch details of a specific customer by ID |
| list_customersC | List customers with optional filters |
| get_subscriptionA | Fetch details of a specific subscription |
| list_subscriptionsC | List subscriptions with optional filters |
| get_subscription_analyticsA | Analyze subscriptions — active count, churn rate, MRR, upcoming renewals |
| get_refundC | Fetch details of a specific refund |
| list_refundsC | List refunds for a payment |
| get_dashboard_summaryA | Get a high-level business summary — revenue today, this week, this month, success rate, top payment methods. Perfect for a quick business health check. |
| get_failed_payment_analysisB | Analyze why payments are failing — breakdown by error code, bank, payment method |
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 14 tools
Every tool targets a distinct resource or analysis type (customers, orders, payments, refunds, subscriptions, dashboard, failed payment analysis), with no overlapping purposes. An agent can clearly differentiate between them.
All tools follow a consistent verb_noun pattern using lowercase and underscores: 'get_' for single items and 'list_' for collections. No mixing of conventions.
14 tools is well-scoped for a payment gateway MCP, covering all major entities and analytics without being excessive or insufficient.
The tool surface is entirely read-only (get and list operations), lacking any create, update, or delete tools. For a payment gateway, this is a significant gap that prevents agents from taking actions like creating payments or refunds.