Announced September 3, 2026, BulkPublish exposed its full social publishing stack — single posts, media uploads, recurring queues, feed automation, and analytics — to autonomous agents through a REST API, Python and Node SDKs, and a Model Context Protocol server.
2026-09-03 · by Moe Ameen
On September 3, 2026, BulkPublish announced it had opened its entire social publishing stack to AI agents, giving autonomous software the same programmatic access a human gets from the scheduling dashboard. The company frames it as agent-first rather than a bolt-on: everything the web app can do — single posts, media uploads, recurring queues, feed-driven automation, and post-level analytics — is now callable through an API on every plan.
BulkPublish describes the surface as 51 publishing operations across 15 networks, covering Facebook, Instagram, X/Twitter, TikTok, YouTube, LinkedIn, Threads, Bluesky, Pinterest, Google Business Profile, Mastodon, Discord, Telegram, Tumblr, and Snapchat. Access runs through a REST API with bearer-token keys, official Python and Node/TypeScript SDKs, and a Model Context Protocol (MCP) server that exposes the operations as tools an assistant like Claude can call in natural conversation — scheduling posts, uploading media, checking analytics, and managing channels without a browser session. There is a free tier with published rate limits alongside paid tiers for higher throughput.
Founder Muhammad Azeem summed up the design shift: "We stopped designing for the person clicking buttons and started designing for whatever is calling us." He added that "an agent should not have to imitate a human to post something. If it can reason about the content, it should be able to publish the content."
Treat exact operation counts, network coverage, rate limits, and pricing as a launch-window snapshot — an early-stage developer product like this moves fast. Confirm any single figure against BulkPublish's own docs before building against it.
The news here is a pipe getting wider, and it is worth being precise about what that changes. BulkPublish is a publishing API: hand it a finished post and a token and it ships to fifteen networks, on a schedule, with analytics back. What it does not do — by design — is make the post. An agent still has to arrive with the caption, the video, the carousel, the thumbnail. That is exactly the half [Kompozy](/) owns: it *generates* the finished formats — captioned [Persona Shorts](/glossary/persona-shorts) and avatar video, [Carousel Posts and Photo Posts](/glossary/output-buckets) rendered brand-exact via [HyperFrames](/glossary/hyperframes), Quote Graphics, Text Posts, Blogs, and Newsletters — then schedules and publishes them across the eight social platforms plus blog and email on [Autopilot](/glossary/autopilot), all held to one voice by your [Persona Brief](/glossary/persona-brief). BulkPublish makes distribution a solved problem for developers; Kompozy makes the content that distribution needs, and ships it too.
There is also the timely move: "a social scheduler just went agent-native" is a story your developer- and marketer-adjacent audience is reacting to this week. Drop your take into Kompozy and one idea becomes a week of posts — a Carousel on what agent-first publishing means, a captioned Persona Short explaining MCP in plain English, Quote Graphics pulling Azeem's "designing for whatever is calling us" line, a Text Post for X and LinkedIn, and a Blog Article for the long-tail search — every piece on brand and published everywhere at once. For related shifts, see our coverage of [Snapchat's third-party ads MCP server](/news/snapchat-ads-mcp-server-third-party-ai) and [Hootsuite's July 2026 update](/news/hootsuite-new-features-july-2026). If you are weighing a raw publishing API against a done-for-you engine, the [Kompozy vs BulkPublish alternative](/alternatives/bulkpublish) page lays out the choice.
On September 3, 2026, BulkPublish opened its entire social publishing stack to AI agents, giving autonomous software the same programmatic access a person gets from the dashboard. It described the surface as 51 publishing operations across 15 networks, reachable through a REST API, official Python and Node/TypeScript SDKs, and a Model Context Protocol (MCP) server that exposes the operations as tools an assistant like Claude can call directly.
BulkPublish lists 15 networks, including Facebook, Instagram, X/Twitter, TikTok, YouTube, LinkedIn, Threads, Bluesky, Pinterest, Google Business Profile, Mastodon, Discord, Telegram, Tumblr, and Snapchat. Treat exact coverage as a moving target for an early-stage product and confirm against BulkPublish's own documentation before building against it.
No. BulkPublish is a publishing and scheduling API — it moves and schedules content it is handed and reports analytics back, but it does not generate the video, image, carousel, or caption itself. Producing the finished, on-brand assets is a separate job, which is what a content engine like Kompozy does before handing posts off to be published.
BulkPublish is a developer-facing publishing API and MCP server — you or your agent bring finished posts and it ships them across networks. Kompozy is a content generation and publishing engine: it produces 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. One distributes what you give it; the other makes the content and distributes it.