Razorpay MCP Server

Created By
LightHeadsa year ago
Unofficial Razorpay MCP server
Overview

what is razorpay-mcp?

razorpay-mcp is an unofficial server for Razorpay's MCP (Merchant Control Panel) that allows developers to interact with Razorpay's services in a more flexible manner.

how to use razorpay-mcp?

To use razorpay-mcp, clone the repository from GitHub, install the necessary dependencies, and run the server to start interacting with Razorpay's APIs.

key features of razorpay-mcp?

  • Unofficial API server for Razorpay MCP
  • Customizable and extendable for developers
  • Supports TypeScript for better development experience

use cases of razorpay-mcp?

  1. Integrating Razorpay payment solutions into custom applications.
  2. Developing custom dashboards for merchants to manage their payments.
  3. Testing Razorpay APIs in a local environment.

FAQ from razorpay-mcp?

  • Is razorpay-mcp an official Razorpay product?

No, razorpay-mcp is an unofficial server created by developers for enhanced flexibility.

  • What programming language is used in razorpay-mcp?

razorpay-mcp is developed using TypeScript.

  • Is there any license for using razorpay-mcp?

Yes, it is licensed under the Apache-2.0 license.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
LightHeads
Star
2
Language
TypeScript
License
Apache-2.0 license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago