Summary

Check the plan limit before you wire an agent to it.

The headless design is the point: no browser automation, no session that expires mid-run, and structured JSON that a model can act on. The constraint worth knowing first is the quota — the free plan allows 30 API requests per day, against burst ceilings of 60 write and 300 read requests per minute, so an agent that polls post status in a loop will exhaust a free account quickly.

What it is

The MCP server for BulkPublish, a social publishing API. You connect Facebook, Instagram, X, TikTok, YouTube, Threads, Bluesky, Pinterest, Google Business Profile, LinkedIn, Mastodon, Discord, Telegram, Tumblr and Snapchat once in the dashboard; the server then exposes those channels to an agent as tools, with no browser session or OAuth pop-up at run time.

What you get

50 tools over the publishing API, including `create_post` to draft, schedule or publish, `list_channels` to see what is connected, `upload_media` for images and video, and `get_analytics` for engagement figures
`compose_post`, an interactive composer that renders in clients supporting MCP Apps
Scheduling that takes an ISO 8601 `scheduledAt` plus an IANA `timezone`; a time in the past queues the post for immediate publishing
Draft state — a post saved as a draft stays put until you publish it explicitly
Two ways to run it: locally over stdio, or the hosted endpoint at `https://mcp.bulkpublish.com/mcp`

Requirements

A free BulkPublish account and an API key from Settings > Developer — keys start with `bp_` and are shown once. The MCP server is the npm package `@bulkpublish/mcp-server`, version 1.2.0, launched through `npx` with `BULKPUBLISH_API_KEY` in the environment. Social accounts must be connected in the dashboard before any channel can be posted to.

Setup effort

One command plus a key — npx -y @bulkpublish/mcp-server, then supply credentials