BulkPublish
An agent-native social publishing API and MCP server for 15 networks, callable from code or directly by an AI assistant like Claude, with Python and Node SDKs.
Last verified · 2026-10-23 · by Moe Ameen
Published 2026-09-05 · Updated
Short answer
BulkPublish is a social media publishing and scheduling API built for code and AI agents rather than people clicking buttons. It posts to 15 networks, including Telegram, Mastodon, Discord, and Snapchat, through a REST API, Python and Node SDKs, and an MCP server that lets an assistant like Claude publish directly. It moves finished posts. It doesn't create the content.
Key takeaways
- BulkPublish is an API and MCP server for publishing to 15 social networks from code or an AI agent.
- It has Python and Node SDKs, and its local MCP server lists 79 tools.
- It schedules, uploads media, and reports analytics, but it doesn't generate posts.
- Kompozy users usually don't need it unless they're building a custom agent pipeline.
What is BulkPublish?
BulkPublish is a social media publishing and scheduling API built for software rather than for a person clicking buttons. Its GitHub README describes a social media API built for automation, AI agents, and LLMs: posts, scheduling with queue slots, media uploads, RSS and feed-driven pipelines, and analytics are all reachable from code. It publishes to 15 networks from one endpoint.
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 README puts it plainly: most social media tools are built for humans clicking buttons, and BulkPublish is built for code. Its local MCP server lists 79 tools.
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. The README bills it as a free publishing and scheduling API; check BulkPublish's own site for plan limits. 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.
What can you build with BulkPublish?
- A code- or agent-driven publishing pipeline that ships to up to 15 networks without a human touching a dashboard
- MCP tools an assistant like Claude can call directly to schedule posts, upload media, and read post-level analytics
- Recurring queues and feed-driven autoposting managed entirely through the API
- Cross-network distribution to niche surfaces some schedulers skip — Telegram, Tumblr, Mastodon, Discord, Snapchat
- Programmatic post-level analytics pulled back into your own tooling or agent loop
- A custom automation where your own generator produces assets and BulkPublish handles only the last-mile shipping
Where does BulkPublish fit in a content pipeline with Kompozy?
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 and avatar video, brand-exact Carousels, Photo Posts and Quote Graphics, plus blogs and newsletters — every output governed by a Persona Brief so voice stays consistent and rendered through 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 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.
- In Kompozy, generate the content from one source or brief — Persona Shorts, Carousels, Photo Posts, a blog, a newsletter — all held to your Persona Brief and rendered brand-exact with HyperFrames.
- Let Kompozy reframe each clip to 9:16, 1:1, and 16:9, burn in captions, and trim copy to each platform's limit, so the assets are genuinely publish-ready.
- For most workflows, publish straight from Kompozy: schedule across the eight social platforms plus blog and email on Autopilot behind a per-post review — no API, no code.
- If you are building a custom agent pipeline instead, export the finished assets and hand them to BulkPublish's MCP server or SDK to distribute across its 15 networks.
- Track results — Kompozy reports its own pipeline stats, and BulkPublish returns post-level analytics into your agent loop.
What does this look like in Kompozy?
A real quote graphic made in the Kompozy workspace. It's the kind of finished, platform-ready post a publishing API like BulkPublish assumes already exists.
Who is this for, and who should skip it?
Best for:
- Developers building their own agent that needs to post to social networks
- Teams that need networks like Telegram, Discord, Mastodon, or Snapchat
- Automation builders wiring RSS or CSV feeds into scheduled posts
Not ideal for:
- Creators who want a no-code app. BulkPublish is built for code
- Anyone who needs the posts made. It ships what you hand it
- Teams that want one app for making and publishing. Kompozy already schedules and posts its own output
Frequently asked questions
What is BulkPublish?
BulkPublish is an agent-native social publishing and scheduling API. It publishes to 15 networks 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.
Does BulkPublish generate the content it publishes?
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.
How is Kompozy different from BulkPublish?
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.
Do I need BulkPublish if I use Kompozy?
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.
How do we know this?
We checked every figure, date, and price on this page against the sources listed below on 2026-10-23, using BulkPublish's public GitHub README. Kompozy plan, format, and platform details come from kompozy.io and kompozy.io/pricing.
Sources
- GitHub — azeemkafridi/bulkpublish-api README (read 2026-10-23)
- Kompozy — Home (platforms, formats, Persona Brief, autopilot) (read 2026-10-23)
Related tools
- Postiz — An open-source, self-hostable social media scheduler with a chat-driven AI Smart Agent, an MCP server, and a public API — publishing to a broad set of networks under AGPL-3.0.
- Mixpost — Open-source, self-hosted social media management — schedule and publish from your own server with no monthly subscription.
- Hootsuite Social OS — Hootsuite's AI-native social operating system — four connected apps and a social-first AI agent called Wisdom.
- Buffer vs Later — Two of the most popular AI-assisted social media scheduling tools. Buffer is a channel-priced, multi-platform generalist; Later is an Instagram-first visual planner with link-in-bio and a creator marketplace. Both add AI only at the caption level.
- LinkedIn Post Proofreader — A LinkedIn Premium writing feature that reviews, shortens, or clarifies a post draft before you publish — polishing your own words instead of generating new ones.