Skip to main content
Glama
jmeserve

sprout-mcp

by jmeserve
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to sprout-mcp

No user-submitted related servers found.

    Related Servers

    • social0-mcp

      Abhishek-B-R
      A
      license
      A
      quality
      B
      maintenance
      MCP server to manage social media accounts from AI assistants, enabling post creation, scheduling, publishing, and media uploads across multiple platforms.
      13
      41 npm
      1
      MIT

    • so-easy-mcp

      Pantalones411
      A
      license
      Not graded
      quality
      C
      maintenance
      A full social media management MCP server enabling post, read, schedule, and analyze across Facebook, Instagram, LinkedIn, X/Twitter, Pinterest, and YouTube from any MCP-compatible AI client.
      MIT

    • sprout-mcp

      shauryasa0
      F
      license
      A
      quality
      C
      maintenance
      Read-only MCP server for the Sprout Social public API, exposing profile and post analytics as tools with raw JSON passthrough.
      5
      -
    • socialchamp-mcp by SocialChamp

      socialchamp-mcpofficial

      SocialChamp
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that exposes the full Social Champ tool catalog for scheduling and managing posts, channels, workspaces, labels, queues, and more through AI clients like Claude Desktop and Cursor.
      2
      MIT

    • postforme-mcp-pro

      helbertparanhos
      A
      license
      A
      quality
      C
      maintenance
      MCP server for the Post for Me API, enabling publishing, scheduling, editing, deleting, and analyzing social media posts across 9 platforms from any MCP client.
      27
      26 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 11 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. The tools cover separate domains like publishing (create_post, get_publishing_post), analytics (get_post_analytics, get_profile_analytics), inbox management (get_messages), and listing resources (list_* functions). Descriptions explicitly differentiate similar tools, such as get_messages for inbound messages versus get_post_analytics for outbound metrics.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case throughout. The naming is highly predictable: 'create_post', 'get_messages', 'list_profiles', etc. There are no deviations in style or convention, making the set easy to navigate and understand at a glance.

    Tool Count5/5

    With 11 tools, the count is well-scoped for a social media management server. Each tool earns its place by covering essential operations like publishing, analytics, and resource listing. This number is typical for such a domain (3-15 tools), providing comprehensive functionality without being overwhelming.

    Completeness4/5

    The tool surface is nearly complete for social media management, covering key areas like post creation, retrieval, analytics, and resource listing. Minor gaps exist, such as no update_post or delete_post tools for post lifecycle management, but agents can likely work around this by creating new posts or using existing tools for basic operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources