Skip to main content
mcpSource-backedReview first Safety Privacy

Razorpay MCP Server for Claude

Automate payments, orders, refunds, settlements, and Razorpay checkout integrations from Claude with the official Razorpay MCP Server — hosted remotely at mcp.razorpay.com or self-hosted, covering 40+ payment API tools for South Asia's leading payments platform.

HarnessClaude CodeCodexCursorClaude Desktop
Review first review before installing

Open the source and read safety notes before installing.

Safety notes

  • The server can create orders, capture payments, create refunds, and generate payment links — these are live financial operations on your Razorpay account.
  • Use test mode credentials (key IDs starting with `rzp_test_`) during development to avoid real charges.
  • Treat your Razorpay Key Secret and Base64-encoded credentials as sensitive secrets — do not commit them to version control.

Privacy notes

  • Payment details, customer information, refund records, and settlement reports from your Razorpay account are surfaced in Claude's context.
  • The remote MCP server is hosted by Razorpay — requests go through Razorpay's infrastructure; review Razorpay's privacy policy for data handling.

Prerequisites

  • A Razorpay account with Key ID and Key Secret from the Dashboard → Settings → API Keys.
  • Base64-encode your credentials: `echo -n 'key_id:key_secret' | base64` and use the result as the Authorization value.
  • Node.js with `npx` installed.
  • An MCP client such as Claude Code or Claude Desktop.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
10 minutes
Difficulty
intermediate
Tool listing metadata
Disclosure
Razorpay is a commercial payments platform. The MCP server is officially maintained by Razorpay.
Full copyable content
{
  "mcpServers": {
    "razorpay": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.razorpay.com/mcp",
        "--header",
        "Authorization:Basic YOUR_BASE64_KEY_SECRET"
      ]
    }
  }
}

About this resource

Overview

The Razorpay MCP Server is the official Model Context Protocol server from Razorpay — India's leading payment gateway. It provides 40+ tools for payments, orders, refunds, payment links, UPI/QR codes, settlements, payouts, recurring payment tokens, and an AI-powered checkout integration generator.

The recommended setup uses Razorpay's hosted remote server at https://mcp.razorpay.com/mcp with Basic auth using your API key and secret. A self-hosted Go binary option is also available for on-premises deployments. Licensed under MIT.

Key capabilities

  • Payment management — fetch, capture, initiate, and update payments; resend/submit OTP for authentication flows.
  • Orders — create, fetch, update orders and retrieve associated payments.
  • Payment links — create standard and UPI payment links; send via SMS/email.
  • Refunds — create instant refunds and fetch refund status.
  • QR codes — generate, fetch, and close Razorpay QR codes.
  • Settlements — fetch settlement reports and instant settlement details.
  • Payouts — query payout details from Razorpay X.
  • Tokens — list and revoke saved recurring payment methods.
  • Checkout integrationdetect_stack and integrate_razorpay_checkout generate end-to-end Razorpay Standard Checkout code for your detected framework.

Tools (40+)

Tool Category
fetch_payment, capture_payment, fetch_all_payments Payments
create_order, fetch_order, fetch_order_payments Orders
create_payment_link, create_payment_link_upi, send_payment_link Payment Links
create_refund, fetch_refund, fetch_all_refunds Refunds
create_qr_code, fetch_qr_code, close_qr_code QR Codes
fetch_all_settlements, fetch_settlement_recon_details Settlements
fetch_all_payouts, fetch_payout_by_id Payouts
fetch_tokens, revoke_token Recurring Tokens
detect_stack, integrate_razorpay_checkout Checkout Integration

How it compares

Server Payments Refunds Settlement recon Checkout codegen Auth
Razorpay MCP Yes Yes Yes Yes Basic (key|secret)
Stripe MCP Yes Yes No No API key
PayPal MCP Yes Yes No No OAuth
Square MCP Yes Yes Limited No API key

Razorpay's integrate_razorpay_checkout tool is unique — it detects your project's framework and generates a complete Razorpay Standard Checkout integration, including frontend and backend code.

Installation

Claude Code (remote server)

# Base64-encode your credentials first:
echo -n 'rzp_live_KEY_ID:KEY_SECRET' | base64

# Then add the MCP server:
claude mcp add razorpay \
  -e AUTH_HEADER="Basic <your-base64-credentials>" \
  -- npx mcp-remote https://mcp.razorpay.com/mcp \
  --header "Authorization:${AUTH_HEADER}"

Claude Desktop

{
  "mcpServers": {
    "razorpay": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.razorpay.com/mcp",
        "--header",
        "Authorization: Basic YOUR_BASE64_KEY_SECRET"
      ]
    }
  }
}

Local / self-hosted

See the GitHub repository for the self-hosted Go binary build instructions.

Requirements

  • A Razorpay account with API credentials (Key ID and Key Secret).
  • Node.js with npx (for mcp-remote).
  • An MCP client (Claude Code or Claude Desktop).

Security

  • Use test credentials (rzp_test_...) during development; switch to live credentials for production after verifying workflows.
  • Never commit credentials or Base64-encoded key secrets to version control.
  • Payment operations are live — always confirm financial actions before executing.

Source Verification Notes

Verified on 2026-06-18:

  • Official GitHub repository razorpay/razorpay-mcp-server (MIT, 225 stars) documents the hosted remote MCP endpoint at https://mcp.razorpay.com/mcp, the mcp-remote connection pattern with Authorization: Basic <Base64(key:secret)> header, all 40+ tools (payments, orders, refunds, QR codes, settlements, payouts, tokens, checkout codegen), and the self-hosted Go binary option.
  • Claude Code MCP documentation at code.claude.com/docs/en/mcp describes the MCP connector pattern used above.

Source citations

Add this badge to your README

Show that Razorpay MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/razorpay-mcp-server.svg)](https://heyclau.de/entry/mcp/razorpay-mcp-server)

How it compares

Razorpay MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

FieldRazorpay MCP Server for Claude

Automate payments, orders, refunds, settlements, and Razorpay checkout integrations from Claude with the official Razorpay MCP Server — hosted remotely at mcp.razorpay.com or self-hosted, covering 40+ payment API tools for South Asia's leading payments platform.

Open dossier
Adyen MCP Server for Claude

Integrate with Adyen's payment platform from Claude — create payment sessions and links, cancel/refund payments, manage terminals, webhooks, API credentials, and merchant accounts — with the official Adyen Model Context Protocol server covering Checkout and Management APIs.

Open dossier
Canva MCP Server for Claude

Browse, summarize, and generate Canva designs directly from Claude

Open dossier
Customer.io MCP Server for Claude

Manage Customer.io from Claude — create segments, inspect customer profiles, send broadcasts and campaigns, work with journeys, and access the full Journeys UI and CDP Data Pipelines APIs — with the official Customer.io remote MCP server.

Open dossier
Trust
Install riskReview firstReview firstLow riskReview first
Notes Safety Privacy Safety Privacy Safety Privacy Safety Privacy
Categorymcpmcpmcpmcp
Sourcesource-backedsource-backedfirst-partysource-backed
AuthorRazorpayAdyenCanvaCustomer.io
Added2026-06-182026-06-182025-09-182026-06-18
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo
Safety notesThe server can create orders, capture payments, create refunds, and generate payment links — these are live financial operations on your Razorpay account. Use test mode credentials (key IDs starting with `rzp_test_`) during development to avoid real charges. Treat your Razorpay Key Secret and Base64-encoded credentials as sensitive secrets — do not commit them to version control.This server can create payment sessions, generate payment links, cancel authorized payments, and initiate refunds — these are live financial operations. Use `--env=TEST` during development with Adyen's test API keys to avoid live transactions. Restrict enabled tools to only what is needed via the `--tools` parameter (e.g., `--tools=create_session,list_merchants`).Limit access to the intended Canva team or projects and review generated or modified designs before publishing or sharing them.The server exposes three tool categories: read (GET), write (POST/PUT/PATCH), and delete (DELETE) — approve each independently. By default, the MCP server cannot delete customer profiles or modify live active campaigns — only create new items — reducing accidental audience impact. Write and delete tools can trigger real sends and modify live data; review Claude's proposed actions before confirming.
Privacy notesPayment details, customer information, refund records, and settlement reports from your Razorpay account are surfaced in Claude's context. The remote MCP server is hosted by Razorpay — requests go through Razorpay's infrastructure; review Razorpay's privacy policy for data handling.Payment session data, merchant account details, terminal configurations, and webhook payloads from your Adyen instance are surfaced in Claude's context. Your Adyen API key is passed as a CLI argument — use environment variable substitution (e.g., `--adyenApiKey=${ADYEN_API_KEY}`) to avoid exposing it in config files.Design contents, uploaded media, brand assets, templates, and Canva account metadata may be sent to the MCP client and model.Customer profiles, segment definitions, journey configurations, and campaign data from your Customer.io workspace are surfaced in Claude's context. Customer.io's MCP server is authenticated via OAuth — no API keys are stored in your MCP config.
Prerequisites
  • A Razorpay account with Key ID and Key Secret from the Dashboard → Settings → API Keys.
  • Base64-encode your credentials: `echo -n 'key_id:key_secret' | base64` and use the result as the Authorization value.
  • Node.js with `npx` installed.
  • An MCP client such as Claude Code or Claude Desktop.
  • An Adyen account with a web service API key (customer area → Developers → API credentials).
  • The API key user must have appropriate roles: Checkout Webservice, Management API - Accounts Read, Merchant PAL Webservice, and others depending on tools used (see docs).
  • Node.js with `npx` available.
  • An MCP client such as Claude Code or Claude Desktop.
  • Canva account (Canva Pro subscription recommended for full API access and team features)
  • OAuth 2.0 authentication configured via Canva Developer Console (https://www.canva.dev/)
  • HTTP transport support in MCP client (required for Canva MCP server)
  • Internet connection for accessing Canva API (https://api.canva.com endpoints)
  • A Customer.io account — authenticate via OAuth when prompted on first tool use.
  • EU customers should use `https://mcp-eu.customer.io/mcp` instead of the US endpoint.
  • An MCP client such as Claude Code or Claude Desktop (MCP requires a paid Claude plan).
Install
claude mcp add razorpay -e AUTH_HEADER="Basic YOUR_BASE64_KEY_SECRET" -- npx mcp-remote https://mcp.razorpay.com/mcp --header "Authorization:${AUTH_HEADER}"
claude mcp add adyen -- npx -y @adyen/mcp --adyenApiKey=YOUR_ADYEN_API_KEY --env=TEST
claude mcp list && claude mcp status canva
claude mcp add --transport http customerio https://mcp.customer.io/mcp
Config
{
  "mcpServers": {
    "razorpay": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.razorpay.com/mcp",
        "--header",
        "Authorization: Basic ${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "YOUR_BASE64_ENCODED_KEY_SECRET"
      }
    }
  }
}
{
  "mcpServers": {
    "adyen": {
      "command": "npx",
      "args": [
        "-y", "@adyen/mcp",
        "--adyenApiKey=YOUR_ADYEN_API_KEY",
        "--env=LIVE",
        "--livePrefix=YOUR_LIVE_URL_PREFIX"
      ]
    }
  }
}
{
  "mcpServers": {
    "canva": {
      "url": "https://mcp.canva.com/mcp",
      "type": "http"
    }
  }
}
{
  "mcpServers": {
    "customerio": {
      "type": "http",
      "url": "https://mcp.customer.io/mcp"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.