MCP server for Interswitch APIs: payments, transfers, Verve cards, airtime, and paycodes.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-dairus01-interswitch-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Model Context Protocol (MCP) server that enables AI assistants to interact with Interswitch APIs for payments, transfers, VAS, cardless paycodes, Transaction Search, Card 360, lending, payouts, agency banking, and fintech card-processing utilities.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in finance
Real-time financial market data: stocks, forex, crypto, commodities, and economic indicators
A Model Context Protocol (MCP) server that provides AI assistants with direct access to the Spreedly payments API. Enables LLMs to manage gateways, process transactions, tokenize payment methods, and more, through structured, validated tool calls.
MCP server for InsightSentry financial data API - market data, options, screeners, and more
A Model Context Protocol server allows Clients to interact with Xero
MCP Security Weekly
Get CVE alerts and security updates for io.github.Dairus01/interswitch-mcp-server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server that enables AI assistants to interact with Interswitch APIs for payments, transfers, VAS, cardless paycodes, Transaction Search, Card 360, lending, payouts, agency banking, and fintech card-processing utilities.
[!WARNING] Public Preview: This MCP server is currently in public preview. It supports both Interswitch sandbox and production environments, so use cautiously, start with read-only mode, and report any issues you encounter.
Install and run via npm (recommended):
npx interswitch-mcp-server
Or install globally:
npm install -g interswitch-mcp-server
interswitch-mcp-server
Or for local development, clone and build:
git clone https://github.com/Dairus01/Interswitch-mcp-server.git
cd Interswitch-mcp-server
npm install
npm run build
Then configure your MCP client to use the server (see Client Integration).
| Environment Variable | Purpose |
|---|---|
INTERSWITCH_CLIENT_ID | Core OAuth2 client ID for payments, transfers, VAS, cardless, lending, transfer service, and payouts |
INTERSWITCH_CLIENT_SECRET | Core OAuth2 client secret |
INTERSWITCH_ENV | API environment: sandbox or production; defaults to sandbox |
INTERSWITCH_READ_ONLY | Set true to block write tools before any API call; defaults to false |
INTERSWITCH_REQUIRE_CONFIRMATION | Compatibility setting. Tool confirmation is enforced by tool mode and risk. |
INTERSWITCH_MERCHANT_CODE | Merchant code for payment operations that require it |
INTERSWITCH_PAYABLE_CODE | Payable code for payment operations that require it |
INTERSWITCH_INITIATING_ENTITY_CODE | Initiating entity code for transfer operations |
INTERSWITCH_TERMINAL_ID | Terminal ID for operations that require terminal identification |
CARD360_CLIENT_ID | Separate Card 360 client ID |
CARD360_CLIENT_SECRET | Separate Card 360 client secret |
CARD360_RSA_PUBLIC_KEY | RSA public key used to encrypt Card 360 PIN payloads locally |
TRANSACTION_SEARCH_CLIENT_ID | Separate Transaction Search client ID |
TRANSACTION_SEARCH_CLIENT_SECRET | Separate Transaction Search client secret |
INTERSWITCH_AGENCY_MERCHANT_ID | Agency Banking merchant identifier |
INTERSWITCH_AGENCY_TERMINAL_ID | Agency Banking terminal identifier |
INTERSWITCH_LEGACY_AUTH_ENABLED | Enables legacy InterswitchAuth-backed flows where supported |
DEBUG | Enables debug logging. Avoid using this in production. |
You can select the API environment with INTERSWITCH_ENV:
INTERSWITCH_ENV=sandboxINTERSWITCH_ENV=productionSecurity note: Production mode uses real Interswitch production endpoints. If
INTERSWITCH_ENV=production, valid production credentials are configured,INTERSWITCH_READ_ONLY=false, and a write tool is called withconfirm: true, the server can make real production API calls.
For safer first-time setup, start in read-only mode:
INTERSWITCH_ENV=production \
INTERSWITCH_READ_ONLY=true \
INTERSWITCH_CLIENT_ID=your_production_client_id \
INTERSWITCH_CLIENT_SECRET=your_production_client_secret \
interswitch-mcp-server
When you are authorized and ready to allow live writes, set:
INTERSWITCH_READ_ONLY=false
The Interswitch MCP Server works with any MCP-compatible client. Below is the standard configuration schema used by most clients (Claude Desktop, ChatGPT Desktop, Cursor, Windsurf, VS Code, Claude Code, etc.).
For