Social media management from Muse

Open a new chat in Muse and ask it to create a custom connector for the remote MCP server at https://mcp.omnisocials.com. Muse builds the connector, sends you a sign-in link, and you approve access with your OmniSocials account. No settings form and no API key handling needed.

Yes. Muse custom connectors speak the Model Context Protocol over streamable HTTP. Muse builds the bridge itself with the official MCP SDK and keeps credentials in its Secure Credentials Store. Meta does not review custom connectors, so you approve the access yourself.

Draft, schedule and publish posts across 11 platforms, upload media, view analytics, manage connected accounts, reply in the social inbox, and set up webhooks, all in plain language from the chat.

No. The OmniSocials MCP server supports OAuth with dynamic client registration, so Muse registers itself and sends you a sign-in link. If you prefer an API key, give Muse https://mcp.omnisocials.com?API_KEY=your_key through its secure credential prompt, never in the chat itself.

Yes, by default. Muse checks with you before sensitive actions, and every outbound request passes its Sentinel approval agent. You can tighten or loosen this per connector in Muse's settings, for example read-only access for analytics.

Muse is rolling out in the US first, on iOS, Android, the web at muse.ai, and inside WhatsApp. The OmniSocials connector works the same on each, because Muse runs in Meta's cloud and connects to our hosted server.

Instagram, Facebook, LinkedIn, YouTube, TikTok, X, Pinterest, Threads, Bluesky, Mastodon, and Google Business, including Stories and Reels where available.