Socialclaw

What the socialclaw MCP server does

The socialclaw MCP server exposes SocialClaw’s hosted publishing service through the Model Context Protocol. It operates on accounts connected to a SocialClaw workspace, rather than connecting an agent directly to each social network. The available tools support account discovery, media handling, schedule operations, publishing, delivery inspection, analytics, usage checks, and workspace health checks.

Supported publishing destinations listed by the project include X, Facebook Pages, Instagram Business, standalone Instagram professional accounts, LinkedIn profiles and pages, Pinterest, TikTok, Discord, Telegram, YouTube, Reddit, and WordPress. Actual account capabilities depend on the provider and the accounts connected in the workspace.

How it works

The package starts the MCP server with npx -y socialclaw mcp. An MCP client launches that command as a local stdio process, while the process calls the deployed SocialClaw service. Authentication uses SOCIALCLAW_API_KEY, or credentials previously saved by the CLI through socialclaw login --api-key.

The workflow is validation-first. An agent can list accounts and provider capabilities, upload media, preview a schedule, validate it, and apply it with an idempotency key. It can then publish drafts or inspect posts, attempts, runs, analytics, usage, and health. Supported published posts can also be deleted through the provider-side deletion operation.

Setup and configuration

Install the package globally or invoke it through npx:

npm install -g socialclaw
socialclaw login

For an MCP client that accepts JSON server configuration, add a server entry similar to this:

{
  "mcpServers": {
    "socialclaw": {
      "command": "npx",
      "args": ["-y", "socialclaw", "mcp"],
      "env": {
        "SOCIALCLAW_API_KEY": "sc_live_your_key"
      }
    }
  }
}

Claude Code can add the same server with claude mcp add socialclaw --env SOCIALCLAW_API_KEY=sc_live_your_key -- npx -y socialclaw mcp. If the CLI has already saved credentials, the environment entry can be omitted. Account connection and workspace setup happen through the hosted SocialClaw dashboard or the CLI, including browser OAuth and manual Discord or Telegram connection flows.

Tools and capabilities

The socialclaw MCP server provides 17 tools covering these operations:

• List connected accounts and their provider capabilities.
• Upload hosted media for later publishing.
• Validate schedules and preview campaigns before applying them.
• Apply schedules with idempotency keys.
• Publish drafts.
• Retrieve posts and delete supported published posts.
• Inspect attempts, runs, and delivery status.
• Read post analytics, workspace usage, and workspace health.

The same hosted workspace can also be used from the SocialClaw CLI, OpenClaw-compatible skill bundle, Claude Code plugin, or custom agents that execute commands or make HTTP requests.

Limitations and notes

This is a client for a deployed SocialClaw workspace, not a self-contained local social-network connector. The workspace must have connected accounts with the required provider permissions, and the account’s capabilities vary by provider. A trial or paid plan is required for CLI and API access. The README also identifies Claude Code, Claude Desktop, Cursor, Cline, and Codex as supported agent environments; other clients need to support MCP server configuration or the underlying CLI and HTTP workflows.