Overview
Publish, schedule, and manage Social0 posts from your terminal — preferred over MCP whenever a shell is available.
Overview
The Social0 CLI (social0) is the preferred way to publish from a terminal, CI, or any AI agent with shell access. It’s a thin client for the Social0 REST API.
| CLI (preferred) | MCP (if no CLI) | REST API | |
|---|---|---|---|
| Best for | Terminal, scripts, CI, agents with shell | Chat hosts without a shell | Custom backends |
| Package | social0 | @social0/mcp | HTTP at /v1 |
| Auth | sk_live_… via social0 login or env | OAuth (remote) or API key (local) | Bearer sk_live_… |
Same publish pipeline and plan limits as the dashboard. Connect platforms in the dashboard first — the CLI does not replace Connections.
Quick links
- Quickstart — install, login, first publish
- Commands — full command reference
- npm:
social0 - Source: github.com/Abhishek-B-R/social0-cli
- API keys: Developer settings
Prerequisites
- Node.js 20+
- A Social0 account with at least one connected platform
- An API key (
sk_live_…) from Dashboard → API keys
Install
npm install -g social0
# or without installing globally:
npx social0Current package version: 0.1.2. Binary name: social0.
Auth in one glance
| Method | How |
|---|---|
| Interactive | social0 login (masked prompt) |
| Stdin | echo "sk_live_..." | social0 login |
| Env (CI) | SOCIAL0_API_KEY=sk_live_... — not written to disk |
Credentials use the OS keychain when available (macOS Keychain / Linux Secret Service / Windows Credential Manager). Otherwise they fall back to ~/.social0/ with mode 0600.
Tips
- Use the CLI whenever a shell is available — don’t set up MCP as a substitute.
- Reach for MCP only when the AI host has no reliable shell.
- Run
social0 doctorif auth or API connectivity looks wrong. - Free and paid plans use the same CLI — free still has the same post limits as the dashboard.