OmniSocialsOmniSocials
DocumentationAPI reference
Help centerSupport
  • Documentation
  • API reference
Developers
  • Quickstart
  • API reference
  • SDKs
  • MCP server
  • CLI
For AI agents
  • Docs for AI agents
  • llms.txt
  • OpenAPI spec
  • Postman collection
Product
  • OmniSocials
  • Pricing
  • Changelog
  • Help center
Company
  • Support
  • Privacy policy
  • Terms of service

© 2026 OmniSocials

OmniSocials on GitHubOmniSocials on XOmniSocials on LinkedIn
Overview
Get started
SDKs
CLI
MCPDocs for AI agentsWebhooks
Guides
Platforms
Integrations
    OverviewClaudeChatGPTGrokMuseNotionOpenClawn8nMakeZapierAgent frameworksAgent SkillsSmithery
Migrate
Plans and billing
GlossaryChangelogAPI reference
Integrations

Post to social media from Muse

Muse is Meta's personal AI agent (muse.ai on the web, and the Muse apps for iPhone, Android and Mac). Muse builds custom connectors from a chat message: give it the OmniSocials MCP address once, and every Muse chat can draft posts, schedule content, and read your analytics.

Before you start

  • Muse signs in to OmniSocials with an API key. Create one under Settings → Organisation → Integrations → Muse and copy the key itself (it shows once). You do not need the MCP URL with the key in it.
  • Custom connectors are available where Muse is: the United States, and Canada on iOS and the web (September 2026). Meta does not review custom connectors.

Connect

  1. Open Muse and start a new chat.
  2. Send Muse this message:
Text
Create a custom connector for OmniSocials. It is an MCP server over streamable HTTP at https://mcp.omnisocials.com. It signs in with a bearer token: ask me for the API key in a secure prompt. Then list my social accounts and save the connector so I can use it in every chat.
  1. Muse asks how the server signs in. Choose the bearer token. Muse opens a secure prompt for the credential: paste your API key there, never in the chat.
  2. Muse connects, lists the OmniSocials tools and runs the first call. Ask it to save the connector so you do not repeat the setup in the next chat.

Muse sends the key as Authorization: Bearer omsk_live_<YOUR_KEY> on every call. To give Muse several workspaces, join their keys with a comma, the same as in the MCP URL.

Verifying the connection

In a new Muse chat, ask:

Show my connected social accounts on OmniSocials

Muse should call list_accounts and return the accounts in your workspace. If it reports an authentication error, create a new key in OmniSocials and hand it to Muse again through the secure prompt.

Approvals

Muse's settings decide what a custom connector may do on its own: read only, ask before every action, or allow. Set OmniSocials to ask first if you want to confirm each post before Muse creates or schedules it.

Capabilities

With OmniSocials connected, you can ask Muse to:

  • List connected accounts, media library items, or scheduled posts
  • Create drafts or scheduled posts with per-platform content
  • Upload media from a URL and attach it to a post
  • Query analytics for a post, account, or time period
  • Manage webhooks

The available tools match the public API. The key's workspace determines what Muse can see and do.

Last modified on October 20, 2026
GrokNotion
On this page
  • Before you start
  • Connect
  • Verifying the connection
  • Approvals
  • Capabilities