Razorpay

Name: Razorpay MCP Server
Availability: InStock
Author: Razorpay

Productivity25 tools

Query Razorpay payments, orders, refunds, settlements and payouts from your AI assistant. Anthropic's directory lists 25 read tools; Razorpay's own server ships 45, and 19 of those write.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on 18 August 2026.

Anthropic states this reflects the level of review a connector received, not a security audit.

Connect Razorpay via MCP

https://mcp.razorpay.com/mcp

Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.

Razorpay Tools & Capabilities (25)

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

The directory's tool list is a floor, not the surface. Anthropic's snapshot names 25 read tools; Razorpay's source registers 45, of which 19 write. Nineteen of the 20 omitted names write, and Razorpay marks them supported on the remote server. Check your own client's tool list rather than this page's table before granting approval.
A fetch_* prefix does not mean read-only. fetch_tokens is registered as a write tool in Razorpay's source because it calls Customer.Create when given only a contact number. It is one of the 25 the directory labels "Read".
One endpoint serves test and live. The environment comes from the API key prefix, not the URL. A misconfigured key means an agent reads real merchant and customer data during what was meant to be a rehearsal.
Read-only mode exists but not on the hosted server. READ_ONLY and --read-only are documented for the Local MCP Server and default to false. No equivalent is documented for the remote endpoint.
Scopes are unverifiable from outside. scopes_supported is absent from all three live .well-known documents we fetched, while Razorpay's OAuth guide shows ["read_only"]. We cannot confirm what a consent screen grants.
Tool parameters and safety annotations were not readable. The endpoint returned HTTP 401 to an anonymous initialize on 2026-08-18, so names came from the directory snapshot and meanings from Razorpay's documentation and source. We read no readOnlyHint or destructiveHint off the wire and make no claim about them. No tool was called.
Rate limits are real but unpublished. Razorpay documents a rate limiter, HTTP 429 and exponential backoff with randomisation, but no numbers — and nothing MCP-specific.
Three tools are local-only. create_refund, close_qr_code and create_instant_settlement are marked unsupported on the remote server in Razorpay's reference table. The hosted connector cannot issue a refund.
Razorpay's own counts disagree with each other. Its docs say "35+ tools", its category breakdown sums to 37, its reference table has 39 rows and its source registers 45.

Frequently asked questions

Can I use the Razorpay MCP Server in production?

Yes. Razorpay describes it as an official integration designed for production use, and tells you to match your API keys to the environment — test keys for development, live keys for production — while following security best practices for key management. The connector has been generally available since Razorpay launched the hosted server in June 2025.

How do I switch between test and live modes?

By swapping the API key, not by changing the endpoint. Razorpay documents test keys beginning rzp_test_ and live keys beginning rzp_live_, and states the MCP Server automatically detects the environment from the key you supply. There is one hostname for both modes, so the credential is the only thing separating a rehearsal from real merchant data.

What is the difference between the Remote and Local Razorpay MCP Server?

Remote is hosted by Razorpay with no infrastructure to manage and quick setup. Local is self-hosted with Docker and gives complete control plus, in Razorpay's words, access to all tools without restrictions. Anthropic's directory lists the hosted server only. Three tools are marked local-only in Razorpay's own reference table.

Does fetch_payment_card_details expose a customer's full card number?

No. Razorpay's API reference for the expanded card object returns only the last four digits, the network, the card type, the issuer code, the cardholder name and a sub-type. No full card number, expiry date or CVV appears anywhere in the documented response. Razorpay operates as an RBI-authorised payment aggregator.

Which AI applications does the Razorpay MCP Server support?

Razorpay names Claude Desktop, Cursor and Visual Studio Code with an MCP extension, and says other MCP-compatible tools follow the same standard. Its remote setup page adds ChatGPT, Windsurf, Replit and Gemini CLI, and points Claude users at the official connector or Claude Code. Configuration details differ slightly per application.

What rate limits apply to the Razorpay MCP Server?

Razorpay publishes no numbers for MCP specifically. Its API guide describes a request rate limiter that caps requests within a time frame to maintain stability under heavy load, returning HTTP 429 when exceeded. The documented guidance is to build a retry mechanism using exponential backoff with randomisation added to the schedule.