Sprout Social MCP Server

Note: This is an unofficial, community-built MCP server to use while Sprout Social works on releasing their official one.

A Model Context Protocol (MCP) server for the Sprout Social API. It lets AI assistants (Claude, Cursor, Devin, etc.) access your Sprout Social data — analytics, publishing, messages, listening, and more — through a standardized interface.

Quick Start

Prerequisites

• Node.js 18+

• A Sprout Social API token (how to create one)

• Your Sprout Social Customer ID (how to find it)

Running via npx

No installation required:

SPROUT_SOCIAL_API_KEY=your-token \
SPROUT_SOCIAL_CUSTOMER_ID=your-customer-id \
npx sprout-social-mcp

Configuration with Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "sprout-social": {
      "command": "npx",
      "args": ["-y", "sprout-social-mcp"],
      "env": {
        "SPROUT_SOCIAL_API_KEY": "your-api-token",
        "SPROUT_SOCIAL_CUSTOMER_ID": "your-customer-id"
      }
    }
  }
}

Configuration with Cursor

Add to your .cursor/mcp.json:

{
  "mcpServers": {
    "sprout-social": {
      "command": "npx",
      "args": ["-y", "sprout-social-mcp"],
      "env": {
        "SPROUT_SOCIAL_API_KEY": "your-api-token",
        "SPROUT_SOCIAL_CUSTOMER_ID": "your-customer-id"
      }
    }
  }
}

Configuration with VS Code (GitHub Copilot)

Add to your .vscode/mcp.json:

{
  "servers": {
    "sprout-social": {
      "command": "npx",
      "args": ["-y", "sprout-social-mcp"],
      "env": {
        "SPROUT_SOCIAL_API_KEY": "your-api-token",
        "SPROUT_SOCIAL_CUSTOMER_ID": "your-customer-id"
      }
    }
  }
}

Configuration with Devin

In Devin's MCP settings, add a new server:

• Name: sprout-social

• Command: npx -y sprout-social-mcp

• Environment Variables:

  • SPROUT_SOCIAL_API_KEY → your API token

  • SPROUT_SOCIAL_CUSTOMER_ID → your customer ID

Environment Variables

Available Tools

Customer Metadata

Analytics

Messages

Listening

Publishing

Media

Cases

Usage Tips

Post Analytics Pagination

The Sprout Social API paginates post analytics. Always check paging.total_pages in the response and request all pages:

Ask: "Get all Instagram post analytics for last week"
→ Tool calls get_post_analytics with page=1, then page=2, etc.

Valid Post-Level Metrics

All platforms (Instagram, Facebook, LinkedIn, TikTok, etc.):

• lifetime.impressions — total views

• lifetime.engagements — total engagement (likes, comments, shares, saves)

• lifetime.reactions — reactions only

• lifetime.video_views — video view count

• lifetime.saves — saves/bookmarks

• lifetime.comments_count — comment count

• lifetime.post_shares_count — share count

Facebook only:

• lifetime.post_link_clicks — clicks on links in the post

• lifetime.post_content_clicks — total clicks on post content

• lifetime.post_content_clicks_other — other content clicks

Platform limitations:

• Reach (lifetime.reach) is NOT available at the post level — only at the profile level via get_profile_analytics. This is a Sprout Social API limitation.

• Click metrics are only available for Facebook posts. For Instagram, the API silently ignores them (no error, but no data returned).

Invalid metrics (will cause errors): lifetime.comments, lifetime.shares, lifetime.reach

Finding Profile IDs

Use get_profiles first to discover your customer_profile_id values, then pass them to analytics or publishing tools.

Development

git clone https://github.com/jginorio/sprout-social-mcp.git
cd sprout-social-mcp
npm install
npm run build

To test locally:

SPROUT_SOCIAL_API_KEY=your-token \
SPROUT_SOCIAL_CUSTOMER_ID=your-customer-id \
node dist/index.js

License

MIT