Overview
Use Social0 MCP only when you can’t run the CLI — hosted OAuth or local npx.
Overview
Social0 MCP lets AI assistants create, schedule, and publish posts when they cannot use the CLI (no reliable shell — e.g. Claude.ai or ChatGPT connectors).
Prefer the social0 CLI whenever you can (npm install -g social0). Use this MCP page only if the host has no shell.
When you do need MCP, remote OAuth is the default among MCP options — no Node.js, no API key in config.
| Remote MCP | Local MCP (npx) | |
|---|---|---|
| Endpoint | https://mcp.social0.app/mcp | npx -y @social0/mcp |
| Auth | Social0 OAuth (Connect → approve) | SOCIAL0_API_KEY in config |
| Needs Node.js? | No | Yes (Node 20+) |
| Use when | Chat hosts with remote connectors only | Stdio-only hosts with no CLI |
Both MCP paths use the same tools and the same Social0 publish pipeline as the dashboard / CLI.
Quick links
- Quickstart — Option A (remote) or Option B (local)
- Tools reference — what your agent can call
- Marketing: social0.app/mcp
- npm:
@social0/mcp - Source: github.com/Abhishek-B-R/social0-mcp
Prerequisites
- A Social0 account
- At least one platform connected in Dashboard → Connections
API keys are only for the local npx path — create them in Developer settings. Hosted OAuth mints a connector key automatically (you can revoke it there anytime).