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 OpenClaw

OpenClaw is a personal AI assistant with native MCP support. Connect OmniSocials to the remote MCP server with an API key or with OAuth, or run the npm package locally.

OmniSocials' remote server speaks Streamable HTTP only. OpenClaw uses SSE when a server has no transport, so always set "transport": "streamable-http".

Option 1: Remote server with an API key (recommended)

  1. Create an API key in OmniSocials (Settings → API).
  2. Put the key in OpenClaw's env file, so it never sits in the config:
TerminalTerminal
echo 'OMNISOCIALS_API_KEY=omsk_live_<YOUR_KEY>' >> ~/.openclaw/.env
  1. Stop the Gateway (the CLI edits saved servers only while it is stopped), add the server, probe it and start again:
TerminalTerminal
openclaw gateway stop openclaw mcp set omnisocials '{"url":"https://mcp.omnisocials.com","transport":"streamable-http","headers":{"Authorization":"Bearer ${OMNISOCIALS_API_KEY}"}}' openclaw mcp doctor omnisocials --probe openclaw gateway start

The same server in ~/.openclaw/openclaw.json, under mcp.servers:

JSON
{ mcp: { servers: { omnisocials: { url: "https://mcp.omnisocials.com", transport: "streamable-http", headers: { Authorization: "Bearer ${OMNISOCIALS_API_KEY}" }, }, }, }, }

You can also add it in the Control UI: Settings → MCP → Add server, Streamable HTTP, the URL above.

Option 2: Remote server with OAuth

TerminalTerminal
openclaw gateway stop openclaw mcp add omnisocials --url https://mcp.omnisocials.com --transport streamable-http --auth oauth openclaw mcp login omnisocials openclaw gateway start

The login opens OmniSocials in your browser: pick the workspaces OpenClaw may use and click Allow access.

Option 3: npm package (local)

Runs the MCP server as a subprocess. The npm package has fewer tools than the remote server.

JSON
{ mcp: { servers: { omnisocials: { command: "npx", args: ["-y", "@omnisocials/mcp-server"], env: { OMNISOCIALS_API_KEY: "omsk_live_<YOUR_KEY>" }, }, }, }, }

Verifying

Ask OpenClaw:

List my connected social accounts on OmniSocials

If OpenClaw responds with your accounts, the integration is working. If it errors, check the OpenClaw gateway logs. The error usually points at a missing config field or an invalid API key.

Last modified on October 20, 2026
Notionn8n
On this page
  • Option 1: Remote server with an API key (recommended)
  • Option 2: Remote server with OAuth
  • Option 3: npm package (local)
  • Verifying