An agent-native social publishing API and MCP server: 51 publishing operations across 15 networks, callable from code or directly by an AI assistant like Claude, with Python and Node SDKs.
Last verified · 2026-09-05 · by Moe Ameen
BulkPublish is a social media publishing and scheduling API built for software rather than for a person clicking buttons. On September 3, 2026, its maker (founder Muhammad Azeem) announced it had opened its entire publishing stack to AI agents: everything the web app can do — single posts, media uploads, recurring queues, feed-driven automation, and post-level analytics — is exposed programmatically on every plan. The company describes the surface as 51 publishing operations across 15 networks.
What makes it a distinctly agent-era product is how you reach those operations. Alongside a REST API, BulkPublish ships official Python and Node/TypeScript SDKs and a Model Context Protocol (MCP) server. The MCP server exposes each operation as a tool an assistant like Claude can call directly, so an agent can draft, queue, and publish across every connected network without a human ever opening a scheduling dashboard. The founder's framing — that an agent should not have to imitate a human to post something — is the whole positioning.
The listed networks span the major social surfaces plus several that most schedulers skip: Facebook, Instagram, X/Twitter, TikTok, YouTube, LinkedIn, Threads, Bluesky, Pinterest, Google Business Profile, Mastodon, Discord, Telegram, Tumblr, and Snapchat. There is a rate-limited free tier plus paid tiers for higher throughput. Because this is an early, fast-moving developer product, treat the exact operation count, network list, rate limits, and pricing as a launch-window snapshot and confirm any single figure against BulkPublish's own documentation before you build against it.
The honest creator framing matters here: BulkPublish is a distribution layer, not a creative one. It moves and schedules content it is handed and reports analytics back, but it generates no video, no images, no carousels, and no captions, and it has no brand-voice layer. An MCP `publish` call presupposes a finished, on-brand post already exists — and producing that post is the actual work.
BulkPublish is the last mile of an automated content pipeline — the pipe that ships a finished post. The first mile, making that post on-brand and platform-ready, is the part it deliberately leaves to you, and it is by far the larger job. A `publish(post)` call is only useful once `post` exists: the right aspect ratios, burned-in captions, a consistent face and look, copy in your voice within each platform's character limit. [Kompozy](/) is the engine that produces exactly that object. From a single source it generates the full inventory an automated pipeline needs to ship — captioned [Persona Shorts](/glossary/persona-shorts) and avatar video, brand-exact [Carousels](/glossary/hyperframes), Photo Posts and Quote Graphics, plus [blogs and newsletters](/glossary/output-buckets) — every output governed by a [Persona Brief](/glossary/persona-brief) so voice stays consistent and rendered through [HyperFrames](/glossary/hyperframes) for pixel-exact styling. Where BulkPublish assumes the content, Kompozy makes it.
For most creators, the cleaner truth is that they never need to wire BulkPublish at all: Kompozy already includes its own scheduling and [Autopilot](/glossary/autopilot) publishing across the eight primary social platforms plus blog and email, behind a per-post review gate — so the making and the shipping live in one app with no code. BulkPublish earns its place at the other end of the spectrum: if you are a developer or agent-builder assembling a custom distribution layer — or you need a raw network like Telegram or Snapchat that Kompozy does not target — it is a strong, purpose-built pipe. Generate the on-brand content in Kompozy; if your automation demands a bespoke publishing API, hand the finished assets to BulkPublish's MCP server to ship. One tool makes the content; the other only moves it.
BulkPublish is an agent-native social publishing and scheduling API. On September 3, 2026 it opened its full stack to AI agents — described as 51 publishing operations across 15 networks — reachable through a REST API, official Python and Node SDKs, and a Model Context Protocol (MCP) server that lets an assistant like Claude publish directly. It is built for software to call, not for a person clicking a dashboard.
No. BulkPublish is a distribution layer — it moves, schedules, and reports on content it is handed, but it generates no video, images, carousels, or captions and has no brand-voice layer. A publish call assumes a finished, on-brand post already exists. Producing that post is a separate job, which is what a content engine like Kompozy does.
They cover opposite ends of the pipeline. BulkPublish is the last mile — an API and MCP server that ships posts you already made across up to 15 networks. Kompozy is the first mile plus the shipping — it generates the on-brand Shorts, avatar video, carousels, images, blogs, and newsletters from a single source, then schedules and publishes them across eight social platforms plus blog and email inside one app, no code required.
Usually not. Kompozy already includes scheduling and Autopilot publishing across its platforms behind a per-post review, so the making and shipping happen in one place. BulkPublish makes sense at the developer end: if you are building a custom agent pipeline, want first-class MCP publishing, or need a niche network like Telegram or Snapchat that Kompozy does not target, you can generate assets in Kompozy and hand them to BulkPublish to distribute.