PAYMENTS / Razorpay
Razorpay MCP Server
Inspect Razorpay payments and settlements and optionally perform payment, refund and other merchant operations.
“server that provides seamless integration with Razorpay APIs, enabling advanced payment processing capabilities for developers and AI tools.”
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.
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.
- 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"
}
}
}
} 04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://github.com/razorpay/razorpay-mcp-server/blob/7950d51d118ca164c32b7cf0cfaa14f34f24849f/README.md
Supports: description, setup, capabilities, review, limitations
https://github.com/razorpay/razorpay-mcp-server/blob/7950d51d118ca164c32b7cf0cfaa14f34f24849f/LICENSE
Supports: license
- Pinned package metadata ↗Checked
https://github.com/razorpay/razorpay-mcp-server/blob/7950d51d118ca164c32b7cf0cfaa14f34f24849f/go.mod
Supports: install, language, review
https://github.com/razorpay/razorpay-mcp-server/blob/7950d51d118ca164c32b7cf0cfaa14f34f24849f/cmd/razorpay-mcp-server/stdio.go
Supports: review, install, access, limitations
https://github.com/razorpay/razorpay-mcp-server/blob/7950d51d118ca164c32b7cf0cfaa14f34f24849f/pkg/razorpay/server.go
Supports: review, install, access, limitations