meta-horizon-developer-mcp
Related Servers
Alternatives to meta-horizon-developer-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for organic Instagram analytics via the Meta Graph API, providing read-only tools for profiles, media, insights, audience, and optional publishing.GPL 3.0
- FlicenseNot gradedqualityBmaintenanceA read-only MCP server for querying Meta Ads accounts through Meta's Marketing API. It provides tools to retrieve ad accounts, campaigns, ad sets, ads, and performance insights.-
- AlicenseBqualityBmaintenanceRead-only MCP server for Meta Ads that lists and reads ad accounts, campaigns, ad sets, ads, ad images, creatives, and fetches insights at various levels.14MIT
- AlicenseCqualityDmaintenanceRead-only MCP server for Meta (Facebook) Graph API, enabling access to Marketing API, Pages, Instagram, and WhatsApp Business data through Claude Code and any MCP-compatible client.305 npm1MIT
- AlicenseAqualityCmaintenanceA read-only MCP server for AppDynamics that exposes 12 task-oriented tools to query applications, topology, metrics, snapshots, health rules, anomalies, events, alerting config, analytics events, and dependency maps via OAuth API-client credentials.121MIT
- AlicenseNot gradedqualityBmaintenanceA read-only MCP server exposing Google Analytics 4 and AdSense APIs (reports, metadata, admin reads) via Cloudflare Workers with OAuth authentication.MIT
TDQS
Scored across 4 tools
The status and latest_snapshot tools both report collection health, creating ambiguity about which to use. collect and read_operation are clearly distinct, but the overlap between the two status-related tools is confusing.
Tool names mix conventions: 'status' and 'latest_snapshot' are noun phrases, while 'collect' and 'read_operation' start with verbs. There is no consistent verb-first or predictable pattern, making it hard to guess the right tool.
With 4 tools, the server is tightly scoped, which is appropriate for a niche developer-oriented MCP. However, the duplicate health functionality between status and latest_snapshot suggests the count could be reduced without losing capability.
The core workflow of collecting snapshots and reading operations is covered, but there is no tool to list snapshots, retrieve a specific non-latest snapshot, or manage the snapshot lifecycle. The overlap between status and latest_snapshot also indicates the surface is not fully refined.