Razorpay MCP Server

What is Razorpay MCP Server?

A Model Context Protocol (MCP) server that connects the Razorpay payment gateway API to AI assistants such as Cursor, Claude, and Copilot. It enables these assistants to directly access Razorpay account data through a standardized interface.

How to use Razorpay MCP Server?

Install globally via npm (npm install -g [email protected]), then run the binary with your Razorpay API key ID and key secret. For cursor integration, add the configuration to .cursor/mcp.json. For web applications, start the SSE server on a chosen port and connect from your web app using an EventSource.

Key features of Razorpay MCP Server

• Supports both stdio and SSE transport modes.
• Provides 11 Razorpay data retrieval tools.
• Pagination support with count, skip, from, to parameters.
• Works with Cursor, Claude, Copilot, and other MCP clients.
• Docker image available for containerized deployment.
• Simple authentication using key‑id and key‑secret.

Use cases of Razorpay MCP Server

• Query recent payments, orders, or refunds directly inside an AI coding assistant.
• Fetch account balance or customer lists without leaving the development environment.
• Automate dispute or settlement review by asking the assistant for the latest data.
• Integrate Razorpay data inspection into custom web applications via SSE.

FAQ from Razorpay MCP Server

What does this server do?

It acts as a bridge between the Razorpay API and AI assistants, allowing the assistants to fetch Razorpay data using natural language commands.

What are the runtime requirements?

Node.js is required to run the server after global npm installation. Docker is also supported as an alternative deployment method.

Where does the data come from?

All data is retrieved in real time from the Razorpay API using the provided API credentials.

What is the maximum number of items per request?

The count parameter defaults to 10 and has a maximum value of 100.

Which transports are available?

Two transport methods are supported: stdio (for direct integration with tools like Cursor) and SSE (for use in web applications).