The Razorpay MCP Server is a Model Context Protocol (MCP) server that provides seamless integration with Razorpay APIs, enabling advanced payment processing capabilities for developers and AI tools.
Currently, the Razorpay MCP Server provides the following tools:
Tool | Description | API |
---|---|---|
capture_payment |
Change the payment status from authorized to captured. | Payment |
fetch_payment |
Fetch payment details with ID | Payment |
fetch_payment_card_details |
Fetch card details used for a payment | Payment |
fetch_all_payments |
Fetch all payments with filtering and pagination | Payment |
update_payment |
Update the notes field of a payment | Payment |
create_payment_link |
Creates a new payment link (standard) | Payment Link |
create_payment_link_upi |
Creates a new UPI payment link | Payment Link |
fetch_all_payment_links |
Fetch all the payment links | Payment Link |
fetch_payment_link |
Fetch details of a payment link | Payment Link |
send_payment_link |
Send a payment link via SMS or email. | Payment Link |
update_payment_link |
Updates a new standard payment link | Payment Link |
create_order |
Creates an order | Order |
fetch_order |
Fetch order with ID | Order |
fetch_all_orders |
Fetch all orders | Order |
update_order |
Update an order | Order |
fetch_order_payments |
Fetch all payments for an order | Order |
create_refund |
Creates a refund | Refund |
fetch_refund |
Fetch refund details with ID | Refund |
fetch_all_refunds |
Fetch all refunds | Refund |
update_refund |
Update refund notes with ID | Refund |
fetch_multiple_refunds_for_payment |
Fetch multiple refunds for a payment | Refund |
fetch_specific_refund_for_payment |
Fetch a specific refund for a payment | Refund |
create_qr_code |
Creates a QR Code | QR Code |
fetch_qr_code |
Fetch QR Code with ID | QR Code |
fetch_all_qr_codes |
Fetch all QR Codes | QR Code |
fetch_qr_codes_by_customer_id |
Fetch QR Codes with Customer ID | QR Code |
fetch_qr_codes_by_payment_id |
Fetch QR Codes with Payment ID | QR Code |
fetch_payments_for_qr_code |
Fetch Payments for a QR Code | QR Code |
close_qr_code |
Closes a QR Code | QR Code |
fetch_all_settlements |
Fetch all settlements | Settlement |
fetch_settlement_with_id |
Fetch settlement details | Settlement |
fetch_settlement_recon_details |
Fetch settlement reconciliation report | Settlement |
create_instant_settlement |
Create an instant settlement | Settlement |
fetch_all_instant_settlements |
Fetch all instant settlements | Settlement |
fetch_instant_settlement_with_id |
Fetch instant settlement with ID | Settlement |
fetch_all_payouts |
Fetch all payout details with A/c number | Payout |
fetch_payout_by_id |
Fetch the payout details with payout ID | Payout |
- Workflow Automation: Automate your day to day workflow using Razorpay MCP Server.
- Agentic Applications: Building AI powered tools that interact with Razorpay's payment ecosystem using this Razorpay MCP server.
- Docker
- Golang (Go)
- Git
To run the Razorpay MCP server, use one of the following methods:
You can use the public Razorpay image directly. No need to build anything yourself - just copy-paste the configurations below and make sure Docker is already installed.
Note: To use a specific version instead of the latest, replace
razorpay/mcp
withrazorpay/mcp:v1.0.0
(or your desired version tag) in the configurations below. Available tags can be found on Docker Hub.
This will use the public razorpay image
Add the following to your claude_desktop_config.json
:
{
"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"
}
}
}
}
Please replace the your_razorpay_key_id
and your_razorpay_key_secret
with your keys.
- Learn about how to configure MCP servers in Claude desktop: Link
- How to install Claude Desktop: Link
Add the following to your VS Code settings (JSON):
{
"mcp": {
"inputs": [
{
"type": "promptString",
"id": "razorpay_key_id",
"description": "Razorpay Key ID",
"password": false
},
{
"type": "promptString",
"id": "razorpay_key_secret",
"description": "Razorpay Key Secret",
"password": true
}
],
"servers": {
"razorpay": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"RAZORPAY_KEY_ID",
"-e",
"RAZORPAY_KEY_SECRET",
"razorpay/mcp"
],
"env": {
"RAZORPAY_KEY_ID": "${input:razorpay_key_id}",
"RAZORPAY_KEY_SECRET": "${input:razorpay_key_secret}"
}
}
}
}
}
Learn more about MCP servers in VS Code's agent mode documentation.
You need to clone the Github repo and build the image for Razorpay MCP Server using docker
. Do make sure docker
is installed and running in your system.
# Run the server
git clone https://github.com/razorpay/razorpay-mcp-server.git
cd razorpay-mcp-server
docker build -t razorpay-mcp-server:latest .
Once the razorpay-mcp-server:latest docker image is built, you can replace the public image(razorpay/mcp
) with it in the above configurations.
You can directly build from the source instead of using docker by following these steps:
# Clone the repository
git clone https://github.com/razorpay/razorpay-mcp-server.git
cd razorpay-mcp-server
# Build the binary
go build -o razorpay-mcp-server ./cmd/razorpay-mcp-server
Once the build is ready, you need to specify the path to the binary executable in the command
option. Here's an example for VS Code settings:
{
"razorpay": {
"command": "/path/to/razorpay-mcp-server",
"args": ["stdio","--log-file=/path/to/rzp-mcp.log"],
"env": {
"RAZORPAY_KEY_ID": "<YOUR_ID>",
"RAZORPAY_KEY_SECRET" : "<YOUR_SECRET>"
}
}
}
The server requires the following configuration:
RAZORPAY_KEY_ID
: Your Razorpay API key IDRAZORPAY_KEY_SECRET
: Your Razorpay API key secretLOG_FILE
(optional): Path to log file for server logsTOOLSETS
(optional): Comma-separated list of toolsets to enable (default: "all")READ_ONLY
(optional): Run server in read-only mode (default: false)
The server supports the following command line flags:
--key
or-k
: Your Razorpay API key ID--secret
or-s
: Your Razorpay API key secret--log-file
or-l
: Path to log file--toolsets
or-t
: Comma-separated list of toolsets to enable--read-only
: Run server in read-only mode
You can use the standard Go debugging tools to troubleshoot issues with the server. Log files can be specified using the --log-file
flag (defaults to ./logs)
This project is licensed under the terms of the MIT open source license. Please refer to LICENSE for the full terms.