Chirpie MCP Server

@chirpie/mcp

Post, schedule, and track social posts on X, Bluesky, LinkedIn, Instagram and more from AI agents. Chirpie is one API for X/Twitter, Bluesky, LinkedIn, Threads, Mastodon, Instagram, Facebook and Telegram, covering posting, threads, scheduling, deletion and analytics. This MCP server puts all of it in front of Claude, Cursor, ChatGPT or any other MCP-capable agent, so "post this to X and LinkedIn, and schedule the follow-up for 9am" is a single sentence rather than a pile of platform SDKs, OAuth dances and rate-limit handling.

Hosted server (recommended)

You don't need to install anything. Point your client at:

https://chirpie.ai/mcp

Sign in when prompted and you're connected. No API key to copy, nothing to keep up to date.

Claude Code

claude mcp add --transport http chirpie https://chirpie.ai/mcp

Claude: Settings → Connectors → Add custom connector → https://chirpie.ai/mcp

Cursor: add to .cursor/mcp.json:

{
  "mcpServers": {
    "chirpie": {
      "url": "https://chirpie.ai/mcp"
    }
  }
}

ChatGPT: Settings → Connectors → Create → MCP server → https://chirpie.ai/mcp

Prefer a key over OAuth (CI, scripts, clients without an OAuth flow)? Send it as a header:

{
  "mcpServers": {
    "chirpie": {
      "type": "http",
      "url": "https://chirpie.ai/mcp",
      "headers": { "Authorization": "Bearer chirpie_sk_your_key_here" }
    }
  }
}

Local server (this package)

Run the same tool set locally over stdio.

npm install -g chirpie
chirpie login

Claude Code

claude mcp add chirpie -- npx @chirpie/mcp

Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "chirpie": {
      "command": "npx",
      "args": ["@chirpie/mcp"]
    }
  }
}

Cursor: add to your MCP settings:

{
  "mcpServers": {
    "chirpie": {
      "command": "npx",
      "args": ["@chirpie/mcp"]
    }
  }
}

The local server resolves credentials in this order:

1. CHIRPIE_API_KEY environment variable
2. ~/.chirpie/config.json (written by chirpie login)

The CLI and this server share that config, so one chirpie login covers both.

Tools

The hosted and local servers expose exactly the same tools. On the hosted server, chirpie_create_key, chirpie_list_keys, chirpie_revoke_key and chirpie_remove_x_keys require API-key auth. Sign in with OAuth and they are not offered, since an OAuth connection must not leave a long-lived key behind or tear down credentials your other connections depend on.

Try it

Once connected, ask your agent:

• "Post to X and LinkedIn: we just shipped v2."
• "Draft a 5-post thread about why we moved off cron, and schedule it for 9am tomorrow."
• "How did my last Bluesky post do?"
• "Connect my X account."

Links

• Docs: https://chirpie.ai/docs/mcp
• API reference: https://chirpie.ai/docs
• Dashboard: https://chirpie.ai/dashboard

MIT © Fireflo LLC

---

This repository is an automatically maintained source mirror of packages/mcp in the Chirpie monorepo. Pull requests opened here cannot be merged.