@ndesv21
基本情報
Social media scheduling MCP for AI agents posting to X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, and Pinterest.
以下の設定を使って、このサーバーを 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.
List media (images/videos) the user has uploaded to their SocialClaw library, newest first. Each asset includes a publicUrl usable directly as media_link in validate_schedule/apply_schedule. Use this to find a previously uploaded file (e.g. from the dashboard) to post. Optionally filter by kind (image/video), mime, or a text query over filename/id.
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.
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.
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.
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.
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.
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.
The server supports both stdio transport (via `npx`) and streamable HTTP transport (hosted at `https://getsocialclaw.com/mcp`).
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).
Connect an AI assistant to one Vocenya business account: list calls, leads, bookings and chats, add leads, queue compliant AI callbacks and update Do Not Call.https://github.com/gadyamedia/vocenya-mcp
Send, receive and track real faxes in the US and Canada from Claude, ChatGPT or Cursor.
Email inboxes for AI agents. Give an agent its own address in one call; it sends, receives and replies in threads, waits for a sign-up code and gets it back already extracted, and hands a conversation to a person when it
Body language for AI agents, on your terms. A consented three-second phone gesture gives your agent an Aligned or Unaligned signal with confidence. You remain the authority.
Official Mobile Text Alerts server. Send and schedule SMS, manage subscribers and groups, and complete carrier registration from any MCP-compatible AI assistant.
コメント