Razorpay MCP Server
Deploy and configure the Razorpay MCP server with authentication, use cases, security notes, and India-ready hosting guidance.
Quick Answer / TL;DR
The Razorpay MCP server exposes Razorpay capabilities to AI clients through scoped tools, resources, and JSON-RPC calls, using Razorpay API Key & Secret for authentication.
Key Takeaways
- Authentication: Razorpay API Key & Secret.
- Category: Finance.
- Best first use case: Query daily transaction totals.
- Use environment variables and least-privilege scopes for production.
Integration overview
Optimized for Indian startups. Audit transactions, trace refund requests, and manage Razorpay Route splits.
Use this connector when an AI assistant such as Claude, Cursor, or a custom agent needs a governed path into Razorpay. Keep the server focused on the approved workflows instead of exposing a whole account or admin surface.
For Indian teams, deploy the connector near the users and the data source, then add request IDs, redaction, and audit logs before connecting production data.
| Field | Value |
|---|---|
| Connector | Razorpay MCP Server |
| Category | Finance |
| Authentication | Razorpay API Key & Secret |
| Production route | /servers/razorpay-mcp-server/ |
Features and use cases
Razorpay is most useful when the agent has a narrow job to complete and the server can validate every argument before execution.
Start with read-only or low-risk tools. Add write operations only after approval prompts, scoped credentials, and logging are working.
| Capability | Recommended guardrail |
|---|---|
| Order status audit | Allow with scoped read access |
| Refund checks | Allow with scoped read access |
| Settlements analytics | Allow with scoped read access |
| Route allocations | Allow with scoped read access |
Local and hosted configuration
Configure Razorpay with credentials stored in environment variables. Do not hardcode tokens in prompts, repositories, screenshots, or browser-visible code.
The local configuration pattern works for a single developer. Hosted deployments should add TLS, bearer-token authentication, health checks, and monitoring.
{
"mcpServers": {
"razorpay": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-razorpay"],
"env": {
"RAZORPAY_TOKEN": "${RAZORPAY_TOKEN}"
}
}
}
}Security and permissions
Protect Razorpay API Key & Secret credentials with least privilege, rotation, and separate environments for development, staging, and production.
Review every tool output for sensitive data before letting it enter model context. For regulated Indian workflows, add DPDP-aware redaction and retention controls.
{
"server": "razorpay-mcp-server",
"auth": "Razorpay API Key & Secret",
"policy": {
"leastPrivilege": true,
"redactSecrets": true,
"requireApprovalForWrites": true,
"auditToolCalls": true
}
}Razorpay MCP Server FAQs
Direct answers for developers, operators, and Indian teams evaluating MCP.