GHB MCP
Related Servers
Alternatives to GHB MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP clients to query Google Analytics 4 reporting and configuration data through 27 read-only tools, including pivots, funnels, realtime reports, Admin API inspection, and diagnostics, with identifiers redacted by default.27148 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables querying Google Analytics 4 data through MCP tools for running reports, listing properties, getting real-time metrics, and exploring metadata.149 npmMIT
- AlicenseBqualityBmaintenanceEnables read-only access to Google Analytics 4 properties through MCP tools for listing properties, inspecting metadata, checking metric compatibility, and running core or realtime reports, summaries, traffic-source, page, and event queries.18MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients like Claude and Cursor to run read-only Google Analytics 4 queries — reports, funnels, realtime data, property and stream setup, custom dimensions, plus tracking-health checks for duplicate transactions and traffic attribution — with a one-time browser Google sign-in and no Google Cloud project required. GA4 data flows directly from the local machine to Google, and only read-only analytics access is requested.Apache 2.0
- AlicenseBqualityBmaintenanceEnables read-only access to Google Marketing Platform data across GMP Admin, Display & Video 360, Campaign Manager 360, and Search Ads 360 through OAuth-authenticated MCP tools for discovering accounts, campaigns, reports, and performance metrics.33495 PyPIMIT
- AlicenseAqualityAmaintenanceEnables MCP clients to inspect Google Play releases, reviews, Android vitals, and scoped bulk reports, and to prepare explicitly authorized changes using locally supplied service-account credentials. Reads are default, while optional writes and sensitive reads require explicit configuration and single-use execution.21331 PyPIAGPL 3.0
TDQS
Scored across 5 tools
Each tool maps to a distinct platform/action: local authorization info (connection_info), GTM reads, GA4 admin reads, GA4 reporting, and Ads queries. Only connection_info could overlap slightly with gtm_read in that both surface authorized resources, but the scopes are clearly separate.
Four of five tools follow a clean platform_action pattern (gtm_read, ga4_admin_read, ga4_report, google_ads_search) with clear snake_case naming. connection_info breaks the platform-prefix convention but remains readable and unambiguous.
Five tools is a reasonable, tight scope for a read-only tri-platform MCP. It is slightly thin given three distinct products are covered, but no tool feels redundant or filler.
The surface is entirely read-only, so no create/update/publish operations exist for GTM tags, GA4 config, or Ads entities, and GTM reporting/version publishing is absent. If read-only is intentional the read coverage is decent, but agents wanting to modify anything hit a dead end.