PhonePe's Official MCP Server: Documentation, Not Payments

PhonePe publishes an official, open-source MCP server at phonepe/phonepe-pg-docs-mcp on GitHub. The name is precise about what it is: a documentation and knowledge-base server for the PhonePe Payment Gateway (PG), aimed at developers integrating PhonePe PG — it is not a server that lets an AI assistant move money or initiate transactions on your behalf.

What It Exposes: A Three-Tier Knowledge Base

The server organizes documentation access into three tiers, each trading off speed for depth:

• Tier 1 — Instant (~0ms): a curated YAML knowledge base covering product features, FAQs, and error codes.
• Tier 2 — Fast (~2ms): full-text search across 241 documentation sections using SQLite FTS5.
• Tier 3 — Fallback (~1–2s): live web scraping from developer.phonepe.com when the first two tiers don't have an answer.

Ten tools sit on top of this, including ask_knowledge_base, list_products, get_feature_support, get_error_code_info, and search_docs, plus endpoint and environment reference lookups.

Installing It

The package is distributed on PyPI and installable either way:

uvx --from phonepe-pg-docs-mcp phonepe-pg-docs
# or
pip install phonepe-pg-docs-mcp

Configure it in Claude Desktop, Cursor, GitHub Copilot, or Windsurf by pointing your client's MCP config at the installed server, then ask natural questions directly in your editor — "Does PhonePe support recurring payments?" or "What does error code X mean?" — without leaving your IDE to search docs manually.

What It Is Not

This is the important part: no PhonePe credentials are required, because the server doesn't touch real payment infrastructure at all. It doesn't process transactions, doesn't handle merchant credentials, and doesn't initiate UPI transfers. It's purely a reference tool for the integration and debugging phase of building against PhonePe's real Payment Gateway API — the actual payment calls still go through your own direct integration with PhonePe PG, following their standard authentication and API flow.

Why This Distinction Matters

It's easy to see "PhonePe" and "MCP server" in the same sentence and assume it means AI-initiated payments, especially given how Zomato's MCP server does handle real checkout. PhonePe's is a different category entirely — a documentation accelerator for engineers, not a payments API exposed to an LLM. If you need actual UPI payment initiation through an AI client, look at platform-specific servers that have built that capability deliberately (with the safeguards that requires), rather than assuming a docs server implies transaction capability.