# SocialBu [Health: Active]

**Category:** 🌐 Social Media  
**Repository:** https://github.com/socialbu/socialbu-agent  
**GitHub Stars:** 3  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/socialbu

## Description
Manage SocialBu posts, accounts, queues, analytics, automations, media, and listening.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "socialbu": {
    "url": "https://socialbu.com/mcp"
  }
}
```

## Documentation

## What SocialBu MCP server does

The SocialBu MCP server exposes authorized SocialBu data and actions to supported AI clients. It is designed for work involving connected accounts, teams, social posts, publishing queues, media, analytics, automations, curated content, and saved social listening items.

Agents can inspect connected accounts and teams, create drafts, schedule content, update posts, and publish posts when asked. They can also work with custom queues and media uploads, read account and post analytics, inspect automations, enable or disable them, browse curated content, and manage saved Listen items by reading, archiving, restoring, or deleting them.

## How it works

The SocialBu MCP server is hosted by SocialBu and uses Streamable HTTP at `https://socialbu.com/mcp`. Authentication takes place through OAuth: the client opens SocialBu in a browser, where the user signs in and approves access. Credentials should not be entered into an AI prompt.

The repository is not a local API proxy or a second implementation of SocialBu’s business logic. It provides portable agent instructions and client manifests, while the hosted MCP service remains the source of truth. The separate SocialBu CLI is still available for terminal scripts and environments without MCP support; it is not bundled here.

## Setup and configuration

Connect a client to the hosted MCP URL and complete the browser-based authorization flow. The repository also provides installation paths for clients that support its agent skill or native extensions:

- Install the reusable skill with `npx skills add socialbu/socialbu-agent`.
- Install the Gemini CLI extension with `gemini extensions install https://github.com/socialbu/socialbu-agent`, then restart Gemini CLI and authorize SocialBu.
- In Claude Code, add the marketplace and install the `socialbu` plugin.
- GitHub Copilot CLI and Qwen Code have their own extension or plugin installation commands in the repository instructions.

Some clients may need the MCP URL added separately if they do not install bundled MCP servers from `mcp.json`. Client-specific guidance covers ChatGPT, Codex, Cursor, GitHub Copilot, Windsurf, Cline, Zed, OpenCode, Grok Build, and Qwen Code.

## Tools and capabilities

The SocialBu MCP server supports workflows such as:

- Reviewing connected social accounts and teams.
- Drafting, scheduling, editing, and publishing posts.
- Uploading media and using custom publishing queues.
- Reading account-level and post-level analytics.
- Reviewing and changing automation status.
- Browsing curated content.
- Managing saved Listen records, including archive, restore, and delete actions.

These capabilities make it suitable for AI-assisted social publishing, content queue maintenance, reporting, and review of saved listening data within SocialBu.

## Limitations and notes

Available operations depend on the user’s SocialBu plan, permissions, teams, connected networks, and account types. A client’s ability to connect does not guarantee that every listed operation is available for every account.

The SocialBu MCP server requires an MCP-capable client and an authorization flow through SocialBu. It is not the right package for terminal-only environments that do not support MCP; those environments can use the separate SocialBu CLI instead. Do not paste a SocialBu password or API token into a prompt.

_Full upstream README: https://allmcps.com/mcp/socialbu/readme_