Skip to main content
Glama
jmeserve

sprout-mcp

by jmeserve
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SPROUT_API_TOKENYesYour Sprout Social API token, generated at Sprout Social → Settings → API → OAuth tokens
SPROUT_CUSTOMER_IDYesYour Sprout Social customer ID, found in your Sprout Social account URL or via the list_customers tool

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_customersA

List all customers/accounts accessible with the current API token.

Returns customer IDs and names needed for other API calls.

list_profilesB

List all social profiles for a customer.

Args:
    customer_id: Sprout customer ID. Defaults to SPROUT_CUSTOMER_ID env var.
list_tagsB

List all message tags for a customer.

Args:
    customer_id: Sprout customer ID. Defaults to SPROUT_CUSTOMER_ID env var.
list_groupsB

List all profile groups for a customer.

Args:
    customer_id: Sprout customer ID. Defaults to SPROUT_CUSTOMER_ID env var.
list_usersB

List all active users for a customer.

Args:
    customer_id: Sprout customer ID. Defaults to SPROUT_CUSTOMER_ID env var.
list_teamsB

List all teams for a customer.

Args:
    customer_id: Sprout customer ID. Defaults to SPROUT_CUSTOMER_ID env var.
get_profile_analyticsA

Get analytics metrics aggregated by social profile.

Args:
    profile_ids: Comma-separated Sprout profile IDs.
    start_time: Start of period (ISO 8601, e.g. '2024-01-01T00:00:00').
    end_time: End of period (ISO 8601, e.g. '2024-01-31T23:59:59').
    metrics: Comma-separated metric names. Common options:
             impressions, engagements, net_follower_growth, engagement_rate,
             video_views, reactions, comments, shares, clicks.
    timezone: Timezone for the report (e.g. 'America/Chicago'). Default: UTC.
    customer_id: Sprout customer ID. Defaults to SPROUT_CUSTOMER_ID env var.
get_post_analyticsA

Get analytics metrics for individual published posts.

Post-level metrics use the 'lifetime.' prefix (e.g. 'lifetime.impressions').
Common metrics: lifetime.impressions, lifetime.reactions, lifetime.engagements,
                lifetime.clicks, lifetime.shares, lifetime.comments, lifetime.video_views.

Args:
    profile_ids: Comma-separated Sprout profile IDs.
    start_time: Start of period (ISO 8601, e.g. '2024-01-01T00:00:00').
    end_time: End of period (ISO 8601, e.g. '2024-01-31T23:59:59').
    metrics: Comma-separated metric names with lifetime. prefix.
    limit: Number of posts to return (default 50, max 100).
    customer_id: Sprout customer ID. Defaults to SPROUT_CUSTOMER_ID env var.
get_messagesA

Retrieve inbound inbox messages (Smart Inbox) with optional filtering.

This endpoint returns INBOUND messages only (mentions, DMs, comments).
For OUTBOUND post counts and performance metrics, use get_post_analytics instead.

Args:
    profile_ids: Comma-separated Sprout profile IDs.
    start_time: Start datetime (ISO 8601, e.g. '2024-01-01T00:00:00').
    end_time: End datetime (ISO 8601).
    tag_ids: Comma-separated tag IDs to filter by (optional).
    limit: Number of messages to return (default 50).
    page_cursor: Pagination cursor from a previous response (optional).
    customer_id: Sprout customer ID. Defaults to SPROUT_CUSTOMER_ID env var.
create_postB

Create a draft or scheduled post in Sprout Social.

Args:
    profile_ids: Comma-separated Sprout profile IDs to publish to.
    text: Post content/body text.
    scheduled_send_time: When to publish (ISO 8601). Leave empty to save as draft.
    customer_id: Sprout customer ID. Defaults to SPROUT_CUSTOMER_ID env var.
get_publishing_postB

Retrieve a specific publishing post by ID.

Args:
    post_id: The publishing post ID to retrieve.
    customer_id: Sprout customer ID. Defaults to SPROUT_CUSTOMER_ID env var.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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