Postcrow MCP: schedule social posts from your terminal

Postcrow exposes its full feature surface as a Model Context Protocol server. Once configured, you can list, draft, schedule, recycle, and pull analytics from Claude Code, Cursor, or any MCP-compatible client — without opening a browser.

This article covers what the server provides, how to set it up, and which workflows it was designed for.

Setup

Generate an API key in Settings → API keys. The MCP server requires a Pro or Agency plan. Then add this entry to your MCP client configuration:

{
  "mcpServers": {
    "postcrow": {
      "command": "npx",
      "args": ["-y", "@postcrow/mcp"],
      "env": {
        "POSTCROW_API_KEY": "psk_..."
      }
    }
  }
}

Reload the client. The Postcrow tools are listed alongside any other MCP servers you have configured.

Optional environment variables

• POSTCROW_API_URL — override for self-hosted installs. Defaults to https://postcrow.app.
• POSTCROW_PROJECT_ID — pin a default project so you don't have to pass project_id to every call.

Tools

The server exposes fifteen tools, grouped by purpose.

Read

• postcrow_list_projects
• postcrow_list_accounts — connected social accounts per project, including token health
• postcrow_list_posts — filter by status (draft / scheduled / published / failed)
• postcrow_top_posts — ranked by engagement (likes + 2× comments + 3× shares)
• postcrow_cross_project_overview — scheduled posts across every project in a date window

Write

• postcrow_create_draft
• postcrow_schedule_post
• postcrow_update_post
• postcrow_publish_now
• postcrow_delete_post
• postcrow_recycle_post

Bulk and AI

• postcrow_bulk_schedule — schedule N posts evenly across a date range in one call
• postcrow_ai_compose — given a brief, returns one draft per requested platform, in the project's trained voice
• postcrow_smart_recycle — finds top performers and returns AI-rewritten variations
• postcrow_campaign — deploys one brief across multiple projects, each in its own voice

Example workflows

The tools are most useful in combination. A few patterns:

Cross-project review.

"What's scheduled across all my projects this week?"

The client calls postcrow_cross_project_overview and returns a per-project timeline. Useful as a daily or weekly health check.

Recycle top performers.

"Recycle the top 3 LinkedIn posts from last month with fresh variations. Schedule them Monday, Wednesday, and Friday next week at 9am Paris."

The client calls postcrow_smart_recycle for the project, reviews the returned drafts, then postcrow_schedule_post on each.

Cross-brand announcement.

"Announce the new pricing across the five product brands. Each in their own voice. Schedule for Tuesday 10am Paris, stagger by 5 minutes."

One call to postcrow_campaignhandles the full fan-out. Each project's trained brand voice is auto-loaded server-side.

Authentication and authorization

Each API key belongs to one user. Calls are scoped to that user's projects only. Keys are stored as SHA-256 hashes — the full key is shown once at creation and can't be retrieved later. Revoke a key any time in Settings → API keys; revocation is immediate.

Calls authenticated with an API key are gated behind an active Pro or Agency subscription. Web-app usage remains available on the Free plan.

Source and license

The MCP server is open-source under MIT on GitHub. You can read the source, fork it, contribute back, or run it against a self-hosted Postcrow instance using the POSTCROW_API_URL override.