MCP server for social media posting
OmniSocials provides an MCP (Model Context Protocol) server so AI assistants and tools can manage your social media directly. The server is available in two forms:
- Remote MCP endpoint at
https://mcp.omnisocials.com, for clients that speak MCP over HTTP (claude.ai, ChatGPT, Notion, OpenClaw) - npm package
@omnisocials/mcp-server, for clients that spawn local MCP servers over stdio (Claude Desktop, Cursor, Windsurf, Claude Code, OpenClaw)
Both expose the same tools and use your OmniSocials API key. Pick whichever your client supports.
Dedicated client guides
These clients have their own walkthroughs with screenshots and exact config paths:
For every other MCP-compatible client, use one of the setups below.
Remote MCP URL (hosted)
The remote endpoint supports two authentication modes:
OAuth (preferred). Clients with a connector/app flow (ChatGPT, claude.ai, grok.com) add https://mcp.omnisocials.com as the server URL and sign in when prompted; no key handling needed. See the ChatGPT guide for the walkthrough.
API key in the URL. For clients without an OAuth flow:
Text
Or, for clients that support Bearer token authentication, use the URL without the query parameter and pass the key as Authorization: Bearer omsk_live_<YOUR_KEY>.
npm package (local stdio)
For clients that spawn MCP servers as local subprocesses:
Terminal
Pass the API key via environment variable:
Terminal
The generic MCP config shape most clients accept:
JSON
Config file location varies by client:
| Client | Config path |
|---|---|
| Claude Desktop (macOS) | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Claude Desktop (Windows) | %APPDATA%\Claude\claude_desktop_config.json |
| Cursor | .cursor/mcp.json (in the project) or ~/.cursor/mcp.json (global) |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
| Claude Code | Managed via claude mcp add command |
Available tools
The MCP server exposes the public API as structured tools:
| Category | Tools |
|---|---|
| Posts | list_posts, get_post, create_post, create_and_publish_post, update_post, delete_post, publish_post, retry_post, list_approval_workflows, approve_post, reject_post, get_post_approval, get_recent_platform_posts, search_locations, list_pinterest_products, search_instagram_audio |
| Media | list_media, upload_media, update_media, check_media_compatibility |
| Folders | list_folders, create_folder |
| Hashtag Sets | list_hashtag_sets, create_hashtag_set, update_hashtag_set, delete_hashtag_set |
| Automations | list_automations, get_automation, create_automation, update_automation, delete_automation, get_automation_activity (comment-to-DM on Instagram or a Facebook Page, and DM keywords on X, chosen with platform; create_post also takes comment_dm_automation with platforms) |
| Accounts | list_accounts, get_account |
| Inbox | list_inbox_conversations, get_inbox_conversation, get_next_unanswered, mark_inbox_read, reply_to_inbox, hide_inbox_comment, delete_inbox_comment |
| Analytics | get_post_analytics, get_posts_analytics, get_analytics_overview, get_account_analytics, get_best_times |
| Webhooks | list_webhooks, get_webhook, create_webhook, update_webhook, delete_webhook, rotate_webhook_secret |
| Workspaces | list_workspaces, switch_workspace |
Each tool accepts the same parameters as the corresponding REST endpoint. create_post and update_post support the full post feature set, including per-platform automatic first comments and PDF-to-carousel uploads. The MCP server handles validation, retries, and response shaping so the assistant gets clean structured output.
For the Social Inbox, get_next_unanswered serves the next DM or comment that needs an answer together with the whole thread and the post it is on, and reply_to_inbox takes include_next: true to return the following item in the same call, so an assistant can work through the inbox in a loop. list_inbox_conversations accepts an unanswered filter, get_inbox_conversation shows the post (caption, link, image) and each message's #id, hide_inbox_comment hides or unhides Instagram, Facebook, TikTok, YouTube, and Threads comments, and delete_inbox_comment deletes Instagram, Facebook, and TikTok comments together with their replies (irreversible, the assistant confirms first). See Using it from an AI assistant.
Scopes
The MCP server respects your API key's scopes. A key without posts:write will see create_post in the tool list but calling it will return 403 Forbidden. Give the key exactly the scopes it needs for the task, and no more.
Alternative: Agent Skills
If your AI tool does not support MCP (e.g. GitHub Copilot, Codex, Gemini CLI), use Agent Skills instead. Agent Skills work via a CLI + markdown instruction file and support any tool that can run shell commands.