Socialclaw

Name: Socialclaw
Author: ndesv21

@ndesv21

Socialclaw について

Social media scheduling MCP for AI agents posting to X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, and Pinterest.

#social-media #schedule #post #tiktok #x #instagram #linkedin #youtube

基本情報

カテゴリ

コミュニケーション

トランスポート

stdio

公開者

ndesv21

投稿者

ndesv21

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

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

ツール

List connected social accounts in the SocialClaw workspace. Optionally filter by provider (x, facebook, instagram_business, instagram, linkedin, linkedin_page, pinterest, tiktok, telegram, discord, youtube, reddit, wordpress).

Get publish capabilities and provider rules for connected accounts: what media is allowed, text limits, and whether publishing is currently possible. Pass accountId for one account, or provider to filter, or neither for all.

Start connecting a new social account. For OAuth providers this returns an authorizeUrl the user must open in a browser. Telegram requires botToken and chatId; Discord requires webhookUrl.

Upload a local media file (image or video) to SocialClaw hosted storage. Returns an asset id and a public URL that can be used as media_link in schedules.

Validate a schedule document against provider rules, media limits, account state, and publish times WITHOUT creating any posts. Always run this before apply_schedule.

Preview how a campaign schedule document expands into concrete posts and steps without creating anything.

Create a publishing run from a schedule document. Posts are scheduled or published through connected accounts. Send an idempotencyKey so retries do not create duplicate runs; one is generated when omitted.

Publish a previously created draft run, optionally at a given ISO-8601 start time.

List posts in the workspace with optional filters.

Get one post including its delivery state and provider identifiers.

List publish attempts for a post, including provider errors. Use this to debug failed posts.

Retry a failed post.

Cancel a scheduled post before it publishes.

Get the status summary of a publishing run and its posts.

Get analytics snapshots for a post, an account, or a run. scope must be post, account, or run; id is the matching identifier.

Get workspace usage counters and plan entitlement consumption.

Get workspace health, including connection state across providers. Pass provider to check one provider's connections.

概要

What is Socialclaw?

Socialclaw is a social media scheduling and publishing MCP server for AI agents. It provides 17 validation-first tools that let any MCP client (Claude Code, Claude Desktop, Cursor, etc.) publish through real connected accounts on X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, and Pinterest — all from one workspace. Unlike direct posting integrations, Socialclaw validates schedules against provider rules before posting, supports human preview and approval of drafts, and exposes per-attempt delivery state for debugging.

How to use Socialclaw?

Sign in at getsocialclaw.com/dashboard (Google), connect your social accounts, and create a workspace API key. Then add the server to your MCP client using the npx -y socialclaw mcp command with the SOCIALCLAW_API_KEY environment variable, or use the hosted streamable HTTP endpoint at https://getsocialclaw.com/mcp with an Authorization: Bearer <key> header. A typical agent flow is: list_accounts → account_capabilities → upload_asset → validate_schedule → apply_schedule → run_status.

Key features of Socialclaw

17 validation-first tools for publishing and inspection
Works with X, LinkedIn, Instagram, Facebook, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, Pinterest
Idempotency-key deduplication for safe schedule application
Draft preview and human approval before posting
Per-attempt delivery state for debugging failed posts
Upload media once and reuse hosted URLs across posts

Use cases of Socialclaw

Schedule and publish posts across multiple social platforms from one AI agent workspace
Validate schedules against provider rules (media limits, account types, publish times) before going live
Inspect and retry failed post attempts with detailed delivery state
Manage campaigns with preview, cancel, and retry capabilities
Track workspace analytics, usage, and health

FAQ from Socialclaw

How does Socialclaw differ from direct posting integrations?

Socialclaw is built so agents don't post blindly: it validates schedules against provider rules before posting, allows human preview and approval of drafts, and exposes per-attempt delivery state for debugging.

What runtime or dependencies are required?

The server runs via npx (no install needed) or as a hosted streamable HTTP endpoint. No additional runtime beyond Node.js (for the stdio transport) and an MCP client is required.

Where does user data and account information live?

Users sign in at getsocialclaw.com/dashboard and connect social accounts within a workspace. API keys are created per workspace, and the server communicates with Socialclaw’s hosted backend.

What transports are supported?

The server supports both stdio transport (via npx) and streamable HTTP transport (hosted at https://getsocialclaw.com/mcp).

How is authentication handled?

Authentication uses a workspace API key passed either as the SOCIALCLAW_API_KEY environment variable (for stdio) or as a Bearer token in the Authorization header (for HTTP).