TropiPay 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., "@TropiPay MCP Server show my account balance"
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.
TropiPay MCP Server
A Model Context Protocol (MCP) server for interacting with TropiPay's payment platform. This server provides a standardized interface for AI assistants in various development environments to perform TropiPay operations through tools and resources.
β¨ Features
Authentication: Handles OAuth 2.0 client credentials flow with TropiPay
Modular Architecture: Clean separation of concerns with TypeScript
TropiPay API Integration: Comprehensive wrapper around TropiPay's functionality
Tool-Based Interface: Easy integration with AI assistants
Environment Support: Configure for sandbox or production environments
Editor Compatibility: Works with VS Code, Cursor, Windsurf, and other MCP-compatible editors
Related MCP server: @striderlabs/mcp-cashapp
π οΈ Available Tools
Account Management
get_default_account_balance: Retrieve current default account balanceget_profile_data: Get user profile informationget_accounts_list: List all TropiPay accounts
Transactions
get_movement_list: View transaction history with paginationlist_deposit_accounts: List deposit accounts/beneficiaries (bank accounts, crypto wallets, etc.)list_paymentcards: Get list of payment cards (payment links) created by the user
Beneficiary Management
create_internal_beneficiary: Create a new internal TropiPay beneficiaryRequired Fields: alias, searchValue (email)
create_external_beneficiary: Create a new external bank account beneficiaryRequired Fields: firstName, lastName, accountNumber, currency, countryDestinationId/countryISO
create_crypto_beneficiary: Create a new crypto wallet beneficiaryRequired Fields: firstName, lastName, accountNumber (wallet address), currency, network
Payment Links
create_paymentcard: Create payment links (called payment cards in TropiPay)Required Fields: amount, currency, concept, description
Optional Fields: reference, favorite, singleUse, expirationDays, reasonId, lang, urlSuccess, urlFailed, urlNotification, serviceDate, accountId
System
test_connection: Verify API connectivity and authentication
π Available Resources
The TropiPay MCP Server provides the following reference resources:
tropipay://config: Current TropiPay API configuration and environment settingstropipay://status: TropiPay API connection status and health checktropipay://movement-types: Complete reference of TropiPay movementType IDs and their meaningstropipay://movement-states: Complete reference of TropiPay movement state codes and their meaningstropipay://account-states: Complete reference of TropiPay account state codes and their meanings
π Getting Started
Prerequisites
Node.js 20+
npm or yarn
TropiPay API credentials (Client ID and Client Secret)
Installation
Clone the repository:
git clone https://github.com/yosle/tropipay-mcp-server.git cd tropipay-mcp-server npm installInstall dependencies:
npm install
MCP Client Configuration
This MCP server can be used with any MCP-compatible client such as Claude Desktop, Windsurf, Cline, or other AI assistants that support the Model Context Protocol.
Configuration File Locations
Locate your client's MCP configuration file:
Claude Desktop:
Windows:
%APPDATA%\Claude\claude_desktop_config.jsonMacOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonLinux:
~/.config/Claude/claude_desktop_config.json
Windsurf:
Windows:
%USERPROFILE%\.codeium\windsurf\mcp_config.jsonMacOS:
~/.codeium/windsurf/mcp_config.jsonLinux:
~/.codeium/windsurf/mcp_config.json
Cline: Refer to the Cline documentation for configuration details
Installation Methods
Option 1: Using npx (Recommended)
You can run the server directly with npx:
{
"mcpServers": {
"tropipay": {
"command": "npx",
"args": ["-y", "tropipay-mcp-server"],
"env": {
"TROPIPAY_CLIENT_ID": "your_client_id",
"TROPIPAY_CLIENT_SECRET": "your_client_secret",
"TROPIPAY_BASE_URL": "https://sandbox.tropipay.me"
}
}
}
}Option 2: Local Development/Installation
For local development or if you've cloned the repository:
{
"mcpServers": {
"Tropipay MCP Server": {
"command": "node",
"args": [
"D:\\proyectos\\tropipay-mcp-server\\tropipay-mcp-server\\build\\index.js"
],
"env": {
"TROPIPAY_CLIENT_ID": "your_client_id",
"TROPIPAY_CLIENT_SECRET": "your_client_secret",
"TROPIPAY_BASE_URL": "https://sandbox.tropipay.me"
}
}
}
}Environment Variables
Configure the following environment variables in your MCP client configuration:
Variable | Required | Description | Default |
| β Yes | Your TropiPay API client ID | - |
| β Yes | Your TropiPay API client secret | - |
| β No | Environment: |
|
| β No | Custom API base URL (overrides environment) | Based on environment |
Base URL Options
Sandbox:
https://sandbox.tropipay.me(default)Production:
https://www.tropipay.comLocal Development:
http://localhost:3001(or your custom endpoint)
Important Notes:
For Windows paths, use double backslashes:
"D:\\folder\\tropipay-mcp-server\\build\\index.js"For Linux/Mac paths, use forward slashes:
"/home/user/tropipay-mcp-server/build/index.js"The
-yflag in npx automatically confirms package installationMake sure to run
npm run buildbefore using the local installation method
ποΈ Project Structure
src/
βββ client/ # TropiPay client initialization and management
βββ config/ # Configuration management
βββ resources/ # MCP resource handlers
βββ tools/ # Tool definitions and handlers
β βββ definitions.ts
β βββ handlers.ts
βββ types/ # TypeScript type definitions
βββ index.ts # Main server entry pointπ Usage Examples
Get a list of my beneficiaries Getting Account Balance
Get the balance in all my Tropipay accounts π License
This project is licensed under the MIT License - see the LICENSE file for details.
π€ Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
π§ Contact
For questions or support, please open an issue on GitHub.
Available Tools
11 toolscreate_crypto_beneficiaryA
Create a new crypto wallet beneficiary using TropiPay API.
Required: firstName, lastName, accountNumber (wallet address), currency, network
Example:
{
"firstName": "John",
"lastName": "Doe",
"accountNumber": "5Hw3k2c4Z5oLWxfTMT8nBnhqWF4SWcAFQLnJTJPzNe2y",
"currency": "USDC",
"network": "SOLANA"
}Inputs: network (required), currency (required), lastName (required), firstName (required), +7 more.
create_external_beneficiaryA
Create a new external bank account beneficiary using TropiPay API.
Required: firstName, lastName, accountNumber, currency, countryDestinationId/countryISO
Example:
{
"firstName": "Panfilo",
"lastName": "Epifanio",
"accountNumber": "ES91 2100 0418 4502 0005 1332",
"currency": "EUR",
"countryDestinationId": 1,
"swift": "CAIXESBBXXX",
"address": "Gran Via de les Corts Catalanes, 765",
"city": "Barcelona",
"province": "Barcelona",
"postalCode": "08013"
}Inputs: currency (required), lastName (required), firstName (required), accountNumber (required), +22 more.
create_internal_beneficiaryA
Create a new internal TropiPay beneficiary using TropiPay API.
Required: alias, searchValue (email)
Example:
{
"alias": "MR Buchman",
"searchValue": "wick@gmail.com",
"searchBy": 1
}Inputs: alias (required), searchValue (required), type, email, +11 more.
create_paymentcardA
Create a new payment card (payment link) using TropiPay API. IMPORTANT:- NEVER create payment cards without first asking the user for required information- ALWAYS collect: amount, currency, concept, and description before proceeding- DO NOT generate or assume default values for required fields- Ask clarifying questions if any information is missing or unclearRequired Information to Collect from User:
amount,currency,concept,descriptionAny specific requirements (expiration, single use, etc.)
π Optional Fields:
referencefavoritesingleUseexpirationDaysreasonIdlangurlSuccessurlFailedurlNotificationserviceDateaccountIdπ Process Flow:
First ask user for: amount, currency, concept, and description
Optionally ask about: expiration days, single use, reference, redirect URLs
Then create the payment card with provided information
Return the payment card information to the user
Inputs: amount (required), concept (required), currency (required), lang, +11 more.
get_accounts_listB
Get list of TropiPay accounts associated with the user
Inputs: no named parameters.
get_default_account_balanceA
Get the current selected as default account balance from TropiPay
Inputs: no named parameters.
get_movement_listA
Get list of account movements/transactions (requires ALLOW_GET_MOVEMENT_LIST scope).
π Response Structure:
count: Total number of movements availablerows: Array of movement objects with the following key fields:id: Unique movement identifieramount: Transaction amount (+ for credits, - for debits)currency: Currency code (USD, EUR, etc.)movementTypeId: Type classification (1=Transfer, 2=Card Credit, 3=Refund, 4=Card Refund, 5=Top Up, 6=Exchange, 7=ATM, 8=Fee, 9=Adjustment)state: Transaction status (2=Charged, 3=Paid, 4=Error, 5=Pending In, 6=Cancelled)bankOrderCode: Transaction identifier (TX prefix for regular, DEV for refunds)balanceBefore/balanceAfter: Account balance before/after transactionreference: User-defined referenceconceptTransfer: Transaction descriptioncompletedAt/createdAt: Transaction timestampsfee: Transaction fee (if applicable)accountId: Id of the account that this movement belongsoriginalCurrencyAmount: Amount in original currencydestinationAmount: Amount in destination currencydestinationCurrency: Destination currency codeconversionRate: Applied rate for this movementpaymentcard: uuid of asociated paymentcard to this movement or null otherwise π‘ Tip: Use the 'tropipay_movements_schema' prompt for detailed field explanations.
Inputs: limit, offset.
get_profile_dataA
Get user profile information from TropiPay account
Inputs: no named parameters.
list_deposit_accountsA
Get list of deposit accounts (a.k.a beneficiaries).
π‘ Tip: deposit accounts are also refered as beneficiaries can be internal (other Tropipay accounts) or external (bank accounts, external cripto wallets)
π Response Structure:
`Array of depositaccounts objects:
id: Unique deposit account identifieraccountNumber: IBAN for external bank accounts, wallet address for external crypto accounts, email of user for internal beneficiaries)alias: if not null, User-friendly account name/alias set by usercurrency: Account currencytype: Account type (9=Tropipay account, 12=Crypto wallet, 7=Other, 8=BANDEC card, 4= BPA card, 3=BANMET card)state: Account status (0=Active, 1=Inactive, 2=Deleted)countrydestination: Object with info about the country where the account is registered,slug, name etcuserRelationTypeId: Type of relation with the user (0=myself, 3=commercial)createdAt/updatedAt: Account creation and modification timestampsfirstName: First name of the beneficiary with the accountlastName: Last name of the beneficiary with the account
Inputs: no named parameters.
list_paymentcardsA
Get list of paymentcards (paylinks) created by the user
Inputs: no named parameters.
test_connectionA
Test the connection to TropiPay API and verify authentication by retrieving the selected default account balance
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 11 tools
Most tools target distinct resources (balance, profile, accounts, movements, payment cards, beneficiaries), but test_connection overlaps with get_default_account_balance by also retrieving the balance, and the three create_*_beneficiary tools are very similar in function though differentiated by beneficiary type. Agents may struggle to pick between these without careful reading.
Tools generally follow a verb_noun pattern in snake_case (get_profile_data, list_deposit_accounts), but there is inconsistency with compound nouns: 'list_paymentcards' and 'create_paymentcard' lack the expected underscore between 'payment' and 'card', unlike 'get_default_account_balance' and 'list_deposit_accounts'. This is a minor deviation from an otherwise predictable pattern.
With 11 tools, the set is well-sized for a payment server covering balance, profile, accounts, movements, payment cards, and beneficiaries. Each tool addresses a distinct need without excessive granularity or bloat.
The read side is solid (profile, balance, accounts, movements, cards, beneficiaries) and creation is supported for payment cards and all beneficiary types. However, there are no update/delete operations for cards or beneficiaries, nor any transfer/payment initiation tools, leaving clear gaps in the expected lifecycle for a payment platform.
Maintenance
Related MCP Connectors
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.
One MCP server for the services your AI needs: memory, files, Microsoft 365, kanban and more.
MCP server unifying ERPs, CRMs, APIs and knowledge base for Claude, ChatGPT and Gemini.
MCP server enabling AI agents to manage Bitrix24 features via standardized protocol
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
- AlicenseAqualityDmaintenanceAn MCP server that enables AI assistants to automate Cash App payments, balance checks, and transaction management via browser automation.13MIT
- AlicenseNot gradedqualityCmaintenanceA universal MCP server that provides a single merchant interface for AI agents across multiple protocols, enabling catalog browsing, checkout creation, and transaction status queries.MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that bridges AI agents with external tools, APIs, databases, and services, enabling standardized tool execution and resource access.MIT