WoopSocial Social Media MCP

Name: WoopSocial Social Media MCP
Author: woopsocial

Post to social media including Facebook, Instagram, LinkedIn, Pinterest, YouTube, TikTok, X/Twitter and more.

该来源不提供完整文件导出（国内平台多为平台内托管），仅存元数据与原链

接入信息

传输形态: http
鉴权方式: 鉴权未知
端点: https://woopsocial.run.tools

鉴权方式未标注，请核对官方文档后再接入——不要直接使用以下片段

{
  "mcpServers": {
    "WoopSocial Social Media MCP": {
      "url": "https://woopsocial.run.tools"
    }
  }
}

能力清单

工具	说明
health_get	Returns a minimal response proving the WoopSocial API is reachable.
media_uploads_complete_session	Call this to finalize the upload started by calling [`/media/upload-sessions`](/api-reference/media/start-media-upload-session).
media_uploads_create_session	This endpoint can be used to upload both smaller and larger files (up to 5GB) in a chunked manner. Calling this creates an upload session and returns presigned URLs for uploading the file in parts. Upload the file in `partCount` parts, using the matching `parts[n].uploadUrl` for each part number. Every part except the last must be exactly `partSizeInBytes` bytes. The last part may be smaller. After all parts have been uploaded, call `/media/upload-sessions/{uploadSessionId}/complete` to finalize the upload and create the media item.
media_uploads_get_session	Get media upload session status
oauth_create_authorization	Generates a browser authorization URL for connecting a new social account to a project. This endpoint is useful for multi-user integrations where your application lets your own users, clients, or brands connect their social accounts to WoopSocial without giving them access to your WoopSocial account. A common flow is: 1. Create or select a WoopSocial project for your user, client, or brand. 2. Call this endpoint from your backend with that `projectId`, the target `platform`, and a `redirectUrl` in your application. 3. Open the returned `url` in your user's browser. 4. After OAuth completes, WoopSocial redirects the browser back to `redirectUrl` with result query parameters. 5. Use `projectId` and `socialAccountIds` from the redirect, or call `GET /social-accounts?projectId=...`, to store or confirm the connected account in your application. When `redirectUrl` is provided, the browser is redirected back to that URL after the OAuth callback is handled. On success, WoopSocial appends these query parameters to `redirectUrl`: - `status=success` - `projectId`: the project identifier from the request - `platform`: the connected social platform - `socialAccountIds`: comma-separated connected social account identifiers. This may contain one or more IDs depending on the platform OAuth flow. On failure, WoopSocial appends these query parameters to `redirectUrl`: - `status=error` - `projectId`: the project identifier from the request - `platform`: the requested social platform - `error`: an OAuth callback error code If the OAuth callback state is missing or expired, WoopSocial cannot safely determine the original `redirectUrl`, so the callback returns an HTTP error instead of redirecting. The redirect never includes OAuth tokens or credentials.
posts_create	Creates a post with one or more social-account targets. All referenced social accounts must belong to the same project. The request is validated atomically. If any social-account fails validation, the post is not created.
posts_delete	Deletes one scheduled post by post ID. A post can only be deleted when all of its social-account deliveries are still `NOT_STARTED`.
posts_get	Returns one post with its social account posts inline.
posts_validate	Validates a post without creating one. This endpoint applies the same validation rules as `POST /posts`, including social-account resolution, platform-specific validation, and media validation for referenced media library items.
projects_create	Creates a project in the API key's organization. Use projects to isolate social accounts, media, and posts for a specific user, client, or brand in your application.
projects_delete	Permanently deletes one project and its related data, including connected social accounts, OAuth grants, media references, and posts.
projects_list	Returns projects that belong to the same organization as the API key. A project corresponds to a "Business Profile" in the UI.
social_account_posts_list	Returns standalone social account posts for the API key's organization. Each item includes the materialized content and schedule for that social-account target.
social_accounts_get_platform_inputs	Returns platform-specific input options for a connected social account. Use this endpoint to discover valid values for flattened post-target fields such as `pinterestBoardId` and `privacyLevel`.
social_accounts_list	Returns social accounts that can currently be used for publishing. When `projectId` is provided, only social accounts usable within that project are returned.
webhooks_create_endpoint	Registers a URL to receive webhook events for the specified event types. The response includes a `signingSecret` (base64-encoded, 32 bytes) that is returned once only. Use it to verify the `X-Woop-Signature` header on incoming webhook payloads. Signature format: `t=<unix>,v1=<hmac-sha256-hex>` Signed payload: `<unix>.<json-body>`
webhooks_delete_endpoint	Delete webhook endpoint
webhooks_list_endpoints	Returns all registered webhook endpoints for the organization. The `signingSecret` field is omitted.

纠错与举报（发现条目失效、署名有误或涉及侵权？）

提交举报 / 纠错

侵权举报经核验成立后，我们会即时下线该条目并删除已存的内容副本。