The tools mirror the whole API rather than a read-only slice, so an assistant can connect an account, upload the video and schedule the post without you opening the dashboard. The validate call is the one worth building a habit around: it checks a post against each platform's rules before anything exists.
A hosted server at https://api.woopsocial.com/mcp, over Streamable HTTP, that gives an assistant the same operations as the WoopSocial API: projects, connected social accounts, posts, media, webhooks and a health check.
- posts_create builds a parent post with one child post per social account; posts_validate checks the same post without creating anything
- posts_get, posts_delete, social_account_posts_list and social_account_posts_delete for reading and cleaning up what is already scheduled
- social_accounts_list returns the accounts cleared for publishing, and social_accounts_get_platform_inputs the options each platform accepts
- oauth_create_authorization returns the browser URL that connects a new social account to a project
- media_uploads_create_session handles files up to 5GB in parts; media_list and media_delete manage the library
- webhooks_create_endpoint registers a URL to receive the post events you name
A WoopSocial account. The endpoint implements OAuth, so the client sends you to log in; an API key is the fallback for clients that cannot complete that flow. Chunked uploads hand back presigned URLs on r2.cloudflarestorage.com, which some clients need added to their domain allowlist first.
One command plus a key — claude mcp add --transport http woopsocial "https://api.woopsocial.com/mcp?api_key=YOUR_API_KEY", then supply credentials