Interswitch MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Interswitch MCP Server Make a transfer of 5000 NGN to account 1234567890"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Interswitch MCP Server
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.
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.
Quick Start
Install and run via npm (recommended):
npx interswitch-mcp-serverOr install globally:
npm install -g interswitch-mcp-server
interswitch-mcp-serverOr for local development, clone and build:
git clone https://github.com/Dairus01/Interswitch-mcp-server.git
cd Interswitch-mcp-server
npm install
npm run buildThen configure your MCP client to use the server (see Client Integration).
Related MCP server: PayLink MCP Server
Requirements
Node.js v18+
npm or yarn
Interswitch API credentials for the domains you want to use
Required Interswitch merchant, payable, initiating entity, terminal, or domain-specific identifiers for your use case
Configuration Options
Environment Variable | Purpose |
| Core OAuth2 client ID for payments, transfers, VAS, cardless, lending, transfer service, and payouts |
| Core OAuth2 client secret |
| API environment: |
| Set |
| Compatibility setting. Tool confirmation is enforced by tool mode and risk. |
| Merchant code for payment operations that require it |
| Payable code for payment operations that require it |
| Initiating entity code for transfer operations |
| Terminal ID for operations that require terminal identification |
| Separate Card 360 client ID |
| Separate Card 360 client secret |
| RSA public key used to encrypt Card 360 PIN payloads locally |
| Separate Transaction Search client ID |
| Separate Transaction Search client secret |
| Agency Banking merchant identifier |
| Agency Banking terminal identifier |
| Enables legacy InterswitchAuth-backed flows where supported |
| Enables debug logging. Avoid using this in production. |
You can select the API environment with INTERSWITCH_ENV:
Sandbox (default):
INTERSWITCH_ENV=sandboxProduction:
INTERSWITCH_ENV=production
Security 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-serverWhen you are authorized and ready to allow live writes, set:
INTERSWITCH_READ_ONLY=falseClient Integration
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.).
Using npm (recommended)
For npm-installed server:
{
"mcpServers": {
"interswitch": {
"command": "npx",
"args": ["-y", "interswitch-mcp-server"],
"env": {
"INTERSWITCH_ENV": "sandbox",
"INTERSWITCH_READ_ONLY": "true",
"INTERSWITCH_CLIENT_ID": "your_client_id",
"INTERSWITCH_CLIENT_SECRET": "your_client_secret",
"INTERSWITCH_MERCHANT_CODE": "your_merchant_code",
"INTERSWITCH_PAYABLE_CODE": "your_payable_code",
"INTERSWITCH_INITIATING_ENTITY_CODE": "your_entity_code"
}
}
}
}For production, change the environment values intentionally:
{
"mcpServers": {
"interswitch": {
"command": "npx",
"args": ["-y", "interswitch-mcp-server"],
"env": {
"INTERSWITCH_ENV": "production",
"INTERSWITCH_READ_ONLY": "true",
"INTERSWITCH_CLIENT_ID": "your_production_client_id",
"INTERSWITCH_CLIENT_SECRET": "your_production_client_secret",
"INTERSWITCH_MERCHANT_CODE": "your_production_merchant_code",
"INTERSWITCH_PAYABLE_CODE": "your_production_payable_code",
"INTERSWITCH_INITIATING_ENTITY_CODE": "your_production_entity_code"
}
}
}
}Using a local build
If you've cloned and built the server locally:
{
"mcpServers": {
"interswitch": {
"command": "node",
"args": ["/path/to/Interswitch-mcp-server/dist/index.js"],
"env": {
"INTERSWITCH_ENV": "sandbox",
"INTERSWITCH_READ_ONLY": "true",
"INTERSWITCH_CLIENT_ID": "your_client_id",
"INTERSWITCH_CLIENT_SECRET": "your_client_secret"
}
}
}
}When settingcommand: "node", you should ensure you're using Node v18+. If you are using a package manager, you might need to get the path of your Node binary by running this command in your CLI:
Linux and MacOS
which nodeWindows
where nodeOnce you have the path, use it as the value of the MCP Server command in the JSON configuration. e.g., command: "path/to/installation/bin/node"
Where to add this configuration
Client | Config file location |
VS Code |
|
Claude Desktop |
|
ChatGPT Desktop | MCP settings in app preferences |
Cursor |
|
Windsurf | MCP configuration in settings |
Claude Code |
|
How It Works
The Interswitch MCP Server exposes Interswitch API domains to AI assistants through dedicated MCP tools. The server does not parse an OpenAPI file at runtime; instead, it provides curated, typed tools for the supported Interswitch domains.
Architecture Diagram
graph TD
subgraph MCP Server
A[Interswitch MCP Server]
B[Tool Registry]
C[Resource Registry]
end
subgraph Auth Layer
D[OAuth2 Passport Manager]
E[Card 360 Token Manager]
F[Transaction Search Manager]
G[Agency Banking Token Manager]
H[Legacy Auth Manager]
end
subgraph Core Services
I[Payments Service]
J[VAS Services]
K[Transfers Service]
L[Cardless Services]
M[Transaction Search Service]
N[Card 360 Service]
O[Lending Service]
P[Transfer Service]
Q[Payouts Service]
R[Agency Service]
S[Fintech Utilities]
end
subgraph Safety Layer
J1[Confirmation Gate]
J2[Read-Only Mode]
J3[Redaction System]
J4[Audit Logging]
end
A --> B
A --> C
A --> D
A --> E
A --> F
A --> G
A --> H
B --> I
B --> J
B --> K
B --> L
B --> M
B --> N
B --> O
B --> P
B --> Q
B --> R
B --> S
I --> J1
J --> J1
K --> J1
L --> J1
M --> J1
N --> J1
O --> J1
P --> J1
Q --> J1
R --> J1
S --> J1
J1 --> J2
J2 --> J3
J3 --> J4
J4 --> Z[External APIs]
style MCP Server fill:#f0f8ff,stroke:#333,stroke-width:2px
style Auth Layer fill:#e6f7e6,stroke:#333,stroke-width:1px
style Core Services fill:#f9f9f9,stroke:#666,stroke-width:1px
style Safety Layer fill:#fff0f0,stroke:#c33,stroke-width:1px
style Z fill:#d4d4d4,stroke:#999,stroke-dasharray: 5 5Each tool:
Validates its input with a strict schema
Applies confirmation and read-only safety gates
Selects the configured sandbox or production base URL
Uses the correct authentication system for the domain
Calls the Interswitch API only when the tool is invoked
Redacts sensitive fields from returned data
Returns a normalized MCP response
Authentication systems
Auth system | Used for |
OAuth2 Passport | Core payments, transfers, VAS, cardless, lending, transfer service, and payouts |
Card 360 token manager | Card 360 operations |
Transaction Search token manager | Transaction Search APIs |
Legacy InterswitchAuth | Legacy signed request flows where enabled |
Agency Banking token manager | Agency Banking SOAP/XML token flow |
Available Tools
Tool | Description |
| Initialize a payment request |
| Check transaction status |
| Fetch transaction by reference |
| Create a payment link |
| Initiate a refund; high-risk write |
| Check refund status |
| Pay a bill |
| List billers |
| List packages for a biller |
| List billers by category |
| Fetch biller details |
| Validate a biller customer |
| Pay a VAS bill |
| Recharge airtime |
| Request airtime ePINs |
| Send a single bank transfer; high-risk write |
| Send bulk transfers; high-risk write; max 100 transactions |
| Resolve bank account details |
| List supported bank codes |
| Initiate agency cashout; high-risk write |
| Create a cardless paycode |
| Create bulk paycodes; high-risk write; max 100 paycodes |
| Check paycode status |
| Deactivate a paycode |
| Search transactions by quick-search fields |
| Search by transaction reference |
| Search multiple transactions |
| Fetch detailed transaction information |
| Create a card; high-risk write |
| Retry card creation |
| Initiate card data preparation |
| Fetch a data-prep request |
| Fetch prepared cards |
| Start bulk card production; high-risk write |
| Reissue a card PIN; high-risk write |
| Change a card PIN; high-risk write |
| Retrieve PIN-related response where supported; high-risk read |
| Block a card; high-risk write |
| Unblock a card; high-risk write |
| Block a prepaid card; high-risk write |
| Unblock a prepaid card; high-risk write |
| Link a card to an account; high-risk write |
| Check prepaid card balance |
| Check debit card balance |
| Confirm prepaid sufficient balance |
| Confirm debit sufficient balance |
| Fetch cards by issuer |
| Fetch a single card by PAN with redaction |
| Fetch cards by account |
| Fetch customer card details |
| Fetch Card 360 request logs |
| Validate card data |
| Request a nano loan; high-risk write |
| Start salary lending flow; high-risk write |
| Start value financing flow; high-risk write |
| Fetch customer demographics |
| Fetch customer financial history |
| Fetch financial-history averages |
| Fetch customer financial habits |
| Run credit inquiry |
| Complete credit using OTP; high-risk write |
| Requery transfer status |
| List payout receiving institutions |
| List payout channels |
| Fetch/cache Agency Banking token |
| Validate debit payload structure |
| Validate reversal payload structure |
| Validate enquiry payload structure |
| Validate place-lien payload structure |
| Validate debit-lien payload structure |
| Compute MAC; high-risk because it accepts secrets |
| Build fintech response payload; high-risk when secrets are supplied |
Available Resources
Resource | URI | Description |
|
| Common Interswitch response-code reference |
|
| Safe runtime configuration summary; returns credential presence only, never secrets |
Example
When you ask your AI assistant something like "Use Interswitch to initialize a 5000 NGN payment for customer@example.com", here's what happens behind the scenes:
The assistant selects
isw_initialize_paymentIt passes explicit money input such as
amountNaira: 5000For write operations, it must include
confirm: trueThe server validates the request, converts the amount safely where required, authenticates with Interswitch, and calls the configured sandbox or production endpoint
You get a normalized response with redacted raw data
Prompt recommendation
To get the best results when using this MCP server, be specific in your prompts and always include "Interswitch" in your requests.
Good prompts:
"Initialize an Interswitch payment for 50000 NGN for user@example.com."
"Check the Interswitch transaction status for reference order-1001."
"Resolve Interswitch bank account 0123456789 with bank code 058."
"Send an Interswitch single transfer for 1000 NGN with confirm true."
"Read the Interswitch response code resource."
Less effective prompts:
"List my transactions" (unclear which service and reference/search criteria to use)
"Send money" (missing beneficiary, bank, amount, and confirmation details)
"Pay this bill" (missing biller, package, customer, and amount details)
Being explicit ensures the LLM narrows down to the right tool quickly and reduces ambiguity.
Production Safety
This server can route to production Interswitch endpoints when INTERSWITCH_ENV=production is set. Production readiness depends on correct credentials, Interswitch account permissions, and your organization's operational controls.
Safety behavior built into the server:
Write tools require
confirm: trueHigh-risk sensitive read tools require
confirm: trueINTERSWITCH_READ_ONLY=trueblocks all writes before any external API callLow-risk reads do not require confirmation
Raw responses are redacted before being returned
Tokens and secrets are never intentionally returned in tool output
Card PIN payloads are encrypted locally when the required RSA public key is configured
Production startup warnings are written to stderr instead of silently hiding risky configuration
Recommended production rollout:
Configure production credentials but keep
INTERSWITCH_READ_ONLY=trueVerify startup warnings and config summary
Test safe read-only tools first
Confirm domain credentials for the exact tools you intend to use
Switch
INTERSWITCH_READ_ONLY=falseonly when live writes are authorizedRequire human review before prompts that include
confirm: true
Development
Run locally (without building)
For local development and testing, you can run the TypeScript source directly:
npm run devRun with MCP Inspector
npm run inspectBuild
npm run buildRun tests
npm testType-check
npm run lintPreview npm package contents
npm pack --dry-runTroubleshooting
Issue | Solution |
Server exits silently at startup | Run it from a terminal and check stderr; verify Node v18+ and valid environment variables |
Production warning appears | Add the missing credential group, set |
Tools not appearing in client | Ensure the server is running and the client config path is correct |
Write tool blocked | Pass |
High-risk read blocked | Pass |
Payment tools fail | Configure |
Transfer tools fail | Configure |
Card 360 tools fail | Configure |
PIN operations fail | Configure a valid |
Transaction Search fails | Configure |
Agency tools fail | Configure |
Request timeouts | Check network connectivity to the configured Interswitch environment |
Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.
See CONTRIBUTING.md for more details.
License
MIT
Available Tools
74 toolsisw_agency_banking_cashoutC
Perform agency banking cashout. High-risk financial operation; requires confirm: true.
Inputs: agentCode (required), transactionRef (required), customerAccount (required), customerBankCode (required), +4 more.
isw_agency_cashout_xmlB
Submit raw Agency Banking cashout XML. High-risk financial operation; requires confirm: true.
Inputs: xml (required), confirm.
isw_agency_get_tokenA
Fetch an Agency Banking SOAP token using configured merchant and terminal IDs. Token is redacted in output.
Inputs: no named parameters.
isw_agency_requery_xmlC
Submit raw Agency Banking requery XML.
Inputs: xml (required).
isw_airtime_rechargeC
Top up a phone number through VAS airtime. Requires confirm: true.
Inputs: phoneNumber (required), transactionRef (required), extra, confirm, +3 more.
isw_block_cardC
Block a card immediately. Requires confirm: true.
Inputs: cardPan (required), extra, confirm, amountKobo, +2 more.
isw_block_prepaid_cardB
Block a prepaid card. Requires confirm: true.
Inputs: cardPan (required), extra, confirm, amountKobo, +2 more.
isw_bulk_card_productionC
Submit Card 360 bulk card production. Requires confirm: true.
Inputs: extra, cardPan, confirm, amountKobo, +2 more.
isw_bulk_transferA
Send money to multiple bank accounts. High-risk financial operation; requires confirm: true. Max 100 transactions.
Inputs: transactions (required), confirm, narration, initiatingEntityCode.
isw_change_card_pinB
Change a Card 360 card PIN. Plaintext PINs are encrypted locally and never sent. Requires confirm: true.
Inputs: pan (required), newPin (required), oldPin (required), cardPan (required), +2 more.
isw_check_debit_balanceD
Check debit card balance.
Inputs: cardPan (required), extra.
isw_check_prepaid_balanceC
Check prepaid card balance.
Inputs: cardPan (required), extra.
isw_complete_creditA
Complete bank credit using inquiryRef and OTP. High-risk financial operation; requires confirm: true.
Inputs: otp (required), inquiryRef (required), extra, confirm.
isw_confirm_debit_sufficientC
Confirm debit card sufficient balance. Requires confirm: true.
Inputs: cardPan (required), extra, confirm, amountKobo, +2 more.
isw_confirm_prepaid_sufficientC
Confirm prepaid card sufficient balance. Requires confirm: true.
Inputs: cardPan (required), extra, confirm, amountKobo, +2 more.
isw_create_bulk_paycodesA
Create multiple cardless withdrawal paycodes. High-risk batch operation; requires confirm: true. Max 100.
Inputs: paycodes (required), extra, confirm.
isw_create_cardC
Provision a new Verve card through Card 360. Requires confirm: true.
Inputs: extra, cardPan, confirm, amountKobo, +2 more.
isw_create_paycodeC
Create a cardless withdrawal paycode. Requires confirm: true.
Inputs: customerId (required), expiryDate (required), transactionRef (required), extra, +4 more.
isw_create_payment_linkA
Create a shareable payment link. Provide amountNaira or amountKobo explicitly; endpoint receives kobo. Requires confirm: true.
Inputs: expiryDate (required), extra, confirm, amountKobo, +3 more.
isw_credit_inquiryC
Run Transfer Service credit inquiry before bank credit.
Inputs: beneficiaryBankCode (required), beneficiaryAccountNumber (required), extra, amountKobo, +1 more.
isw_deactivate_paycodeA
Deactivate an unused paycode. Requires confirm: true.
Inputs: paycode (required), confirm.
isw_fetch_cards_by_accountC
Fetch cards linked to an account.
Inputs: accountNumber (required), extra.
isw_fetch_cards_by_issuerC
Fetch cards by issuer number.
Inputs: issuerNumber (required), page, extra, pageSize.
isw_fetch_customer_card_detailsC
Fetch customer card details by account.
Inputs: accountNumber (required), extra.
isw_fetch_data_prep_requestC
Fetch Card 360 data prep request by requestRef.
Inputs: requestRef (required), extra.
isw_fetch_prepared_cardsC
Fetch prepared cards for a data prep request.
Inputs: requestRef (required), page, extra, pageSize.
isw_fetch_request_logsC
Fetch Card 360 request logs.
Inputs: page, extra, toDate, fromDate, +1 more.
isw_fetch_single_card_by_panB
Fetch card details by PAN. Sensitive fields are redacted.
Inputs: cardPan (required), extra.
isw_fintech_build_responseC
Build a Fintech Card Processing response payload and optional MAC.
Inputs: requestId (required), responseCode (required), transactionReference (required), amount, +3 more.
isw_fintech_compute_macC
Compute Fintech Card Processing HMAC over ordered fields.
Inputs: fields (required), secret (required), payload (required), confirm, +1 more.
isw_fintech_validate_debit_lien_payloadC
Validate incoming Fintech Card Processing debit-lien payload shape.
Inputs: payload (required).
isw_fintech_validate_debit_payloadC
Validate incoming Fintech Card Processing debit payload shape.
Inputs: payload (required).
isw_fintech_validate_enquiry_payloadC
Validate incoming Fintech Card Processing enquiry payload shape.
Inputs: payload (required).
isw_fintech_validate_place_lien_payloadC
Validate incoming Fintech Card Processing place-lien payload shape.
Inputs: payload (required).
isw_fintech_validate_reversal_payloadC
Validate incoming Fintech Card Processing reversal payload shape.
Inputs: payload (required).
isw_get_airtime_epinsC
Purchase airtime e-pins. Requires confirm: true.
Inputs: customerId (required), transactionRef (required), extra, confirm, +3 more.
isw_get_bank_codesB
List supported bank codes for transfers.
Inputs: no named parameters.
isw_get_biller_detailsB
Get VAS biller details by billerId.
Inputs: billerId (required).
isw_get_biller_packagesC
List packages for a biller.
Inputs: billerId (required).
isw_get_billersC
List Quickteller billers, optionally filtered by categoryId.
Inputs: categoryId.
isw_get_billers_by_categoryC
List VAS billers by category.
Inputs: categoryId.
isw_get_customer_demographicsC
Get customer demographic profile.
Inputs: customerId (required), extra.
isw_get_financial_habitsD
Get customer financial habits.
Inputs: customerId (required), extra.
isw_get_financial_historyC
Get customer financial history.
Inputs: customerId (required), extra, toDate, fromDate.
isw_get_financial_history_averageC
Get customer average financial history.
Inputs: customerId (required), extra.
isw_get_paycode_statusC
Get status of a generated paycode.
Inputs: paycode (required).
isw_get_payout_channelsB
List available payout channels.
Inputs: no named parameters.
isw_get_pinC
Get a card PIN. Sensitive operation; requires confirm: true and redacts sensitive fields.
Inputs: cardPan (required), extra, confirm.
isw_get_receiving_institutionsC
List payout receiving institutions.
Inputs: code, name, type.
isw_get_refund_statusC
Get refund status by refundRef.
Inputs: refundRef (required).
isw_get_transaction_by_referenceC
Get Quickteller transaction by transactionRef query.
Inputs: transactionRef (required).
isw_get_transaction_detailsB
Get Transaction Search details by transactionId.
Inputs: transactionId (required).
isw_get_transaction_statusC
Get Quickteller transaction status by transactionRef.
Inputs: transactionRef (required).
isw_initialize_paymentC
Initialize a Quickteller payment. Provide amountNaira or amountKobo explicitly; endpoint receives kobo. Requires confirm: true.
Inputs: customerId (required), redirectUrl (required), transactionRef (required), extra, +6 more.
isw_initiate_card_data_prepC
Initiate Card 360 card data prep. Requires confirm: true.
Inputs: extra, cardPan, confirm, amountKobo, +2 more.
isw_initiate_refundA
Initiate a refund for a settled transaction. High-risk write operation; requires confirm: true.
Inputs: transactionRef (required), extra, reason, confirm, +4 more.
isw_link_card_to_accountB
Link a Card 360 card to an account. Requires confirm: true.
Inputs: cardPan (required), extra, confirm, amountKobo, +2 more.
isw_pay_billB
Pay a bill through the payment route. Provide amountNaira or amountKobo explicitly; endpoint receives kobo. Requires confirm: true.
Inputs: customerId (required), transactionRef (required), extra, confirm, +4 more.
isw_pay_vas_billB
Pay a VAS bill. Provide amountNaira or amountKobo explicitly. Requires confirm: true.
Inputs: customerId (required), transactionRef (required), extra, confirm, +3 more.
isw_reissue_card_pinB
Reissue a Card 360 card PIN. The plaintext pin is encrypted locally and never sent. Requires confirm: true.
Inputs: pan (required), pin (required), cardPan (required), extra, +1 more.
isw_requery_transferC
Requery Transfer Service transaction status.
Inputs: transactionRef (required).
isw_request_nano_loanB
Request a nano loan. High-risk operation creating debt; requires confirm: true.
Inputs: customerId (required), extra, tenor, confirm, +4 more.
isw_resolve_bank_accountC
Resolve account name before transfer.
Inputs: beneficiaryBankCode (required), beneficiaryAccountNumber (required).
isw_retry_card_creationC
Retry a Card 360 card creation request. Requires confirm: true.
Inputs: extra, cardPan, confirm, amountKobo, +2 more.
isw_salary_lendingB
Request a salary loan. High-risk operation creating debt; requires confirm: true.
Inputs: customerId (required), extra, tenor, confirm, +3 more.
isw_single_transferB
Send money to a bank account. High-risk financial operation; requires confirm: true. Provide amountNaira or amountKobo explicitly.
Inputs: senderName (required), transactionRef (required), beneficiaryBankCode (required), beneficiaryAccountName (required), +6 more.
isw_transaction_search_bulk_searchC
Search multiple transaction references at once.
Inputs: transactions (required), extra.
isw_transaction_search_quick_searchC
Search transactions by amountKobo, terminal, and date range. Dates use YYYY-MM-DD HH:mm:ss.
Inputs: toDate (required), fromDate (required), extra, amountKobo, +1 more.
isw_transaction_search_reference_searchC
Search transactions by transaction reference and date range.
Inputs: toDate (required), fromDate (required), transactionRef (required), extra.
isw_unblock_cardC
Unblock a card. Requires confirm: true.
Inputs: cardPan (required), extra, confirm, amountKobo, +2 more.
isw_unblock_prepaid_cardC
Unblock a prepaid card. Requires confirm: true.
Inputs: cardPan (required), extra, confirm, amountKobo, +2 more.
isw_validate_cardA
Validate card CVV and expiry. Requires confirm: true.
Inputs: cardPan (required), extra, confirm, amountKobo, +2 more.
isw_validate_customerC
Validate a customer account, meter, or phone number for a biller.
Inputs: billerId (required), customerId (required), extra.
isw_value_financingB
Request value financing. High-risk operation creating debt; requires confirm: true.
Inputs: customerId (required), extra, confirm, amountKobo, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 74 tools
Many tools have overlapping purposes (e.g., multiple transaction status/query tools, similar card operations). The high number of tools increases the risk of an agent selecting the wrong one, though descriptions do help distinguish them.
All tools follow a consistent 'isw_verb_noun' snake_case pattern. Verbs are descriptive and uniformly formatted, making the naming predictable and easy to parse.
74 tools is far above the typical well-scoped range of 3-15. While the server covers a broad financial domain, the sheer number feels overwhelming and likely to confuse agents, suggesting insufficient scoping.
The tool set covers an impressively wide range of financial operations: payments, cards, bills, loans, transfers, agency banking, and more. Minor gaps exist (e.g., dispute management), but core workflows are well-covered.
Maintenance
Related MCP Connectors
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
One MCP server for the services your AI needs: memory, files, Microsoft 365, kanban and more.
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables AI assistants to interact with Flutterwave payment services, providing tools for transaction management, payment link generation, and automated customer support.82 npm4TypeScriptMIT

PayLink MCP Serverofficial
FlicenseNot gradedqualityDmaintenanceOpen-source MCP server that streamlines payment integration for AI agents and financial apps in Africa, providing unified tools for providers like M-Pesa.1-- AlicenseAqualityCmaintenanceA unified MCP server for West African payment providers, enabling AI agents and REST clients to initiate payments, payouts, refunds, and manage webhooks across 10 providers with a single API.822 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server wrapping JazzCash payment provider APIs. Enables interaction with JazzCash services through natural language.MIT