> For the complete documentation index, see [llms.txt](https://socialcli.gitbook.io/socialcli-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://socialcli.gitbook.io/socialcli-docs/introduction.md).

# Introduction

## Introduction <a href="#introduction" id="introduction"></a>

Social CLI is the unified social media infrastructure for AI agents and developers. Post, schedule, reply, and manage content across 14 platforms from a single interface - CLI, API, MCP, or dashboard.

It is designed to serve three main user groups, each with specific needs and use cases.

#### Agent Builders <a href="#agent-builders" id="agent-builders"></a>

Agent builders use Social CLI to give their autonomous AI agents a native social presence across 14 platforms - without writing platform-specific integration code.

Key features agent builders use:

* **MCP Server** - plug Social CLI into Claude Desktop, Cursor, or any MCP-compatible LLM; your agent instantly gains the ability to post, schedule, reply, and analyze across all platforms
* **Structured JSON** - every CLI command and API response returns parseable JSON; feed it into agent memory, chain it with other tools, pipe it into decision loops
* **Autonomous Mode** - start your agent in autonomous mode and it handles posting, replying, and growing without human intervention
* **SKILL.md** - a machine-readable capability manifest that tells any LLM exactly what Social CLI can do, with examples and parameter schemas

#### Creators and Brands <a href="#creators-and-brands" id="creators-and-brands"></a>

Creators and brands use Social CLI to manage all their social accounts from one dashboard - no code, no terminal, no switching between apps.

Key features creators use:

* **Compose and Schedule** - write posts with a rich editor, pick your platforms, set a time; goes live across all 14 platforms at once
* **Queue and Buffer** - build a content queue that drains automatically on your schedule; set cadence, reorder on the fly, never run dry
* **Unified Inbox** - every DM, mention, and comment from every platform in one feed; reply or archive without switching tabs (coming soon)
* **Analytics** - cross-platform performance metrics; impressions, engagement rate, follower growth, best posting times (coming soon)
* **Broadcast** - send bulk messages to all your contacts across Telegram, WhatsApp, Instagram, and Facebook in one click (coming soon)
* **Account Manager** - connect and monitor all 14 social identities from one place; OAuth in seconds, full token health visibility

#### Developers <a href="#developers" id="developers"></a>

Developers use Social CLI for automation pipelines, CI/CD workflows, and custom integrations. Every command returns structured JSON.

Key features developers use:

* **CLI Tool** - install globally with `npm install -g social-cli`; post, schedule, manage queue, read inbox, pull analytics - all from the terminal
* **REST API** - full programmatic access to every feature; authenticated with API keys, returns consistent JSON responses
* **Webhooks** - real-time event notifications for post published, post failed, message received, comment received, account connected/disconnected
* **Chat SDK** - build chatbots that reply across 7 messaging platforms with one codebase (coming soon)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://socialcli.gitbook.io/socialcli-docs/introduction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.