Social0 MCP Server — Manage social posts from AI

What is the Social0 MCP server?

The Social0 MCP server is the official Model Context Protocol integration for Social0. It is a thin translation layer between AI assistants (Claude, Cursor, ChatGPT, VS Code) and the Social0 REST API. The MCP server contains no business logic — it converts MCP tool calls into /v1 API requests using your API key.

flowchart TB
  A[AI Assistant] --> B[Social0 MCP Server]
  B --> C[Social0 REST API]
  C --> D[Social0 Backend]

What you can do

• List connected social accounts
• Create, update, delete, and list posts
• Upload images and video
• Publish immediately or schedule for later
• Track publish progress per platform (including partial multi-platform results)
• Get AI-native platform recommendations (suggest_best_platforms)

What the MCP server is not

• Not a replacement for the dashboard — use the app for visual editing and account management
• Not where OAuth happens — connect platforms in Dashboard → Connections first
• Not a separate backend — it only calls the public REST API

What you need before starting

1. Social0 account with at least one connected platform
2. API key (sk_live_…; legacy s0_live_… still accepted)
3. Node.js 20+ installed
4. An MCP host (Claude Desktop, Cursor, VS Code, or ChatGPT)

Quick start

git clone https://github.com/Abhishek-B-R/social0.git
cd social0/social0-mcp
cp .env.example .env
# Set SOCIAL0_API_KEY=sk_live_... in .env
npm install && npm run build

Then configure your MCP host — see Quick start or host-specific guides below.

Supported AI hosts

Environment variables

Example prompts

Copy these into your AI assistant after MCP is configured:

Show my connected Social0 accounts.
Create a LinkedIn post about AI trends in 2026.
Schedule tomorrow's product launch at 9 AM on LinkedIn and X.
Publish my latest draft.
Show all scheduled posts.
Upload ./assets/logo.png and post it to Twitter and LinkedIn.
Which platforms should I publish this to: "Just shipped v2!"
Did my post publish? Check the tracking ID from the last publish.

Multi-platform publishing

MCP and REST publish fan out to all target platforms in parallel — not sequentially. You receive one tracking_id; poll get_publish_status until the job reaches a terminal state: completed, failed, or partial.

Video uploads (YouTube, X, Instagram) can take 1–5+ minutes. Poll every 2–5 seconds while status is processing. See Tools reference — get_publish_status and Publish via API.

Links

• Quick start
• Tools reference — all 13 tools
• API keys
• Troubleshooting
• REST API — underlying interface
• GitHub: social0-mcp/

FAQ

Q: Do I need to pay for MCP?
A: MCP uses your existing Social0 plan. API access follows the same limits as your account.

Q: Can MCP connect my Instagram or Facebook account?
A: No. Connect platforms in the dashboard. MCP only posts to already-connected accounts.

Q: Is my API key sent to Social0's servers?
A: Yes — the MCP server calls api.social0.app with your key, same as any API client. The key is stored locally in your MCP host config.

Q: Can I use MCP on mobile?
A: MCP hosts are desktop apps (Claude Desktop, Cursor). Mobile is not supported today.

Q: What's the difference between MCP and the REST API?
A: MCP is a translation layer for AI assistants. The REST API is the underlying interface. MCP calls REST.

Q: What does partial mean for publish status?
A: Multi-platform publish finished with mixed results — some platforms succeeded, some failed. Check errors in get_publish_status.

Q: What is suggest_best_platforms?
A: Analyzes your caption length and media to recommend platforms. Uses heuristics plus your connected accounts.

Q: How long should I poll publish status?
A: Text posts usually finish in seconds. Video to YouTube or X can take several minutes. Poll every few seconds until overall_status is terminal.

Q: Does MCP publish work the same as the dashboard Publish button?
A: Same outcome, slightly different plumbing. Dashboard runs on the server. API/MCP fans out per platform; X runs on the server; other platforms use a background worker.