Cashfree CLI
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Cashfree CLI
Prove a Cashfree integration works end to end — from your terminal, or from your AI agent.
Built by Mothi Venkatesh — Product Marketing at Cashfree Payments. An agent-native CLI for the developer (and the coding agent) who would rather never open the dashboard.
Most payment CLIs fetch objects. This one proves the loop: create an order, pay it, catch the webhook, verify the signature, and cross-check the API before it says "done." Sandbox by default. Runs fully offline with
--mock— no keys, no setup.
git clone https://github.com/mothivenkatesh/cashfree-cli
cd cashfree-cli && npm install && npm run build
node dist/index.js verify --mockVerifying upi success (mock)
✓ order created order_d5f8…ae97 (ACTIVE)
✓ payment initiated MOCK_pay_db0f…01a0
✓ webhook received signature valid
✓ api cross-check order_status=PAID (expected PAID)
✓ artifact .cashfree/verify-….jsonZero runtime dependencies · Node 20+ · one binary that is also an MCP server.
What it does
Closes the integration loop in five commands —
init→simulate→listen→verify→doctor. The slow part of a payment integration is testing webhooks and proving it works; this is built for exactly that.One binary, two consumers — a human at a terminal, and an AI agent over MCP. Same commands, same safety, both ways.
Runs offline —
--mockboots a built-in sandbox simulator that signs and delivers real webhooks, so the whole loop runs with no credentials.Agent-native by default —
--jsonoutput (auto-on when piped), semantic exit codes, and structured errors withsuggested_fixso an agent self-corrects.A webhook is a signal, not the truth —
verifyalways cross-checks the authoritative API before declaring success. Never the webhook payload alone.Grounded in the real API —
x-api-version: 2025-01-01, real endpoints, HMAC-SHA256 webhook verification. No invented shapes.
Related MCP server: Paytm MCP Server
What works today
✅
verify— the full loop, validated against the live Cashfree sandbox: real order → pay → simulate → webhook → signature match → API cross-check → typed artifact.✅ Payment Gateway, live-validated:
orders create/get,payments list,links create/get, order pay,simulate,refunds create,settlements get+settlements today,disputes order/get.✅ Signed webhook delivery confirmed live — the sandbox delivers signed webhooks; this CLI's signature verification matches Cashfree's exactly.
✅
listen— forward webhooks to localhost and verify signatures locally, no ngrok (mock + cross-process proven).✅ Real-mode webhooks via
--tunnel—verify --tunnel/listen --tunnelopen a cloudflared tunnel so live Cashfree webhooks reach localhost; graceful fallback if cloudflared is absent.✅ OpenAPI codegen —
npm run codegengenerates typed defs from Cashfree's live specs (PG/Payouts/Verification) for drift-checking.✅
init— scaffolds.env.example, a webhook handler with real signature verification, and anAGENTS.mdso coding agents stop guessing the API.✅
doctor— preflight: credentials, API version, connectivity, mode.✅
mcp serve— exposes the surface as 8 MCP tools over stdio JSON-RPC.✅ 10/10 tests, clean TypeScript build, zero runtime dependencies.
Roadmap — not done yet
⏳ Secure ID (PAN, bank account, UPI verification) — client built; needs signature auth + IP allowlisting handled for a CLI context; live validation pending.
⏳ Payouts (transfers, beneficiaries) — client built; needs IP allowlisting + V2 body finalized; live validation pending.
⏳ Subscriptions (UPI Autopay, plans, mandates) — commands built and grounded in the docs; pending sandbox product enablement; live validation pending.
⏳ Publish to npm for
npx cashfree-cli(package is publish-ready), plus a Homebrew tap.⏳ Migrate the client to generated types — the
npm run codegenpipeline exists; wiring the client to it is the follow-up.⏳ More
initlanguages — Python and PHP scaffolds.
The commands
# the loop
cashfree init # scaffold a working integration + AGENTS.md
cashfree simulate payment --payment-id <id> --status SUCCESS
cashfree listen --forward-to http://localhost:3000/webhook
cashfree verify --outcome success # prove it works, emit an artifact
cashfree doctor # why you are not live yet
# resources (Payment Gateway)
cashfree orders create --amount 100 # orders get <id>
cashfree payments list <order_id>
cashfree refunds create --order <id> --amount 50
cashfree links create --amount 100 # links get <id>
cashfree settlements get <order_id> # settlements today
cashfree disputes order <order_id> # disputes get <id>
# roadmap surfaces (built, validation pending)
cashfree payouts transfer --amount 500 --vpa name@bank # payouts balance
cashfree secureid pan --pan ABCDE1234F --name "Name"
cashfree subscriptions create-plan --amount 499 --interval-type MONTH
# auth + agents
cashfree login --client-id <id> --client-secret <secret>
cashfree mcp serveAdd --mock to run any of it offline. Add --json for machine output.
For AI agents
--jsonon every command, auto-on when stdout is piped (TTY detection).Semantic exit codes:
0ok ·2auth ·3validation ·4confirmation-required ·6not-found ·7rate-limited ·8network. Branch on them; don't scrape text.Structured errors with
suggested_fixandretry_after.cashfree mcp serve— the same surface as MCP tools, same gates.cashfree initwritesAGENTS.mdwith the pinned API version, base URLs, and the "webhook is not the truth" rule.
Safety
Sandbox by default.
--liveis required for production.Live money movement (payouts, refunds) also needs
--confirm, so a script or agent never moves real money by accident.Credentials live in a
0600file (OS keychain hardening on the roadmap), never in argv, never logged.
How it's built
TypeScript, compiled with
tsc, zero runtime dependencies — even the MCP server is a hand-rolled JSON-RPC stdio loop. Fast, reliablenpm install.The real HTTP client and an offline mock sandbox implement one
CashfreeClientinterface, so the CLI and the MCP server share logic and the whole thing is testable without a network.API shapes are grounded in Cashfree's public SDKs and OpenAPI specs.
Status: community project, not an official Cashfree product (yet). Payment Gateway is validated against the live sandbox; the rest is on the roadmap above. Issues and PRs welcome.
MIT © Mothi Venkatesh
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Email inboxes, webhook URLs, mock APIs and 170+ tools for coding agents over one MCP connection.
Webhook, email, WebSocket and tunnel testing for AI agents: capture, wait, verify, replay.
MCP server for building and testing AI agents with multi-model experimentation and insights.
Email inboxes, webhooks, mock APIs, 2FA codes, approvals and 170 tools for AI agents.
Related MCP Servers
FlicenseNot gradedqualityDmaintenanceEnables AI tools and agents to integrate with Cashfree's payment services (Payment Gateway, Payouts, and SecureID) using the Model Context Protocol, allowing transactions and account management through natural language.15-- AlicenseAqualityDmaintenanceEnables AI agents and developers to securely access Paytm's Payments and Business Payments APIs via MCP, allowing contextual automation of payment workflows like refunds, settlement tracking, and transaction status checks.3MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to browse a merchant catalog and place Razorpay test-mode orders with budget gating, persistent monthly limits, and full audit trails.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search a merchant's product catalog and complete UPI checkouts via Razorpay test-mode APIs, with spend mandates and full audit logging.1MIT