Metrx MCP Server
Related Servers
Alternatives to Metrx MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server that routes natural language queries to backend analytics tools (Sales, Finance, Customer, Service) using Google Gemini's function calling.-
- AlicenseNot gradedqualityDmaintenanceMCP server for Stessa rental-property accounting platform, enabling AI agents to query properties, portfolios, banking, documents, and tenancies via natural language.MIT
- AlicenseNot gradedqualityDmaintenanceAn enterprise-grade MCP server for interacting with Odoo ERP through AI assistants, enabling guided workflows, native BI, and deep introspection.10MIT

@intempt/mcp-serverofficial
FlicenseNot gradedqualityCmaintenanceMCP server for Intempt GrowthOS — AI content generation, brand management, knowledge base, and user/account lookup through natural language.-- AlicenseNot gradedqualityDmaintenanceMCP server for integrating manufacturing systems (MES/ERP/quality/maintenance) with LLM agents, enabling event ingestion, incident triage, approval workflows, and RAG-based knowledge retrieval.MIT
- AlicenseAqualityDmaintenanceAn MCP server that enables AI assistants to query databases, execute SQL, and manage Metabase resources like dashboards, cards, and collections through natural language.22MIT
TDQS
Scored across 41 tools
Many tools have distinct purposes, and descriptions often explicitly cross-reference alternatives. However, several adjacent read surfaces overlap in practice: ROI/audit/attribution/upgrade/dashboard tools, health/rankings/scorecard tools, and recommendations/leak-scan tools. With 41 tools, an agent can still struggle to choose correctly without parsing long descriptions.
The set uses a consistent metrx_ prefix and mostly follows a verb_noun pattern such as get_task_roi, set_budget, create_model_experiment, and acknowledge_alert. There are minor deviations like metrx_kb_prior_lookup and some noun-oriented names like get_health_scores/get_rankings, but they remain readable and predictable overall.
The server exposes 41 tools, which is well above the typical well-scoped range and creates a heavy selection burden. The domain is broad, but many tools are narrow read surfaces, so the set feels over-expanded rather than tightly scoped.
Coverage is broad across agent economics, ROI, budgets, contracts, experiments, verification, monitoring, and reporting. Minor lifecycle gaps exist, such as no clear agent create/update/delete, no budget deletion, no experiment traffic-start operation, and alerts only acknowledge rather than resolve, but core workflows are substantially covered.