TropiPay MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TROPIPAY_BASE_URL | No | Custom API base URL (overrides environment) | |
| TROPIPAY_CLIENT_ID | Yes | Your TropiPay API client ID | |
| TROPIPAY_ENVIRONMENT | No | Environment: sandbox or production | sandbox |
| TROPIPAY_CLIENT_SECRET | Yes | Your TropiPay API client secret |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_default_account_balanceA | Get the current selected as default account balance from TropiPay |
| get_profile_dataA | Get user profile information from TropiPay account |
| get_movement_listA | Get list of account movements/transactions (requires ALLOW_GET_MOVEMENT_LIST scope). š Response Structure:
|
| get_accounts_listB | Get list of TropiPay accounts associated with the user |
| 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:
|
| 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:
š Optional Fields:
|
| test_connectionA | Test the connection to TropiPay API and verify authentication by retrieving the selected default account balance |
| list_paymentcardsA | Get list of paymentcards (paylinks) created by the user |
| create_external_beneficiaryA | Create a new external bank account beneficiary using TropiPay API. Required: firstName, lastName, accountNumber, currency, countryDestinationId/countryISO Example: |
| create_internal_beneficiaryA | Create a new internal TropiPay beneficiary using TropiPay API. Required: alias, searchValue (email) Example: |
| create_crypto_beneficiaryA | Create a new crypto wallet beneficiary using TropiPay API. Required: firstName, lastName, accountNumber (wallet address), currency, network Example: |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| tropipay_movements_schema | Get comprehensive schema documentation for TropiPay movements/transactions data structure |
| tropipay_accounts_schema | Get comprehensive schema documentation for TropiPay accounts data structure |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| TropiPay Configuration | Current TropiPay API configuration and environment settings |
| API Status | TropiPay API connection status and health check |
| Movement Types Reference | Complete reference of TropiPay movementType IDs and their meanings |
| Movement States Reference | Complete reference of TropiPay movement state codes and their meanings |
| Account States Reference | Complete reference of TropiPay account state codes and their meanings |
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.