---
title: "Razorpay MCP Server: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/razorpay/
description: "Inspect Razorpay payments and settlements and optionally perform payment, refund and other merchant operations."
---

# Razorpay MCP Server: review, setup & limitations · Undominated.ai

> Inspect Razorpay payments and settlements and optionally perform payment, refund and other merchant operations.

[← Explore all mcp servers](/mcp-servers/)

PAYMENTS / Razorpay

# Razorpay MCP Server

Inspect Razorpay payments and settlements and optionally perform payment, refund and other merchant operations.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/razorpay/razorpay-mcp-server)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 5 linked sources
 Publisher Razorpay
 Licence [MIT ↗](https://github.com/razorpay/razorpay-mcp-server/blob/7950d51d118ca164c32b7cf0cfaa14f34f24849f/LICENSE)
 Revision 7950d51d118c
 [Read what was—and wasn’t—checked ↓](#review)

“server that provides seamless integration with Razorpay APIs, enabling advanced payment processing capabilities for developers and AI tools.”

 [Razorpay · upstream description ↗](https://github.com/razorpay/razorpay-mcp-server/blob/7950d51d118ca164c32b7cf0cfaa14f34f24849f/README.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Inspect Razorpay payments and settlements and optionally perform payment, refund and other merchant operations.
- The setup documentation makes this operating boundary explicit: Merchant credentials can authorize financial mutations such as payment capture and refunds; read-only mode and toolset selection reduce the registered operations.

### A good fit for

 - Inspect Razorpay payments and settlements and optionally perform payment, refund and other merchant operations.
- For local stdio, run the documented razorpay/mcp Docker image with RAZORPAY_KEY_ID and RAZORPAY_KEY_SECRET inherited from a protected environment; start with READ_ONLY=true and the needed TOOLSETS.

### Weigh up before choosing

 - The hosted server has a different supported-tool matrix and uses Basic authentication with encoded key:secret; encoding is not encryption. Source review does not verify image or hosted deployment parity.
- Package/container parity with the pinned source and transitive dependency security were not established.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - README.md
- LICENSE
- go.mod
- cmd/razorpay-mcp-server/stdio.go
- pkg/razorpay/server.go

### Our findings

 - Merchant credentials can authorize financial mutations such as payment capture and refunds; read-only mode and toolset selection reduce the registered operations.
- The hosted server has a different supported-tool matrix and uses Basic authentication with encoded key:secret; encoding is not encryption. Source review does not verify image or hosted deployment parity.

### Not established by this review

 - No server installation, authentication, live tool execution or isolation test was performed.
- Package/container parity with the pinned source and transitive dependency security were not established.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

[Upstream setup instructions ↗](https://github.com/razorpay/razorpay-mcp-server/blob/7950d51d118ca164c32b7cf0cfaa14f34f24849f/README.md)
 - The README gives client configuration blocks rather than a one-line command. For the local server, add its docker run block with RAZORPAY_KEY_ID and RAZORPAY_KEY_SECRET. It was not run.
- Set READ_ONLY=true or a narrow TOOLSETS unless the agent must move money. Do not commit the key or secret.

### Before you start

 - Docker for the local server, or Node.js with npx for mcp-remote
- A Razorpay API key and secret

### Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

 {
 "mcpServers": {
 "razorpay-mcp-server": {
 "command": "docker",
 "args": [
 "run",
 "--rm",
 "-i",
 "-e",
 "RAZORPAY_KEY_ID",
 "-e",
 "RAZORPAY_KEY_SECRET",
 "razorpay/mcp"
 ],
 "env": {
 "RAZORPAY_KEY_ID": "your_razorpay_key_id",
 "RAZORPAY_KEY_SECRET": "your_razorpay_key_secret"
 }
 }
 }
} Copy configuration ↗

### Compatibility

Cursor · Claude Desktop · VS Code

### Implementation

Go

### Transports

stdio

### Local process with service or workstation access

 - Merchant credentials can authorize financial mutations such as payment capture and refunds; read-only mode and toolset selection reduce the registered operations.

### Cost model

Publisher service entitlements, API usage and infrastructure charges apply where applicable; the MCP source licence does not include external services.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Pinned publisher README and migration notices ↗](https://github.com/razorpay/razorpay-mcp-server/blob/7950d51d118ca164c32b7cf0cfaa14f34f24849f/README.md) Checked 2026-10-14 https://github.com/razorpay/razorpay-mcp-server/blob/7950d51d118ca164c32b7cf0cfaa14f34f24849f/README.md Supports: description, setup, capabilities, review, limitations
- [Licence text at the reviewed commit ↗](https://github.com/razorpay/razorpay-mcp-server/blob/7950d51d118ca164c32b7cf0cfaa14f34f24849f/LICENSE) Checked 2026-10-14 https://github.com/razorpay/razorpay-mcp-server/blob/7950d51d118ca164c32b7cf0cfaa14f34f24849f/LICENSE Supports: license
- [Pinned package metadata ↗](https://github.com/razorpay/razorpay-mcp-server/blob/7950d51d118ca164c32b7cf0cfaa14f34f24849f/go.mod) Checked 2026-10-14 https://github.com/razorpay/razorpay-mcp-server/blob/7950d51d118ca164c32b7cf0cfaa14f34f24849f/go.mod Supports: install, language, review
- [Pinned implementation inspected for launch or permission boundary ↗](https://github.com/razorpay/razorpay-mcp-server/blob/7950d51d118ca164c32b7cf0cfaa14f34f24849f/cmd/razorpay-mcp-server/stdio.go) Checked 2026-10-14 https://github.com/razorpay/razorpay-mcp-server/blob/7950d51d118ca164c32b7cf0cfaa14f34f24849f/cmd/razorpay-mcp-server/stdio.go Supports: review, install, access, limitations
- [Pinned implementation inspected for launch or permission boundary ↗](https://github.com/razorpay/razorpay-mcp-server/blob/7950d51d118ca164c32b7cf0cfaa14f34f24849f/pkg/razorpay/server.go) Checked 2026-10-14 https://github.com/razorpay/razorpay-mcp-server/blob/7950d51d118ca164c32b7cf0cfaa14f34f24849f/pkg/razorpay/server.go Supports: review, install, access, limitations

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Square MCP Server ↗ Gives an MCP client generic access to Square's API: discover a service's methods and types, then execute requests, locally with an access token or through Square's hosted OAuth endpoint.](/mcp-servers/square/)[### Adyen MCP Server ↗ Calls Adyen Checkout and Management APIs from an MCP client: payment sessions and links, cancels and refunds, terminals, webhooks, users and API credentials, with a flag to load only chosen tools.](/mcp-servers/adyen/)[### PayPal MCP Server ↗ Local stdio server that gives an assistant PayPal invoice, order, refund, dispute, shipment, catalog, subscription and transaction tools. The required --tools argument selects which tools load, and the environment defaults to sandbox.](/mcp-servers/paypal/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
