Sprout Social MCP Server

A Model Context Protocol server that gives AI assistants complete access to the Sprout Social API — analytics, inbox messages, social listening, content publishing, media uploads, and support cases. Works with Claude, GPT, or any MCP-compatible client.

Why This Exists

Sprout Social is the command center for social media teams managing multiple brands across multiple networks. But its power lives behind a dashboard that requires manual interaction for every query, every export, every draft. This server turns that dashboard into a conversation — ask your AI assistant to pull analytics, draft posts, search listening data, or triage support cases without switching tabs.

Every endpoint in the Sprout Social API is covered. No gaps, no workarounds.

What You Can Do

Ask your AI assistant to work with Sprout Social directly:

• "How did our Instagram perform last month?" — Pull profile-level impressions, engagements, and follower growth across any date range

• "Show me our top posts on LinkedIn this quarter" — Query post-level analytics sorted by engagement metrics

• "What are people saying about our brand?" — Search social listening topics for sentiment, volume, and trending themes

• "Draft a post announcing our product launch across all channels" — Create draft posts with media, scheduling, and tags

• "Are there any open support cases assigned to me?" — Filter cases by status, priority, assignee, and queue

20 Tools Across 6 Domains

Metadata — 8 tools

Discover and enumerate your Sprout Social account structure.

Analytics — 2 tools

Query performance metrics across profiles and individual posts. Supports all major networks: Instagram, Facebook, X (Twitter), LinkedIn, YouTube, Pinterest, TikTok, Threads, and Bluesky.

Messages — 1 tool

Listening — 2 tools

Publishing — 6 tools

Create draft content and manage media uploads of any size.

Cases — 1 tool

Quick Start

Install with MCPB

For Claude Desktop and other MCPB-compatible clients, download the local bundle from the v1.2.0 release:

Download sprout-mcp-server-1.2.0.mcpb

The bundle includes the Sprout Social favicon, production runtime dependencies, and setup prompts for API token or OAuth machine-to-machine credentials.

Prerequisites

• Node.js 18+

• A Sprout Social account with API access enabled (request access)

Install from npm

npm install -g @oliverames/sprout-mcp-server

Or run directly with npx:

npx @oliverames/sprout-mcp-server

Install from source

git clone https://github.com/oliverames/sprout-mcp-server.git
cd sprout-mcp-server
npm install && npm run build

Authentication

There are two ways to connect. Pick the one that fits how the server runs.

Option A — Token / machine auth (best for unattended automation)

Use this when the server runs headless (CI, a scheduled job, a shared host).

A1. API token (simplest). Generate a token in Sprout under Settings → Global Features → API Page → API Token Management.

export SPROUT_API_TOKEN=your-token-here

A2. OAuth 2.0 machine-to-machine. Client-credentials grant; the server acquires and refreshes the token automatically.

export SPROUT_CLIENT_ID=your-client-id
export SPROUT_CLIENT_SECRET=your-client-secret
export SPROUT_ORG_ID=your-org-id

Option B — Sign in with Sprout (best for a person)

Use this to connect your own Sprout account. You sign in at Sprout's real login page in the browser, so the server never sees your password and your normal 2FA/SSO applies. The interactive flow uses PKCE, so it needs only a client ID, with no client secret to configure or store.

1. Set your OAuth client ID (generate it under Settings → Global Features → API → OAuth Client Management):

   export SPROUT_CLIENT_ID=your-client-id

2. Run the login command and sign in when the browser opens:

   npm run login

The CLI starts a local callback server, opens your browser, and on success saves your session to ~/.sprout-mcp-auth.json. After that, run the server with no further configuration:

npm start

The server loads your saved session and refreshes tokens automatically in the background.

1Password Integration

If credentials are not set in the environment, the server automatically attempts to resolve them from 1Password CLI:

This means you can skip setting env vars entirely if you have op installed and a service account or session active. The fallback adds ~1-2s to startup and is silently skipped if 1Password is unavailable.

Configuration

Claude Desktop / Claude Code

Add to your MCP settings (e.g., .claude/settings.json):

{
  "mcpServers": {
    "sprout": {
      "command": "npx",
      "args": ["@oliverames/sprout-mcp-server"],
      "env": {
        "SPROUT_API_TOKEN": "your-token-here"
      }
    }
  }
}

From a local clone

{
  "mcpServers": {
    "sprout": {
      "command": "node",
      "args": ["/path/to/sprout-mcp-server/dist/index.js"],
      "env": {
        "SPROUT_API_TOKEN": "your-token-here"
      }
    }
  }
}

Any MCP Client

The server communicates over stdio transport. Point any MCP-compatible client at node dist/index.js (or npx @oliverames/sprout-mcp-server) with the appropriate environment variables.

Multi-Customer Support

On startup, the server auto-discovers your customer ID from the API. If your token has access to multiple customers, specify which one:

export SPROUT_CUSTOMER_ID=123456

Every tool also accepts an optional customer_id parameter to override the default per-request — useful for agencies managing multiple brands.

Response Formats

All tools accept a response_format parameter:

Supported Networks

Analytics, messages, and publishing support all networks connected in your Sprout Social account:

Built-In Reliability

The server handles the operational details so you don't have to:

• Rate limiting — Sliding-window throttle stays under Sprout's 60 req/min limit (soft cap at 55)

• Automatic retries — Exponential backoff on 429, 500, 503, and 504 responses (up to 3 retries)

• 202 polling — Media uploads and multipart completions automatically poll until processing finishes

• Input validation — Date ranges, profile limits, and required fields validated before hitting the API

• Graceful startup — Starts in unauthenticated mode with setup instructions if no credentials are found

• Response truncation — Large responses are intelligently truncated to stay within LLM context limits

API Coverage

This server provides 100% coverage of the Sprout Social Public API (v1).

Known Limitations

These are Sprout Social API constraints, not server limitations:

Development

npm install          # Install dependencies
npm run build        # Compile TypeScript
npm test             # Run test suite (119 tests)
npm run test:watch   # Watch mode
npm run dev          # TypeScript watch mode
npm start            # Start the server

Project Structure

src/
├── index.ts              # Entry point — auth, customer discovery, tool registration
├── constants.ts          # API URLs, rate limits, validation constraints
├── types.ts              # Shared TypeScript interfaces
├── schemas/
│   └── common.ts         # Reusable Zod schemas for tool input validation
├── services/
│   ├── auth.ts           # API token + OAuth M2M token management
│   ├── api-client.ts     # HTTP client with retries, rate limiting, 202 polling
│   ├── filter-builder.ts # Translates typed params → Sprout's filter DSL (eq, neq, in, gt, match, exists)
│   └── formatter.ts      # Markdown/JSON formatting + truncation
└── tools/
    ├── metadata.ts       # 8 tools — account structure discovery
    ├── analytics.ts      # 2 tools — profile + post performance
    ├── messages.ts       # 1 tool  — inbox message queries
    ├── listening.ts      # 2 tools — topic messages + aggregated metrics
    ├── publishing.ts     # 6 tools — drafts, media upload (simple + multipart)
    └── cases.ts          # 1 tool  — support case management

Architecture

All tool handlers are pure functions with the signature:

handler(client: ApiClient, customerId: number, params: T) → Promise<ToolResponse>

This makes every handler independently testable with a mock ApiClient — no server bootstrap required.

The filter builder translates friendly parameters into Sprout's custom filter DSL (field.op(values)), keeping the DSL syntax internal to the server.

License

MIT