Cashfree Mcp

io.github.cashfreePublished by GitHub account cashfreev1.0.0Updated Oct 25, 2026

Cashfree MCP server for cashfree docs and APIs

Overview

AI-generated overview

Cashfree MCP server that lets an AI assistant search Cashfree docs and call Payment Gateway, Payouts and SecureID APIs from a local process.

What you can do
Search Cashfree developer documentation and get help with input-source errors for Payment Gateway calls. Create, inspect and cancel payment links, and list their orders. Create and read orders, eligible payment methods, payments, refunds, settlements and disputes, and accept or contest disputes. Simulate and fetch test payments. Initiate single and batch payouts, check transfer status, authorize, and create, deactivate or check Cashgrams. Verify name matches and generate, check or deactivate KYC links through SecureID.
When to use it
Use it when you want an assistant to work with Cashfree payments, payouts or identity verification from a desktop MCP client, for example to look up documentation, inspect orders and settlements, or prepare refunds and transfers. Start with sandbox credentials to test flows before pointing it at production.
Requirements
Runs locally as an npm package on Node.js (README asks for v14 or higher, with a note to use 20.18.1 or later on newer Node). A Cashfree account with API credentials: PAYMENTS_APP_ID and PAYMENTS_APP_SECRET, PAYOUTS_APP_ID and PAYOUTS_APP_SECRET, SECUREID_APP_ID and SECUREID_APP_SECRET. Set ENV to sandbox or production and TOOLS to the modules to enable (pg, payouts, secureid). TWO_FA_PUBLIC_KEY_PEM_PATH is needed only if 2FA is enabled.
Before you install
The server holds live payment, payout and KYC API secrets in its environment. It can move money: standard and batch transfers, Cashgrams, refunds and payment links all act on your Cashfree account, and ENV defaults to sandbox but can be set to production. It can also accept or contest disputes and deactivate links. Use sandbox keys first, enable only the modules you need, and keep secrets out of shared configuration files.

Installation

In SourceWeft

  1. Open Cashfree Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[MseeP.ai Security Assessment Badge]

Cashfree MCP Server

Cashfree MCP server allows AI tools and agents to integrate with Cashfree APIs (Payment Gateway, Payouts, and SecureID) using the Model Context Protocol (MCP).

Setup

Clone the Repository

bash
git clone https://github.com/cashfree/cashfree-mcp.gitcd cashfree-mcp

Install Dependencies

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:

bash
node -v# Should output v14.x or higher
Step 1: Install project dependencies
bash
npm install

This will install all required packages listed in package.json.

💡 If you're using Node.js >=18, you might face peer dependency issues with packages like undici. In that case, upgrade Node.js to >=20.18.1 or adjust the package version if needed.

Step 2: Build the project
bash
npm run build

This compiles the source files to the dist/ directory, which is required to run the MCP server.

🛠️ If you see errors related to missing files in /dist, ensure you've run the build step successfully.

Configuration

You will need a Cashfree account with API credentials (we support both sandbox and production keys). You can use Cashfree MCP in your favorite client, some sample configurations are shown below:

Claude

Add the following configuration block to your claude_desktop_config.json

json
{  "mcpServers": {    "cashfree": {      "command": "node",      "args": ["/path/to/cashfree-mcp/dist/index.js"],      "env": {        "PAYMENTS_APP_ID": "YOUR_PG_CLIENT_ID",        "PAYMENTS_APP_SECRET": "YOUR_PG_CLIENT_SECRET",        "PAYOUTS_APP_ID": "YOUR_PAYOUTS_CLIENT_ID",        "PAYOUTS_APP_SECRET": "YOUR_PAYOUTS_CLIENT_SECRET",        "TWO_FA_PUBLIC_KEY_PEM_PATH": "/path/to/public_key.pem",        "SECUREID_APP_ID": "YOUR_SECUREID_CLIENT_ID",        "SECUREID_APP_SECRET": "YOUR_SECUREID_CLIENT_SECRET",        "TOOLS": "pg,payouts,secureid",        "ENV": "sandbox",        "ELICITATION_ENABLED": "true"      }    }  }}

VS Code

Add the following configuration block to your VS Code settings

json
{  "mcp": {    "inputs": [],    "servers": {      "cashfree": {        "command": "node",        "args": ["/path/to/cashfree-mcp/dist/index.js"],        "env": {          "PAYMENTS_APP_ID": "YOUR_PG_CLIENT_ID",          "PAYMENTS_APP_SECRET": "YOUR_PG_CLIENT_SECRET",          "PAYOUTS_APP_ID": "YOUR_PAYOUTS_CLIENT_ID",          "PAYOUTS_APP_SECRET": "YOUR_PAYOUTS_CLIENT_SECRET",          "TWO_FA_PUBLIC_KEY_PEM_PATH": "/path/to/public_key.pem",          "SECUREID_APP_ID": "YOUR_SECUREID_CLIENT_ID",          "SECUREID_APP_SECRET": "YOUR_SECUREID_CLIENT_SECRET",          "TOOLS": "pg,payouts,secureid",          "ENV": "sandbox",          "ELICITATION_ENABLED": "true"        }      }    }  }}

API Credentials

Set the following environment variables for each service: Payment Gateway:

  • PAYMENTS_APP_ID: Your Payment Gateway client ID
  • PAYMENTS_APP_SECRET: Your Payment Gateway client secret

Payouts:

  • 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:

  • SECUREID_APP_ID: Your SecureID client ID
  • SECUREID_APP_SECRET: Your SecureID client secret
  • TWO_FA_PUBLIC_KEY_PEM_PATH: Path to your 2FA public key (required only if 2FA is enabled)

Environment

ENV: Set to production for production environment, sandbox for sandbox (default: sandbox)

Tools Configuration

TOOLS: Comma-separated list of modules to enable. Available options:

  • pg: Payment Gateway APIs
  • payouts: Payouts APIs
  • secureid: SecureID APIs

Elicitation Configuration

ELICITATION_ENABLED: Set to true to enable interactive parameter elicitation, false to disable (default: false)

When enabled, the MCP server will prompt users for missing required parameters instead of failing with validation errors. This provides a more interactive experience by asking users to provide values for required fields that weren't initially supplied.

Tools

Cashfree MCP has the following tools available, grouped by the product category

Payment Gateway (PG)

Tool NameDescription
searchSearch across the Cashfree Payments Developer Documentation.
get-input-source-helpGet comprehensive instructions for handling input source variable errors.
create-payment-linkCreate a new payment link.
fetch-payment-link-detailsView all details and status of a payment link.
cancel-payment-linkCancel an active payment link. No further payments can be done against cancelled links
get-orders-for-a-payment-linkView all order details for a payment link.
create-orderCreate orders with Cashfree to get a payment_sessions_id for transactions
get-orderFetch order details using order_id
get-order-extendedGet extended order data like address, cart, offers, customer details etc
get-eligible-payment-methodsGet eligible payment methods for a given order amount and ID
get-payments-for-an-orderView all payment details for an order.
get-payment-by-idView payment details of an order for a Payment ID.
create-refundInitiate refunds.
get-all-refunds-for-an-orderFetch all refunds processed against an order.
get-refundFetch a specific refund processed on your Cashfree Account.
get-all-settlementsGet all settlement details by specifying the settlement ID, settlement UTR, or date range.
get-split-and-settlement-details-by-order-id-v2-0Get split and settlement details, including settled/unsettled transactions for vendors in an order
get-settlements-by-order-idView all the settlements of a particular order.
get-disputes-by-order-idGet all dispute details by Order ID
get-disputes-by-payment-idGet all dispute details by Payment ID
get-disputes-by-dispute-idGet dispute details by Dispute ID
accept-dispute-by-dispute-idAccept a dispute by its Dispute ID
submit-evidence-to-contest-the-dispute-by-dispute-idSubmit evidence to contest a dispute
simulate-paymentSimulate payment for testing. Requires prior order creation
fetch-simulationFetch simulated payment details

Payouts

Tool NameDescription
standard-transfer-v2Initiate an amount transfer at Cashfree Payments.
get-transfer-status-v2Get the status of an initiated transfer.
batch-transfer-v2Initiate a batch transfer request at Cashfree Payments.
get-batch-transfer-status-v2Get the status of an initiated batch transfer.
authorizeAuthenticate with the Cashfree system and obtain the authorization bearer token.
create-cashgramCreate a Cashgram.
deactivate-cashgramDeactivate a Cashgram.
get-cashgram-statusGet the status of a created Cashgram.

SecureID

Tool NameDescription
verify-name-matchVerify names with variations.
generate-kyc-linkGenerate a verification form for KYC information.
get-kyc-link-statusGet the status of a KYC verification form.
generate-static-kyc-linkGenerate a static KYC link.
deactivate-static-kyc-linkDeactivate a static KYC link.

License

This project is licensed under the terms of the MIT open source license. Please refer to LICENSE for the full terms.

Documentation

For detailed API documentation, visit the Cashfree API Documentation.

Support

For support, contact [email protected] or raise an issue in the GitHub repository.

Source: README.md at commit 04a6278

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.