Integrations & Tools2026-07-202 min read

Razorpay MCP Server: India's First Official Payment Gateway MCP

Razorpay was the first payment provider in India to ship an official MCP server, offering both a hosted remote endpoint and a self-hosted option for payment links, orders, and refunds.

Integration examplesAPI configs

Razorpay holds a notable distinction in India's MCP ecosystem: reporting on the space consistently describes it as the first Indian payment provider to bring an official MCP server to market, ahead of competitors like PayU and Cashfree who followed with their own official servers afterward. The project is open-sourced at razorpay/razorpay-mcp-server on GitHub, with documentation hosted directly at razorpay.com/docs/mcp-server/.

What It Exposes

The server wraps Razorpay's core commercial functions as standardized MCP tools, encapsulating payment processing so that both technical and non-technical users can call them through natural language. Documented capabilities include:

  • Payment details — fetching and inspecting individual payment records
  • Payment links — creating shareable payment links programmatically
  • Order management — creating and tracking orders
  • Refunds — processing refunds against existing payments

The framing Razorpay itself uses is workflow automation and "agentic applications" — AI-powered tools that interact with the payment ecosystem programmatically, rather than a human clicking through the merchant dashboard for every action.

Two Ways to Run It

Razorpay documents two deployment paths:

  • Remote MCP Server (recommended) — hosted by Razorpay directly, giving instant access to Razorpay APIs with no local setup at all.
  • Self-hosted — build from source or run via Docker if you need to run it inside your own infrastructure, alongside your own credential and network policies.

For most merchants and developers, Razorpay's own guidance points to the hosted remote server as the simpler starting point — you skip the deployment and credential-management overhead entirely and connect your AI client straight to Razorpay's endpoint.

Why "First to Market" Matters Here

Razorpay leading the pack has a real practical consequence: the tool schemas, safety patterns, and documentation style it established became a reference point competitors were measured against. When Cashfree and PayU rolled out their own official MCP servers afterward, coverage of both explicitly framed them as following Razorpay's lead into "agentic AI" for Indian payments — worth knowing if you're comparing the three, since Razorpay's has simply had more time in production and more independent write-ups scrutinizing it.

What to Watch For

Refunds and order creation are real money-moving and money-returning actions. As with any payment-capable MCP server, the same caution applies here as with Zerodha's trading tools or Zomato's checkout flow: an AI client that can call refund or create_order autonomously should have a human confirmation step in front of it in any production workflow, regardless of what the underlying server technically permits.

Join the Discussion

Code Snippets (0)

No code snippets shared yet. Be the first to contribute!