sprout-mcp
Related Servers
Alternatives to sprout-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceAn MCP server that integrates the Sprout Social Public API with Claude and other MCP clients. It allows users to manage social profiles, track analytics for posts and profiles, and schedule social media content.11-
- 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 gradedqualityCmaintenanceMCP server for Brandwatch's Consumer Research, Data Upload, and Analysis APIs, exposing 55 tools for social listening, mentions, queries, alerts, and data uploads.-
- AlicenseNot gradedqualityBmaintenancePublish, schedule and read analytics across every major social network from one MCP server. 15+ tools covering publishing, scheduling, validation, media upload and normalised cross-platform analytics.2MIT
- FlicenseCqualityBmaintenanceRead-only MCP server that collects Analytics data from the Meta Horizon developer dashboard by intercepting GraphQL queries. It provides tools for status checks, snapshot collection, and reading allowed query results.4-
- AlicenseAqualityCmaintenanceMCP server for the Meta Threads API, enabling profile retrieval, post creation and deletion, insights, and passthrough to other Threads endpoints with optional read-only and no-destructive modes.69 npmMIT
TDQS
Scored across 5 tools
Each tool serves a distinct purpose: customer ID discovery, profile listing, metric metadata, profile analytics, and post analytics. There is no functional overlap, and descriptions clearly differentiate them.
Tools follow a 'verb_noun' pattern, but verbs are inconsistent: 'get_customer_id' returns a list (could be 'list'), while 'list_profiles' and 'list_metrics' use 'list'. However, the pattern is otherwise consistent and readable.
Five tools cover the essential operations for a social media analytics server: account discovery, profile enumeration, metric exploration, and two data retrieval endpoints. This is well-scoped and not excessive.
The set covers core analytics workflows (profile metrics, post performance) and necessary metadata (customer IDs, profiles, metrics). Minor gaps exist, such as missing a tool to fetch a specific post by ID or account-level aggregation, but these are non-critical for the intended read-only analytics use case.