OmniSocials supports Claude MCP publishing across 10 social platforms
A walkthrough showed OmniSocials importing past posts, drafting platform-specific copy, and scheduling publishing across 10 networks for $10 per workspace through Claude. The setup bundles calendars, formatting, analytics, and scheduling into one chat-driven social stack.
TL;DR
- hasantoxr's walkthrough shows OmniSocials plugging into Claude through MCP, so a chat can draft, schedule, and publish social posts without jumping into a separate dashboard.
- In hasantoxr's style-import demo, OmniSocials pulls in old posts and generates a base prompt for Claude's custom instructions, which is the trick that makes the output look less like generic model copy.
- hasantoxr's content-calendar example and hasantoxr's scheduling step turn the workflow into two prompts: one to write a week of posts, one to place them on the calendar.
- According to hasantoxr's platform list, the stack covers 10 networks, including Instagram, TikTok, LinkedIn, X, Bluesky, Threads, and Mastodon, with formatting and character limits handled per platform.
- hasantoxr's pricing post pegs the product at $10 per workspace, while hasantoxr's compatibility note says the same install also works in Cursor, Windsurf, Codex, Gemini CLI, GitHub Copilot, and OpenClaw.
The live demos point to OmniSocials' Claude page, where the product is framed as a Claude-ready social workflow. You can watch the main walkthrough, jump straight to the voice-cloning step, and check the platform inventory for the part creative teams will care about most.
Three-minute setup
The setup is unusually short for anything touching multi-platform publishing. In hasantoxr's setup post, the flow is just create an OmniSocials account, connect social accounts, and add the MCP server to Claude.
The interesting bit is where the product puts the personalization work. According to hasantoxr's style-import demo, OmniSocials imports a user's existing posts, generates a base prompt from them, and has the user paste that into Claude's custom instructions.
That pushes brand voice into the model context before any scheduling UI shows up, which is smarter than bolting tone controls onto the end of a publishing pipeline.
Two prompts, one content calendar
The demoed workflow is simple enough to remember:
- Ask Claude to draft next week's content calendar.
- Ask Claude to schedule the finished posts.
In hasantoxr's content-calendar example, one prompt generates LinkedIn long-form posts plus X-native short-form copy with different hooks. Then hasantoxr's scheduling step shows Claude scheduling five posts for the following week and returning a confirmation view.
That turns the familiar social stack, writing, adaptation, scheduling, into one conversation instead of three separate tools.
Ten-platform publishing
According to hasantoxr's platform list, OmniSocials supports:
- YouTube
- TikTok
- X
- Bluesky
- Threads
- Mastodon
The same post says the product handles stories, reels, posts, scheduling, analytics, and a unified inbox, while Claude adapts formatting and character limits by platform. That is the part that makes the MCP angle more than a copywriting trick.
$10 pricing, plus clients beyond Claude
The price in hasantoxr's pricing post is $10 per workspace with analytics included, which is aggressive next to the Hootsuite and Sprout Social comparisons in the same thread.
The last useful reveal is that Claude is only one front end. In hasantoxr's compatibility note, hasantoxr says the same install command also works in Cursor, Windsurf, Codex, Gemini CLI, GitHub Copilot, and OpenClaw, which makes OmniSocials look more like an MCP-native social backend than a Claude-only add-on.
If you want the source page the thread links to, OmniSocials' Claude page is the canonical landing page surfaced in the evidence.