Log inSubmit server
Chirpie logo

Chirpie

Publish, schedule, manage, and analyze social posts across connected accounts through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Chirpie

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "chirpie": {
      "command": "npx",
      "args": [
        "@chirpie/mcp"
      ],
      "env": {
        "CHIRPIE_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Chirpie MCP server gives AI agents tools for publishing, scheduling, drafting, threading, and analyzing social media posts across connected accounts. It supports X/Twitter, Bluesky, LinkedIn, Threads, Mastodon, Instagram, Facebook, and Telegram through either a hosted HTTP endpoint or a local stdio package. Reach for Chirpie when an agent needs to coordinate posts across multiple accounts, manage queued content, or inspect engagement. OAuth is available through the hosted service, while local usage can authenticate with a Chirpie API key or CLI login.

Use cases

  • Publish one announcement to several connected accounts
  • Schedule a social media campaign with drafts and time zones
  • Create and manage multi-part social threads
  • Review engagement metrics for published posts
  • Connect and control social accounts from an AI client

Key features

  • Multi-account publishing
  • Post scheduling and drafts
  • 2–25-part thread creation
  • Media upload and attachment
  • Post analytics and refresh
  • Social account and API key management

Tools30

What Chirpie lets your agent do. Expand a tool for its parameters.

Self-reported~638 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

9/9 checks healthy over the last 55d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · @chirpie/mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads2.3kPackage downloads in the last 30 days.
Last commit12d agoMost recent push to the default branch.
Tools exposed30Callable tools this server registers over MCP.

How Chirpie works

What Chirpie does

Chirpie provides MCP tools for managing social publishing workflows from an AI client. Agents can upload images or videos, publish feed posts, create 2–25-part threads, save drafts, schedule content, edit unpublished posts, and retrieve publishing results. A post or thread can target one account or multiple connected accounts in a single call, with per-account text, media, or publishing configuration available for multi-account operations.

Supported connection tools cover X/Twitter, LinkedIn profiles, Threads, Instagram, Facebook Pages, Bluesky, Mastodon, and Telegram. Instagram and Facebook publishing can use platform-specific placements such as feeds, stories, and reels where supported. First comments can be attached to posts or threads for X, Threads, Instagram, and Facebook; failed first comments can be retried separately.

The server also manages the account lifecycle. Agents can list active and inactive accounts, activate or deactivate connected accounts, and disconnect accounts. Deactivation leaves an account connected, while disconnection ends the connection and cancels its scheduled posts. Post analytics return engagement metrics for published content, using stored snapshots unless a refresh is requested.

How it works

Chirpie is available as a hosted MCP server at https://chirpie.ai/mcp or as a local npm package. The hosted option uses sign-in through the MCP client and can also accept a Chirpie API key in an authorization header. The local server runs over stdio and uses credentials from CHIRPIE_API_KEY first, then from the configuration created by chirpie login.

Publishing operations support scheduled timestamps and an IANA timezone when the timestamp has no offset. Passing an idempotency key makes supported publishing, media, and comment retries safe. Multi-account publishing accepts up to 25 account IDs and returns a group ID plus an individual result for each account, so an agent can inspect partial success rather than treating the operation as all-or-nothing.

Chirpie retains deleted posts with a deleted status. Hiding a post only removes it from Chirpie listings; it does not change the post on the social platform. Listing and retrieval tools are read-only, while clients can use MCP tool annotations to request confirmation for destructive actions such as deletion, account disconnection, queued-post edits, and key revocation.

Setup and configuration

For the hosted server, configure the MCP client with the URL https://chirpie.ai/mcp, then sign in when prompted. API-key authentication uses an HTTP Authorization: Bearer header and is suitable for clients or automation that cannot use OAuth.

For local use, install the package globally and authenticate with:

Terminal
npm install -g chirpie
chirpie login

The same credentials are shared by the CLI and local MCP process. Claude Code and Claude Desktop can launch the local package with npx @chirpie/mcp; Cursor can use either the hosted URL or the local command configuration.

API keys can be created, listed, and revoked through dedicated tools. Keys may be restricted with scopes. On the hosted server, key-management tools and removal of custom X application credentials require API-key authentication rather than an OAuth session.

Tools and capabilities

  • Upload media and attach returned media IDs to posts.
  • Publish immediately, schedule posts, or save them as drafts.
  • Create and update threads containing 2 to 25 parts.
  • Publish to several accounts and inspect the resulting group.
  • List posts by status, account, or multi-account group.
  • Delete, hide, unhide, and retrieve posts.
  • Add, retry, update, or remove supported first comments.
  • Read engagement metrics and optionally request a platform refresh, limited to once per post every five minutes.
  • Connect supported social platforms and configure custom X developer keys.

Limitations and notes

Platform behavior still affects what each connection can publish. First comments are accepted only for X, Threads, Instagram, and Facebook, and a failed first comment does not cause the parent post to fail. Without an idempotency key, repeating certain create or publish calls can produce duplicate posts or media uploads.

Disconnecting an account cancels its scheduled posts, while deactivation preserves the connection. LinkedIn Pages connection is identified as coming soon. Hosted OAuth sessions intentionally do not expose tools that create or revoke long-lived API keys or remove custom X credentials.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Chirpie

Chirpie is an MCP server that connects AI clients to social accounts on X/Twitter, LinkedIn, Threads, Instagram, Facebook, Bluesky, Mastodon, and Telegram. Its main tools upload media, publish or schedule posts and threads, manage drafts, retrieve analytics, and administer connected accounts.

Install the local package with `npm install -g chirpie`, then run `chirpie login`. The package runs over stdio and can be launched by clients such as Claude Code, Claude Desktop, and Cursor with `npx @chirpie/mcp`. You can alternatively use the hosted endpoint without installing anything.

Yes, Chirpie can schedule posts and threads instead of publishing them immediately. A schedule can use an IANA timezone when its timestamp has no offset, and drafts can be created first and later scheduled or published with the update tool.

Yes, Chirpie works with Cursor through either the hosted MCP URL or a local `npx @chirpie/mcp` configuration. The hosted configuration uses `https://chirpie.ai/mcp`; the local configuration runs the same tool set over stdio.

Chirpie publishes to multiple accounts by passing up to 25 account IDs to its post or thread tools. The response includes a group ID and an individual result for each account, while account-specific configuration can customize text, media, or first comments.

Related MCP servers

All in Social Media All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewChirpie AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/chirpie?style=directory)](https://allmcps.com/mcp/chirpie)
HTML Embed
<a href="https://allmcps.com/mcp/chirpie"><img src="https://allmcps.com/api/badge/chirpie?style=directory" alt="Chirpie on AllMCPs" /></a>