Razorpay MCP Server for CursorGive Cursor instant access to 12 tools to Create Customer, Create Order, Get Order, and more
Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.
Ask AI about this App Connector for Cursor
The Razorpay app connector for Cursor is a standout in the Industry Titans category — giving your AI agent 12 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Razorpay and 3,400+ MCP Servers from a single visual interface.




{
"mcpServers": {
"razorpay": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About Razorpay MCP Server
Connect your Razorpay account to any AI agent and take full control of your payment orchestration through natural conversation. Razorpay is India's leading payments solution, and this integration allows you to retrieve payment metadata, create customer orders, and manage financial transactions directly from your chat interface.
Cursor's Agent mode turns Razorpay into an in-editor superpower. Ask Cursor to generate code using live data from Razorpay and it fetches, processes, and writes. all in a single agentic loop. 12 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
What you can do
- Order & Payment Orchestration — List all managed orders and retrieve detailed metadata, including creating new payment orders programmatically.
- Transaction Lifecycle Management — Access and monitor payment statuses and retrieve technical metadata directly from the AI interface to ensure successful checkouts.
- Customer CRM Control — List and search through your customer database to maintain accurate records via natural language.
- Subscription & Invoice Intelligence — Access recurring billing plans and monitor invoice statuses to ensure your revenue streams are always optimized.
- Operational Monitoring — Track settlements, transfers, and retrieve account profile metadata using simple AI commands.
The Razorpay MCP Server exposes 12 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 12 Razorpay tools available for Cursor
When Cursor connects to Razorpay through Vinkius, your AI agent gets direct access to every tool listed below — spanning razorpay, payment-gateway, fintech-api, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
Create a new customer
Amount should be in smallest currency subunit (e.g., 50000 for ₹500.00). Create a new payment order
Get details of a specific order
Get details of a specific payment
List all customers
List all invoices
List all payment orders
List all payments
List all refunds
List all settlements
List all subscriptions
List all transfers
Connect Razorpay to Cursor via MCP
Follow these steps to wire Razorpay into Cursor. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Open MCP Settings
Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"Add the server config
mcp.json file that opensSave the file
Start using Razorpay
Why Use Cursor with the Razorpay MCP Server
Cursor AI Code Editor provides unique advantages when paired with Razorpay through the Model Context Protocol.
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Razorpay + Cursor Use Cases
Practical scenarios where Cursor combined with the Razorpay MCP Server delivers measurable value.
Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP
Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically
Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates
Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data
Example Prompts for Razorpay in Cursor
Ready-to-use prompts you can give your Cursor agent to start working with Razorpay immediately.
"List all active customers in my Razorpay account."
"Show me all payment transactions from today with their statuses and settlement details."
"Create a new payment link for ₹15,000 for the consulting invoice with 7-day expiry."
Troubleshooting Razorpay MCP Server with Cursor
Common issues when connecting Razorpay to Cursor through the Vinkius, and how to resolve them.
Tools not appearing in Cursor
Server shows as disconnected
Razorpay + Cursor FAQ
Common questions about integrating Razorpay MCP Server with Cursor.
What is Agent mode and why does it matter for MCP?
Where does Cursor store MCP configuration?
mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.