Razorpay

io.github.indiamcpPublished by GitHub account indiamcpv0.1.0Updated Oct 24, 2026

MCP server for Razorpay API.

Overview

AI-generated overview

Lets an assistant read Razorpay payment, order, customer, subscription, refund and revenue data through natural-language queries.

What you can do
Connects an AI assistant to a Razorpay account and exposes read-only tools for fetching a payment, order, customer, subscription or refund by ID, and for listing each of those with date, count and status filters. It also provides analytics tools for revenue, success rate and payment-method breakdown, subscription churn and upcoming renewals, a business dashboard summary, and failed-payment analysis by reason, method and bank.
When to use it
Useful when you want to ask questions about Razorpay business data in plain language, such as total revenue this month, active subscriptions, churn rate, pending refunds, or why payments failed in a period, without writing code or opening the dashboard.
Requirements
Runs locally as a Node.js process, installed from the npm package @indiamcp/razorpay-mcp or built from source. Requires a Razorpay account and two credentials supplied as environment variables: RAZORPAY_KEY_ID and RAZORPAY_KEY_SECRET. Desktop client configuration is needed; network access to the Razorpay API is implied.
Before you install
The server needs the Razorpay API key secret (RAZORPAY_KEY_SECRET) and key ID (RAZORPAY_KEY_ID), which grant access to live account data; test keys are recommended during development. The README states the server is read-only in v1 and does not store or cache payment data, but it does send account data to the Razorpay API and returns it to the assistant.

Installation

In SourceWeft

  1. Open Razorpay in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

razorpay-mcp

An MCP (Model Context Protocol) server that connects AI assistants like Claude directly to your Razorpay account. Once configured, you can ask your AI to fetch payments, analyze revenue trends, inspect failed transactions, monitor subscriptions, and get a real-time business dashboard — all in natural language, with no code required.

Quick Start

bash
# Clonegit clone https://github.com/indiamcp/razorpay-mcp
# Installcd razorpay-mcpnpm install
# Configurecp .env.example .env# Add your Razorpay API keys to .env
# Buildnpm run build
# Runnpm start

Claude Desktop Setup

Add this to your claude_desktop_config.json (usually at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS or %APPDATA%\Claude\claude_desktop_config.json on Windows):

json
{  "mcpServers": {    "razorpay": {      "command": "node",      "args": ["/path/to/razorpay-mcp/dist/index.js"],      "env": {        "RAZORPAY_KEY_ID": "rzp_test_xxxxxxxxxxxx",        "RAZORPAY_KEY_SECRET": "your_secret_here"      }    }  }}

Or use npx (once published):

json
{  "mcpServers": {    "razorpay": {      "command": "npx",      "args": ["-y", "@indiamcp/razorpay-mcp"],      "env": {        "RAZORPAY_KEY_ID": "rzp_test_xxxxxxxxxxxx",        "RAZORPAY_KEY_SECRET": "your_secret_here"      }    }  }}

Available Tools

ToolDescriptionKey Parameters
get_paymentFetch a specific payment by IDpayment_id
list_paymentsList payments with filtersfrom, to, count, status
get_payment_analyticsRevenue, success rate, method breakdownfrom, to
get_orderFetch a specific order by IDorder_id
list_ordersList orders with filtersfrom, to, count, status, receipt
get_customerFetch a specific customer by IDcustomer_id
list_customersList customerscount, skip
get_subscriptionFetch a specific subscription by IDsubscription_id
list_subscriptionsList subscriptions with filtersfrom, to, count, status
get_subscription_analyticsActive count, churn rate, upcoming renewalsfrom, to
get_refundFetch a specific refundpayment_id, refund_id
list_refundsList refunds for a paymentpayment_id, count
get_dashboard_summaryBusiness health check — revenue today/week/month(none)
get_failed_payment_analysisFailure reasons, by method and bankfrom, to

Example Prompts

Once connected, try asking Claude:

  • "Show me all failed payments in the last 7 days and why they failed"
  • "What's my total revenue this month?"
  • "List all active subscriptions"
  • "Which payment method do my customers prefer?"
  • "Show me customers who signed up this week"
  • "What's my subscription churn rate this month?"
  • "Find payment pay_xxxxx"
  • "How many refunds are pending?"
  • "Give me a dashboard summary of my business today"
  • "Analyze payment failures for the last 30 days"

Security Note

  • Environment variables only — API keys are read from env vars and never hardcoded or logged
  • Read-only in v1 — this server only fetches data; it cannot create payments, issue refunds, or modify any records
  • No data storage — payment data is never persisted or cached by this server
  • Use test keys during development — Razorpay test keys (rzp_test_*) are safe and make no real charges

Development

bash
# Run in dev mode (no build needed)npm run dev
# Type checknpm run lint
# Run testsnpm test

Part of IndiaMCP

This server is part of IndiaMCP — a suite of open-source MCP servers for the Indian API stack.

github.com/indiamcp

Source: README.md at commit 55e91c6

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.