Free + Pro

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

01

Create drafts or publish posts from MCP, CLI, HTTP, or the desktop UI.

02

Use real Electron browser sessions instead of fragile browser extensions.

03

Keep multiple accounts isolated with persistent platform partitions.

04

Track successes, failures, schedules, editor URLs, and policy blocks.

05

Enable professional automation through built-in licensing hooks.

06

Add platforms by implementing an adapter — without touching the core.

Built for specific operators

AI agent operatorsIndependent creatorsDeveloper-tool teamsMarketing and content teams

Product

Supported surfaces and platforms

Developer

CSDNJuejinZhihuSegmentFaultOSChina51CTOCnblogsYuque

Media

WeChat OfficialBaijiahaoSohuWeiboBilibiliEastmoneyXueqiuDoubanWoshipm

Social & video

XiaohongshuDouyinKuaishouWeChat Channels

Global API

Dev.toWordPressGhostTelegramDiscordMastodonThreadsBlueskyTumblr

Related reading

Docs

Core concepts

How OmniPost works — one publishing core, four interfaces, draft/publish/schedule, isolated accounts, and honest results.

Docs

Supported platforms

The platforms OmniPost can publish to, grouped by type, with how each one runs and how far automatic publishing is verified.

Docs

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.

Docs

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.

Docs

API reference

The MCP tools, CLI commands, and key HTTP endpoints OmniPost exposes.

9 min

Check account health before publishing with OmniPost

Learn why OmniPost publish workflows should inspect account health before going live, including when to look at rate limits, login warnings, and recent failures instead of treating publish as a pure content check.

Read
11 min

One core, four faces: UI, CLI, HTTP, and MCP

This article explains why a desktop app should expose UI, CLI, HTTP, and MCP on top of one shared core, and how that design lowers maintenance cost while making AI-agent workflows more reliable.

Read
11 min

Why publishing tools need a 24-hour title dedup window

Learn why multi-platform publishing tools use a 24-hour title dedup window, what real duplicate-publish failures it prevents, and why this guardrail is a reliability feature rather than an arbitrary restriction.

Read
10 min

Should every platform get its own headline?

This guide explains when one article should use different headlines on Zhihu, CSDN, Juejin, and CNBlogs, and how to adapt titles by platform without breaking title-body consistency.

Read
10 min

Draft capabilities across Chinese platforms in 2026

A practical 2026 comparison of draft workflows across Chinese publishing platforms: which ones support programmable draft creation, which allow a later publish step, and which still require manual release.

Read
6 min

Why WeChat turns whitespace into empty list items

This guide explains why WeChat Official Account drafts can show alternating empty list items, how the new editor reinterprets structural whitespace, and how to fix the issue before publishing.

Read
8 min

Reviewing vs published in OmniPost publish status

In OmniPost, reviewing and published can both mean “the post was sent”, but they are not the same kind of success. This guide explains the difference, when to keep watching, and when a post is stable enough to count as truly live.

Read
6 min

request_login vs add_account in OmniPost

In OmniPost, use request_login to restore an existing account and add_account to attach a new one. This guide explains the boundary, the CLI commands, and why the choice affects multi-account publishing.

Read
10 min

Recover from rate limits with publish_draft

When a platform rate-limits a formal publish attempt, the safest recovery path is often not to publish again but to confirm whether a draft already exists and continue from that draft with OmniPost publish_draft.

Read
11 min

OmniPost MCP capabilities in 2026

A practical map of OmniPost's 2026 MCP capabilities: publishing, scheduling, account groups, login management, status checks, and post-publication monitoring for AI-agent-driven content ops.

Read
8 min

Platform groups vs exact targets in OmniPost

This guide explains what account groups and exact targets solve in OmniPost, when to use each one, and how to combine them safely in scheduled and agent-driven publishing workflows.

Read
7 min

A team playbook for multi-platform content ops

Team content operations break down when writing, review, publishing, and logging live in different people's heads. This playbook shows how to structure a repeatable multi-platform publishing workflow with OmniPost.

Read
9 min

How to monitor published, reviewing, and offline posts

Publish success is not the same as content survival. This guide shows how to monitor reviewing, published, offline, draft, and unknown states with OmniPost so your team does not confuse submission logs with real publication status.

Read
8 min

Why creator accounts are safer in local-first tools

Creator accounts in content distribution workflows carry login sessions, reviews, rate limits, and publishing history. This article explains why those accounts are usually safer and easier to recover when the boundary stays local-first.

Read
8 min

Local-first vs cloud cross-posting tools

This article explains the real account-boundary difference between local-first and cloud cross-posting tools, so teams can choose the right model for multi-platform publishing and AI-agent workflows.

Read
8 min

How OmniPost's referral program works

Learn who OmniPost's referral program is for, why it fits local-first publishing, and how to think about the reward beyond a simple discount.

Read
8 min

Why content distribution should be local-first

This guide explains why content distribution should be local-first, with a focus on account boundaries, login-state control, publish traceability, and fit for Markdown and AI-agent workflows.

Read
9 min

What OmniPost's free tier can actually do

Looking for a free multi-platform publishing tool? This guide explains what OmniPost's free tier can do, where the boundary is, and when it makes sense to upgrade.

Read
10 min

How to connect any AI agent to OmniPost

Learn how any AI agent can connect to OmniPost over MCP, CLI, or HTTP, then reliably check readiness, validate accounts, preview content, publish, and record results.

Read
9 min

Choosing between OmniPost CLI, MCP, and HTTP

This guide explains when to use OmniPost over CLI, MCP, or HTTP, and how to make a stable choice across AI agents, local Markdown pipelines, and existing backend systems.

Read
9 min

Scheduling a multi-platform content matrix

This guide explains why scheduling a content matrix takes more than platform drafts, and how to combine a shared topic queue, timing windows, platform rewrites, and result logging into a stable publishing system.

Read
9 min

An autonomous daily content pipeline with AI agents

This guide breaks down a practical daily content workflow for AI agents, from topic intake and bilingual drafting to quality checks, website publishing, indexing, multi-platform distribution, and logging.

Read