Hyros MCP
Related Servers
Alternatives to Hyros MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceBridges Hyros attribution data to Claude via MCP tools, enabling real ROAS/revenue reconciliation by campaign and ad account.49 npmMIT
- AlicenseNot gradedqualityCmaintenanceConnect AI assistants to live Meta Ads, GA4, and Google Search Console data. 100% local, credentials machine-locked and encrypted. Supports Claude Desktop, Cursor, Windsurf, Cline, and more.1MIT
- AlicenseNot gradedqualityCmaintenanceAn implementation of Model Context Protocol (MCP) that allows users to interact with TripleWhale's e-commerce analytics platform using natural language queries through Claude Desktop.106 npm7MIT
- AlicenseBqualityFmaintenanceConnects AI assistants like Claude to Sealmetrics analytics data, enabling natural language queries for traffic analysis, conversions, marketing performance, ROAS tracking, and funnel analysis.8MIT

Adsroid MCPofficial
FlicenseNot gradedqualityCmaintenanceAdsroid MCP connects Claude, ChatGPT, Cursor, or any MCP-compatible client directly to your advertising and marketing accounts, Google Ads, Meta Ads, Microsoft Ads, TikTok Ads, LinkedIn Ads, Google Search Console, Google Analytics 4, and HubSpot, through a single endpoint.-- AlicenseAqualityBmaintenanceConnects Google Analytics 4 data to Claude, Cursor and other MCP clients, enabling natural language queries of website traffic, user behavior, and analytics data with access to 200+ GA4 dimensions and metrics.101,020 PyPI241MIT
TDQS
Scored across 53 tools
Most tools have distinct resource-action purposes, but there are several overlap issues. hyros_get_tags and hyros_get_tags_count serve the same purpose (one deprecated), and multiple reporting tools (hyros_get_attribution_report, hyros_best_performers, hyros_compare_periods) have similar parameters and outputs, making it easy for an agent to misselect.
The majority of tools follow a consistent hyros_verb_noun pattern (e.g., hyros_get_leads, hyros_create_order, hyros_delete_sale). However, a few tools break this pattern with noun-phrase names like hyros_daily_summary, hyros_best_performers, and hyros_compare_periods, which is a minor deviation.
With 53 tools, the server is well beyond the 'heavy' threshold and feels bloated. While the domain is complex, several tools are redundant or could be consolidated (e.g., hyros_get_tags vs hyros_get_tags_count), and the sheer number will likely overwhelm agents.
The tool surface is quite comprehensive, covering CRUD operations for leads, sales, calls, subscriptions, carts, products, sources, custom costs, and webhooks, plus a range of attribution and analytics reports. Minor gaps exist, such as no update/delete for clicks and no direct delete for carts, but core workflows are well supported.