A social media management platform with a hosted MCP server: 48 tools let an AI assistant like Claude or ChatGPT schedule, publish, analyze, and manage the inbox across 11 platforms, included in a single $10/workspace plan.
Last verified · 2026-10-08 · by Moe Ameen
OmniSocials is a social media scheduling, publishing, and analytics platform, founded by Robert Ligthart in the Netherlands, that positions itself as a "social media layer for AI agents." On October 7, 2026 it launched a hosted Model Context Protocol (MCP) server that turns the whole platform into something an AI assistant can drive in plain language — connect once and the assistant can plan a calendar, draft and schedule posts, publish immediately, read analytics, and work a social inbox of DMs, comments, and mentions.
The MCP server exposes 48 tools across workspaces and accounts, posts, approvals, media, hashtag sets, discovery, analytics, a social inbox, and webhooks. Concretely, an assistant can create posts, stories, and reels as drafts or scheduled items; run approval workflows; upload media (up to 100 MB per file, or 1 GB via URL, with PDFs converted to carousels); pull 7-, 30-, or 90-day analytics and best-time suggestions; and read and reply to the inbox. It supports 11 platforms — Instagram, Facebook, LinkedIn (profile and page), YouTube, TikTok, X, Pinterest, Threads, Bluesky, Mastodon, and Google Business — with Reddit and Snapchat listed as coming soon.
Setup works with any MCP-compatible client; OmniSocials names Claude (web and desktop), Claude Code, ChatGPT, Cursor, and Windsurf among them. You can use the hosted remote server at mcp.omnisocials.com over streamable HTTP (OAuth sign-in), or run it locally via the npm package `@omnisocials/mcp-server` with an API key; inbox and analytics sit behind opt-in scopes. The same operations are also reachable through a REST API, SDKs, and a CLI. Pricing is a single plan at $10 per workspace per month billed annually (slightly more monthly), with a 14-day trial and no permanent free tier; the MCP server is included at no extra cost.
The honest framing for a creator: OmniSocials is a control surface for distribution, not a content generator. The assistant you connect writes the caption, and OmniSocials schedules, publishes, and reports on it — but neither produces the short-form video, the carousel, the avatar clip, or the on-brand image the post actually needs. Treat the 48-tool count, platform list, and pricing as a launch-window snapshot and confirm against OmniSocials' docs.
OmniSocials answers "how does my assistant post for me?" It does not answer "what, exactly, is it posting?" — and that second question is where the real work lives. An MCP `create post` call still needs a finished object behind it: a 9:16 video with burned-in captions, a brand-exact carousel, a face-locked avatar reading your script, copy in your voice within the platform's limit. OmniSocials assumes that object exists; the assistant it connects can write a caption but not render any of the visual formats. [Kompozy](/) is the studio that makes them. From one source or brief it generates captioned [Persona Shorts](/glossary/persona-shorts) and avatar video, brand-exact [Carousel Posts](/glossary/hyperframes), Photo Posts and Quote Graphics, plus [Blogs and Newsletters](/glossary/output-buckets) — all held to a written [Persona Brief](/glossary/persona-brief) and rendered through [HyperFrames](/glossary/hyperframes) so every piece is on brand, not just on time.
For most creators the simpler truth is that Kompozy already closes the whole loop on its own: it includes scheduling and [Autopilot](/glossary/autopilot) publishing across the eight social platforms plus blog and email behind a per-post review gate, so the making and the shipping live in one app with no assistant to prompt and no accounts to hand over. Where OmniSocials genuinely shines is as a conversational control surface and social inbox — if you live inside Claude or ChatGPT and want your assistant to triage comments and fire off scheduled posts across 11 accounts — including Bluesky, which Kompozy doesn't reach at all, plus Mastodon and Google Business, which Kompozy reaches via Direct Connect rather than natively — it is a tidy, cheap layer for that. The clean division of labor: generate the on-brand content in Kompozy; if you want an assistant to be the one that schedules and replies, point OmniSocials at the finished assets. One tool makes the week of content; the other is the chat-driven hand that posts it.
OmniSocials is a social media scheduling, publishing, and analytics platform that, on October 7, 2026, launched a hosted MCP server exposing 48 tools so an AI assistant like Claude or ChatGPT can plan, schedule, publish, analyze, and manage the inbox across 11 platforms in plain language. It also offers a REST API, SDKs, and a CLI, on a single plan at $10 per workspace per month.
No. OmniSocials schedules, publishes, and analyzes content and manages the social inbox; the connected AI assistant drafts the caption text. Neither renders the short-form video, carousel, avatar clip, or on-brand image a post needs. Producing those finished, on-brand assets is a separate job — the one a content engine like Kompozy does before anything is handed off to be published.
They sit at opposite ends of the pipeline. OmniSocials is a conversational distribution layer — an assistant schedules, posts, and replies across 11 accounts through its MCP server. Kompozy is the generation engine plus its own publishing: it produces captioned Shorts, avatar video, carousels, images, blogs, and newsletters from a single source under a Persona Brief, then schedules and publishes them across eight social platforms plus blog and email, with a per-post review gate. One makes the content; the other is a chat-driven way to post it.
Usually not. Kompozy already includes scheduling and Autopilot publishing across its platforms behind a per-post review, so making and shipping happen in one app without connecting an assistant or handing over account access. OmniSocials makes sense if you specifically want an AI assistant to be the one driving distribution and the social inbox, or you need a native connection to a network like Bluesky or Mastodon — in which case you can generate the assets in Kompozy and let OmniSocials post them.