← Back to the journal

OmniPost vs xiaohongshu-mcp: one platform deep, or many platforms through one door

xiaohongshu-mcp is an open-source, free MCP server that reads and writes Xiaohongshu only; OmniPost is a closed-source desktop app that publishes to 41 platforms through one endpoint and never interacts. They are not substitutes, and many people run both. Verifiable facts only, plus when to pick the other one.

Short version: these two tools solve different problems. xiaohongshu-mcp lets an agent use one platform, Xiaohongshu, to the full: log in, post image and video notes, search, read the feed, read post details and comments, write comments. OmniPost lets an agent push one piece of content to 41 platforms, Xiaohongshu among them, and it only publishes; it does not read or comment.

  • You only work on Xiaohongshu, you want the agent to read data, search, and reply to comments, you want to read and modify the source, and you do not want to pay: use xiaohongshu-mcp.
  • The same piece goes to Xiaohongshu, WeChat Official Accounts, Zhihu, CSDN, Bilibili and more; you do not want one tool per platform or Docker; you need several accounts; you accept a desktop app and a subscription: use OmniPost.
  • Both: common. xiaohongshu-mcp handles reading and engagement on Xiaohongshu; OmniPost handles multi-platform publishing. Each keeps its own sessions; they do not interfere.

Facts as of 2026-10-15; xiaohongshu-mcp details come from its GitHub README, which is authoritative.

What each one is

xiaohongshu-mcp (github.com/xpzouying/xiaohongshu-mcp): an open-source MCP server written in Go, Apache-2.0, about 16k stars. Runs locally or in Docker and drives the Xiaohongshu web app through a headless browser. Features: QR login and login check, publish image notes (local files or http URLs), publish video notes (local files), keyword search, home feed, post details with like/save/comment counts and the comment list, and posting comments. Two officially recommended variants exist: Skills for OpenClaw (xiaohongshu-mcp-skills / xiaohongshu-skills) and a browser-extension edition, x-mcp, that needs no Docker.

OmniPost: a Windows / macOS desktop app, closed source, free tier plus Pro. It writes nothing and contains no LLM; it exposes one MCP endpoint (http://127.0.0.1:8787/sse, stdio also supported) and one omnipost CLI. Every (platform, account) pair gets its own isolated browser partition; sessions never leave the machine. On Xiaohongshu specifically it publishes image and video notes with topics and covers; it does not search, read posts or comment. Free: 8 developer-oriented platforms, 3 accounts, 30 posts per month. Pro: ¥39/month, ¥99/quarter, ¥299/year for 41 platforms and 50 accounts. The agent Skill and content-rule cheat sheets for 10 Chinese platforms are open source at github.com/OmniGoAI/omnipost-skill.

Difference 1: one platform deep, or many platforms wide

Of what xiaohongshu-mcp can do on Xiaohongshu, OmniPost does less than half. Reading the feed, searching, pulling comments and posting comments are "operations", and OmniPost deliberately leaves them out (see difference 3). If your agent loop is "see what is trending on Xiaohongshu, write a note, post it, read the comments", xiaohongshu-mcp closes the loop and OmniPost covers only the "post it" step.

The other way round, one OmniPost call carries several targets, targets: [xiaohongshu, weixin, zhihu, csdn], and each target returns its own structured result (stage, code); per-target titles or summaries fit in the same call. The gap shows as platforms multiply: one MCP per platform means one login, one config and one result format each, and the agent has to stitch them together.

Difference 2: open and free, or closed and paid

xiaohongshu-mcp is open source under Apache-2.0, costs nothing, has 30-plus contributors, gets fixed quickly by the community when the platform changes, and you can patch it yourself. That is a real advantage.

OmniPost's desktop client is closed, for a stated reason: once the details of a platform adapter are public, the platform can block it more easily. That is also why we open-sourced only the Skill, the connection guides and the platform rule sheets. The free tier works; Pro buys multi-platform, multi-account, scheduling, groups and maintained adapters.

Difference 3: engagement

xiaohongshu-mcp ships a tool for posting comments. How you use it is up to you, but the tool is there.

OmniPost does not. It publishes and reads back results (status, views, likes, comment counts); comments and DMs are always answered by a human. Platforms judge automated interaction far more harshly than automated publishing, and a flagged reply takes the whole account with it. This is a trade-off, not a capability gap.

Difference 4: deployment and multiple accounts

xiaohongshu-mcp is a Docker image or a binary; one instance maps to one Xiaohongshu account, so several accounts mean several instances, each with its own browser, cookie file and port. The repo's troubleshooting thread and the x-mcp extension both exist to lower the setup barrier, which tells you where users struggle most.

OmniPost is an installer; open the app and the service is up. Multiple accounts are built in: each account lives in its own Chromium partition, sessions isolated but all in one process, so dozens of accounts do not exhaust memory; accounts can be grouped and a group published in one go. Sessions warn before they expire, and anything missed because of a lapsed login is republished automatically within 48 hours of logging back in.

Where they are the same

  • Both use the real sessions in a local browser, never ask for your password, and have no cloud relay.
  • Both connect Claude Code, OpenClaw, Codex and Cursor through MCP.
  • Neither can prevent bans. Cloud-server IPs, fixed-interval schedules and templated copy are platform-rule problems, identical for every tool. xiaohongshu-mcp's README recommends a local browser on a residential network; OmniPost's policy layer adds daily caps, duplicate-title blocking, a failure circuit breaker, quiet hours and minimum spacing between targets, enforced server-side when an agent calls. Neither is "ban protection".

One-line decision

Xiaohongshu only, reading and engagement, open source: xiaohongshu-mcp. Many platforms through one door, many accounts, no Docker: OmniPost. Running both is a comfortable setup.

OmniPost unlocks a 7-day Pro trial with one click inside the app. To talk, open an issue titled with "chat" at github.com/OmniGoAI/omnipost-skill; 20 minutes gets you 3 months of Pro.

#OmniPost#xiaohongshu-mcp#comparison#Xiaohongshu#Claude Code#OpenClaw#MCP

More from the journal

4 min

Why WeChat Official Account Logins Expire Every 3–4 Days

Three measured rounds show the WeChat Official Account (mp.weixin.qq.com) QR login dies after 3–4 days no matter how active the session is. Here is what still works: expiry alerts, a retry queue and a pre-flight login check.

Read