Distribute prepared content across 30+ platforms — from agents, scripts, or a desktop app.
OmniPost is an agent-neutral desktop publishing layer. It turns an existing title and Markdown body into drafts, published posts, schedules, and traceable records across many platforms.
Positioning
For creators, operators, and AI-agent workflows that already produce content and need safer, repeatable multi-platform distribution.
Capabilities
OmniPost
Create drafts or publish posts from MCP, CLI, HTTP, or the desktop UI.
Use real Electron browser sessions instead of fragile browser extensions.
Keep multiple accounts isolated with persistent platform partitions.
Track successes, failures, schedules, editor URLs, and policy blocks.
Enable professional automation through built-in licensing hooks.
Add platforms by implementing an adapter — without touching the core.
Built for specific operators
Product
Supported surfaces and platforms
Media
Social & video
Global API
Related reading
OmniPost — Getting started
Install OmniPost, connect platform accounts, and publish prepared content from the app or an agent.
Core concepts
How OmniPost works — one publishing core, four interfaces, draft/publish/schedule, isolated accounts, and honest results.
Supported platforms
The platforms OmniPost can publish to, grouped by type, with how each one runs and how far automatic publishing is verified.
Publishing, drafts & scheduling
The three publishing modes, how a post is checked before it goes out, the result codes you get back, plus groups and safety policy.
Driving OmniPost from an agent
Connect Claude Code, Codex, or your own code to OmniPost over MCP, CLI, or HTTP — and let an agent publish for you.
API reference
The MCP tools, CLI commands, and key HTTP endpoints OmniPost exposes.
Why agent-driven content teams need a distribution layer
A practical view of why content generation and content distribution should be separate systems — and what the distribution layer should actually own.
Read