The Zwitch MCP Server exposes 11 tools covering documentation search and integration code generation. Every tool is read-only and safe to invoke — nothing here moves money or mutates state.
Documentation — 4 tools
Backed by semantic search over the live Zwitch developer docs.
| Tool | Description |
|---|---|
search_docs | Semantic search across Zwitch developer documentation. Pass a natural-language query; get ranked snippets with the source path. |
list_docs | Browse all documentation pages by category (e.g. accounts, payouts, collections, verification, webhooks). |
read_doc | Read the full content of a specific documentation page by path. |
zwitch_setup | Check connection status and which tools are available in your session. Useful as a first call to verify the integration. |
Integration Guides — 7 tools
Each tool generates ready-to-paste integration code.
Common parameters:
| Parameter | Required | Values |
|---|---|---|
language | yes | nodejs, python, go, php |
framework | no | Optional, varies per language (e.g. express for Node.js, flask / django for Python) |
Tools:
| Tool | Description |
|---|---|
get_payment_gateway_guide | Payment gateway integration with Layer.js checkout — order creation, client-side launch, server-side verification |
get_account_setup_guide | Virtual account provisioning + KYC onboarding flow |
get_beneficiary_guide | Beneficiary CRUD with account scoping |
get_payouts_guide | Single transfers and bulk transfers, including bulk reference tracking |
get_collections_guide | UPI collections plus the Zwitch settlement model |
get_verification_guide | KYC verification suite — PAN, bank account (penny + pennyless), VPA, name match |
get_webhook_guide | Unified webhook handler covering all event types, with signature verification |
Each guide returns a single, cohesive code module — not fragments. Copy it into your project as the starting point.