All posts

MCP5 min read

Postcrow MCP: schedule social posts from your terminal

A social scheduler with a hosted Model Context Protocol server. Pilot your queue from Claude, ChatGPT, Codex or Cursor without leaving the conversation.

Postcrow exposes its full feature surface as a Model Context Protocol server, hosted at https://postcrow.app/api/mcp. Once connected, you can list, draft, schedule, recycle, and pull analytics from Claude, ChatGPT, Codex, 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

The server is hosted: there is nothing to install. MCP access requires a paid plan (Pro, Agency or Platform). Two ways to connect:

  • Sign in. Add https://postcrow.app/api/mcp as a remote MCP server or connector, then sign in to Postcrow when the client asks and allow it. This is how claude.ai, ChatGPT and Le Chat connect.
  • API key. Generate a key in Settings → Developer and send it as Authorization: Bearer psk_.... For Claude Code:
claude mcp add --transport http postcrow https://postcrow.app/api/mcp \
  --header "Authorization: Bearer psk_..."

The MCP page has the exact setup for each client: Codex, Cursor, VS Code, Gemini CLI, Zed, the OpenAI and Anthropic APIs, n8n and more.

Tools

The main tools, grouped by purpose (the full list is on the MCP page):

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_platform_constraints: limits, media formats and fields of each connected network, read before writing
  • postcrow_create_draft
  • postcrow_schedule_post: with per_network, one version per network in the same post
  • postcrow_publish_article: one long article for WordPress, Ghost, Blogger and Hatena Blog
  • postcrow_publish_media: a video, track or image for Vimeo, SoundCloud, Flickr and DeviantArt
  • postcrow_update_post
  • postcrow_publish_now
  • postcrow_delete_post
  • postcrow_recycle_post

Bulk and AI

Not switched on yet: the three AI tools below (postcrow_ai_compose, postcrow_smart_recycle, postcrow_campaign) run on Postcrow's AI writing, which is off for now. Your own AI can still write the posts and send them with the other tools.

  • 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 Bluesky 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_campaign handles 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, Agency or Platform subscription. Web-app usage remains available on the Free plan.

Pointing it at another instance

The server reads a POSTCROW_API_URL override, so it can talk to any Postcrow deployment rather than only the hosted one. The source is not public today.