SocialClaw MCP server
Give Claude, Cursor, or any MCP client direct access to real social publishing: connected accounts, hosted media, validation-first scheduling, and delivery inspection across 11+ platforms, all through one workspace API key.
Add SocialClaw to your MCP client
Create a workspace API key in the dashboard, then register the server. Requires Node.js 20+ and socialclaw 0.1.14 or later.
Hosted endpoint (no install)
The same server runs hosted at https://getsocialclaw.com/mcp over streamable HTTP. Send your workspace API key as Authorization: Bearer sc_live_your_key. Tool discovery is open; tool calls require the key.
claude mcp add --transport http socialclaw https://getsocialclaw.com/mcp \
--header "Authorization: Bearer sc_live_your_key"
Claude Code (local stdio)
claude mcp add socialclaw \
--env SOCIALCLAW_API_KEY=sc_live_your_key \
-- npx -y socialclaw mcp
Claude Desktop, Cursor, and other JSON-configured clients
{
"mcpServers": {
"socialclaw": {
"command": "npx",
"args": ["-y", "socialclaw", "mcp"],
"env": {
"SOCIALCLAW_API_KEY": "sc_live_your_key"
}
}
}
}
Alternatively run npm install -g socialclaw and socialclaw login --api-key <key> once; the MCP server then reuses the saved credentials and the config needs no env block.
Available tools
The toolset mirrors the SocialClaw publishing workflow: discover accounts, upload media, validate, publish, inspect.
list_accounts
List connected social accounts, optionally filtered by provider.
account_capabilities
Publish rules per account: allowed media, text limits, publish readiness.
connect_account
Start connecting a new account; returns the OAuth authorize URL.
upload_asset
Upload a local image or video; returns a hosted media URL.
validate_schedule
Validate a schedule against provider rules before publishing.
preview_campaign
Preview how a campaign expands into concrete posts.
apply_schedule
Create a publishing run with idempotency-key deduplication.
publish_draft
Publish a previously created draft run.
list_posts
List posts with status, account, provider, and run filters.
get_post
Inspect one post's delivery state and provider identifiers.
post_attempts
Debug failed posts via per-attempt provider errors.
retry_post
Retry a failed post.
cancel_post
Cancel a scheduled post before it publishes.
run_status
Status summary for a publishing run.
get_analytics
Analytics snapshots for a post, account, or run.
workspace_usage
Workspace usage counters and plan entitlements.
workspace_health
Workspace and provider connection health.
SocialClaw MCP server FAQ
What is the SocialClaw MCP server?
It is a Model Context Protocol server built into the socialclaw npm package. It lets MCP clients such as Claude Code, Claude Desktop, and Cursor publish to connected social accounts through the SocialClaw workspace: list accounts, upload media, validate schedules, publish posts, and inspect delivery.
How does authentication work?
Both transports authenticate with a workspace API key. For the hosted endpoint, send Authorization: Bearer <key> with each request. For the local stdio server, set the SOCIALCLAW_API_KEY environment variable in your MCP client configuration, or run socialclaw login --api-key <key> once and the server reuses the saved credentials.
Is there a hosted MCP endpoint?
Yes. https://getsocialclaw.com/mcp speaks streamable HTTP: POST JSON-RPC messages with your workspace API key as a bearer token. Tool discovery (initialize, tools/list) is open so MCP directories and clients can inspect the toolset without credentials.
Which platforms can an MCP client post to?
X, LinkedIn profiles and pages, Instagram professional accounts, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, and Pinterest, using the accounts connected in your SocialClaw workspace.
Does the agent post blindly?
No. The toolset is validation-first: validate_schedule checks provider rules, media limits, and account state before apply_schedule creates anything, and draft runs can be previewed and published separately for human-in-the-loop workflows.