Cashfree MCP Server

Cashfree MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Cashfree MCP server for cashfree docs and APIs.

What you get

Before installing, ensure you have Node.js v14.x or higher installed. If you're using nvm or brew, make sure the correct version is active:

What the assistant can call

Once Cashfree MCP is connected, these are the calls the assistant has available:

• PAYMENTS_APP_ID — Your Payment Gateway client ID
• PAYMENTS_APP_SECRET — Your Payment Gateway client secret
• PAYOUTS_APP_ID — Your Payouts client ID
• PAYOUTS_APP_SECRET — Your Payouts client secret
• TWO_FA_PUBLIC_KEY_PEM_PATH — Path to your 2FA public key (required only if 2FA is enabled)
• SECUREID_APP_ID — Your SecureID client ID
• SECUREID_APP_SECRET — Your SecureID client secret
• payouts — Payouts APIs
• secureid — SecureID APIs
• Claude — Add the following configuration block to your claude_desktop_config.json
• Environment — ENV: Set to production for production environment, sandbox for sandbox (default: sandbox)
• Payouts — The Payouts tool exposed by this server

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

You will need 8 environment variables: PAYMENTS_APP_ID, PAYMENTS_APP_SECRET, PAYOUTS_APP_ID, PAYOUTS_APP_SECRET, TWO_FA_PUBLIC_KEY_PEM_PATH, SECUREID_APP_ID, SECUREID_APP_SECRET, TOOLS. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Cashfree MCP's toolset — PAYMENTS_APP_ID, PAYMENTS_APP_SECRET, PAYOUTS_APP_ID and 10 more — is a fair guide to whether it matches your workflow. It is maintained by cashfree; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 13 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Cashfree MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the cashfree mcp mcp server does with a few real requests.