PEX MCP Server
Related Servers
Alternatives to PEX MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityNot gradedmaintenanceEnables AI agents to interact with the Brex financial platform, allowing access to account information, transactions, expenses, receipts, budgets, and spend limits through the Brex API.92 npm-
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with the WYGIWYH expense tracking API through 75 dynamically generated MCP tools. Supports comprehensive financial operations including transaction management, account handling, recurring expenses, and investment tracking.7-
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to interact with Conta Azul Financial APIs to manage accounts, balances, and transactions through natural language. It features specialized tools for tracking cash flow, processing payables and receivables, and generating comprehensive financial reports.-
- FlicenseAqualityBmaintenanceEnables AI agents to use corporate card and expense functions, including balance checks, transaction listing, receipt compliance, expense reporting, and approval workflows, by calling existing REST APIs through a governed gateway with identity, policy, and audit controls.8-
- AlicenseAqualityDmaintenanceEnables interaction with Brex financial data including expenses, budgets, transactions, and accounts through read-only API access with support for pagination, filtering, and receipt management.213 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with the TelecomsXChange wholesale telecom API for voice termination, SMS, DID management, eSIM, and account operations through 55 tools and 7 guided workflows using natural language.2MIT
TDQS
Scored across 72 tools
The tools are mostly distinct, but there is notable overlap in areas like cardholder transactions (e.g., pex_get_cardholder_transactions, pex_get_all_cardholder_transactions, pex_get_cardholder_purchases) and business transactions (e.g., pex_get_business_transactions, pex_get_network_transactions, pex_get_transaction_details), which could cause confusion. Descriptions help differentiate some, but the sheer number of similar tools increases ambiguity.
Tool names follow a highly consistent verb_noun pattern, all starting with 'pex_get_' or 'pex_list_' and using snake_case throughout. This predictability makes it easy for agents to parse and understand the naming conventions across all 72 tools.
With 72 tools, the count is excessive for typical MCP server purposes, making it heavy and potentially overwhelming for agents. While the domain (financial/card management) is broad, the tool set could likely be consolidated or scoped more narrowly to improve usability.
The tool set provides extensive coverage for financial and card management operations, including account details, transactions, rules, billing, and administrative functions. Minor gaps might exist, such as update or delete operations for some resources, but agents can likely work around these given the comprehensive read-focused surface.