Unofficial · Model Context Protocol

Razorpay's documentation,
tuned for agents.

A local-first MCP server for Razorpay's docs and SDKs. Works with every major AI coding agent — they all gain three tools: search, fetch, and a validator tuned to ~30 Razorpay-specific integration bugs. No API keys. No rate limits. No telemetry.

Setup MCP See the tools

Official docs: 2,200+
Validator rules: ~30
p95 search: < 200ms
Recall@3: ≥ 0.80

Tool surface

Three tools. No more.

Each MCP tool definition costs the agent 550–1,400 tokens of context before a single user message lands. We hold the line at three — each one earning its place.

01

search_razorpay_docs

Hybrid BM25 + dense retrieval over 2,200+ official docs, fused with RRF. Returns ranked chunks with title, summary, body excerpt, code samples filtered to your SDK, and the canonical URL.

Latency p95< 200 ms
SDK auto-detectNode, Python, PHP, Java, Ruby, Go

02

get_razorpay_doc

Fetch the full markdown body for a known route or URL, plus its outgoing links. Use after search when the agent needs the entire page, not just an excerpt.

ReturnsMarkdown + links
Sourcerazorpay/markdown-docs

03

validate_razorpay_code

The killer feature. ~30 curated rules catch bugs retrieval can't: HMAC over JSON.stringify(req.body), === on signatures, hardcoded rzp_live_* keys, refunds without Idempotency-Key. Each finding cites the exact doc that explains the fix.

Rules~30 curated, citation-backed
Outputid · severity · fix · URL

Why this beats Context7

Razorpay-specific. Not a scraped subset.

Full official corpus, refreshed nightly

2,200+ docs from Razorpay's canonical markdown-docs repo. Not a third-party scrape that lags by weeks.

Code samples filtered to your SDK

Auto-detects Razorpay in package.json, composer.json, requirements.txt, Gemfile, go.mod, pom.xml — answers in your language, every time.

Validator with curated rules

~30 hand-written rules with citations to canonical docs. Not a regex catalog — every finding points the agent at the page that explains the fix.

Hybrid retrieval

BM25 for identifier-heavy queries (route names, SDK methods), dense vectors for synonyms and intent, RRF fusion on top.

Local-first, zero telemetry

Corpus and indexes ship in the npm package. No API keys, no rate limits, no phone-home. One daily SHA check to upstream — disable with RZP_MCP_AUTO_UPDATE=0.

BYO embedder, optional

Defaults to bge-small-en-v1.5 (32 MB, ~80% recall@3). Plug in Voyage or Cohere and rebuild the index for top-quality retrieval.

Install

One JSON snippet. Same wiring everywhere.

The snippet below works in every MCP-aware editor — drop it into the config file each one expects, restart, and your agent gains the three tools.

1. Install MCP server

shell

npx -y @razorpay-docs/mcp@latest --version

2. Add to your editor's MCP config

Claude Code · Cursor · VS Code · Continue · Cline · Windsurf · Zed

{
  "mcpServers": {
    "razorpay-docs": {
      "command": "npx",
      "args": ["-y", "@razorpay-docs/mcp@latest"]
    }
  }
}

Claude Code~/.claude/mcp.json
Cursor.cursor/mcp.json
VS Code Copilot Chat.vscode/mcp.json
OpenAI Codex CLI~/.codex/config.toml
Continue~/.continue/config.yaml
Windsurf~/.codeium/windsurf/mcp_config.json
Zed~/.config/zed/settings.json
Clinesettings → MCP servers

Need a deployed HTTP server instead of stdio? Run npx @razorpay-docs/mcp@latest --http --port=3030 and point clients at http://localhost:3030/.

Read the docs

Razorpay's documentation, tuned for agents.