Razorpay MCP Server

What Razorpay MCP Server does

Razorpay MCP Server exposes Razorpay payment and commerce operations through the Model Context Protocol. It is designed for AI tools and agent workflows that need to work with Razorpay resources without building a separate MCP wrapper around the API.

The API surface covers payment capture, payment lookup, card-detail retrieval, payment listing with filters and pagination, payment-note updates, and payment initiation using saved payment methods. Authentication flows include resending and submitting OTPs. Agents can also create, inspect, send, and update standard payment links, create UPI payment links, and retrieve link collections.

Order operations include creation, lookup, listing, updates, and retrieving payments associated with an order. Refund tools support creation, lookup, listing, note updates, and finding refunds associated with a payment. QR-code tools create and retrieve codes, list them, and filter them by customer or payment ID. Settlement and payout tools provide access to settlement records, reconciliation details, instant-settlement records, and payout information.

Additional tools retrieve or revoke saved payment tokens, create subscription registration links, detect a project's language or framework, and generate Razorpay Standard Checkout integration code for supported frameworks.

How it works

The server communicates with MCP-compatible AI clients and translates tool calls into operations against Razorpay APIs. Razorpay offers a hosted remote server, which avoids deploying the MCP process yourself, and a local option for running it on your own infrastructure. The hosted option is used with a merchant token.

Remote availability varies by tool. The tool catalogue marks most payment, order, retrieval, settlement, payout, token, and helper operations as supported remotely. Creating refunds, closing QR codes, creating instant settlements, and creating registration links are listed as local-only operations.

Setup and configuration

Choose between Razorpay's hosted MCP server and a self-hosted local deployment. The hosted route requires a merchant token and does not require running the server yourself. The local route is appropriate when the MCP process needs to run within your infrastructure.

Connect the selected deployment to an MCP-compatible client, then expose the resulting tools to an agent. Credentials should be configured according to the deployment's authentication requirements and handled as payment-system secrets.

Tools and capabilities

• Manage payments, including capture, initiation, lookup, listing, notes, card details, and OTP submission.
• Create and manage standard and UPI payment links.
• Create, retrieve, update, and inspect orders and their payments.
• Create and investigate refunds, including payment-specific refund lookups.
• Create and query QR codes by ID, customer, or payment.
• Retrieve settlements, reconciliation data, instant settlements, and payouts.
• Manage saved payment tokens and subscription registration links.
• Detect project stacks and generate supported Razorpay Checkout integration code.

Limitations and notes

The remote server does not expose every tool. Refund creation, QR-code closure, instant-settlement creation, and registration-link creation are identified as unsupported remotely. Operations that change payment state or move funds should be reviewed carefully before an agent is allowed to invoke them.