概要
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).
