What social platforms are supported?
Facebook, Instagram, Pinterest, and LinkedIn are explicitly mentioned in the README.
W
Woopsocial MCP Server
@WoopSocial
基本情報
Woopsocial MCP Server について
Allow your AI Agents to directly post to the major social media platforms using this social media MCP by WoopSocial.
Woopsocial MCP Server の設定
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"woopsocial": {
"url": "https://api.woopsocial.com/mcp?api_key=wsk_0123456789abc"
}
}
}Woopsocial MCP Server のツール
25Returns a minimal response proving the WoopSocial API is reachable.
Deletes one media item by ID.
Returns media library items that belong to the API key's organization. When `projectId` is provided, only media in that project is returned.
Call this to finalize the upload started by calling [`/media/upload-sessions`](/api-reference/media/start-media-upload-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.
Get media upload session status
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. For Facebook, WoopSocial shows a page-selection screen after authorization because Facebook may return more pages than the user appeared to select in the Facebook dialog in cases where the user has authorized with WoopSocial previously. The selected pages are connected to the single `projectId` from this request, then WoopSocial redirects back to `redirectUrl` when one was provided. When `redirectUrl` is provided, WoopSocial appends these query parameters on success: - `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. When `redirectUrl` is provided, WoopSocial appends these query parameters on failure: - `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.
Creates a (parent) post with one or more social account (child) posts. 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.
Compatibility workaround for MCP clients that cannot load the full `posts_create` input schema. This is not a simplified input format and uses the same validation and behavior as `posts_create`. Prefer `posts_create` when available. To call this fallback: call `schema_describe` with `toolName: "posts_create_simple"`, construct an object matching the returned canonical schema, JSON-encode the entire object, and pass that string as `requestJson`. Do not pass canonical fields such as `content`, `schedule`, or `socialAccounts` directly to this tool.
Deletes one scheduled post by post ID. A post can only be deleted when all of its social account deliveries are still `NOT_STARTED`.
Returns one post with its social account posts inline.
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.
Compatibility workaround for MCP clients that cannot load the full `posts_validate` input schema. This is not a simplified input format and uses the same validation and behavior as `posts_validate`. Prefer `posts_validate` when available. To call this fallback: call `schema_describe` with `toolName: "posts_validate_simple"`, construct an object matching the returned canonical schema, JSON-encode the entire object, and pass that string as `requestJson`. Do not pass canonical fields such as `content`, `schedule`, or `socialAccounts` directly to this tool.
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.
Permanently deletes one project and its related data, including connected social accounts, OAuth grants, media references, and posts.
Returns projects that belong to the same organization as the API key. A project corresponds to a "Business Profile" in the UI.
Returns the canonical input schema. Use this before calling a tool when the expected arguments are unclear, when validation errors mention missing or invalid fields, or when a tool supports multiple modes, platforms, targets, schedules, content types, or other variants. This is especially useful for complex tools such as posts_create, where required fields and valid enum values depend on the selected target. If jsonPointer is provided, returns only that sub-schema. If toolName is omitted, returns the available tool names and summaries.
Deletes one social account post by ID.
Returns standalone social account posts for the API key's organization. Each item includes the content, schedule, delivery status and latest stored analytics for a given social account target.
Deletes one social account connection by ID. This removes the associated OAuth grant, including stored access and refresh tokens, so the account no longer counts toward the organization's active connected-account allowance.
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`.
Returns social accounts that can currently be used for publishing. When `projectId` is provided, only social accounts usable within that project are returned.
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>`
Delete webhook endpoint
Returns all registered webhook endpoints for the organization. The `signingSecret` field is omitted.
概要
What is Woopsocial?
Woopsocial is a social media MCP server that enables AI agents (e.g., Claude, ChatGPT) to create and automatically post content to multiple platforms through a single unified API. It provides platform-specific metadata so agents can format posts correctly.
How to use Woopsocial?
Install and configure the Woopsocial MCP server. You can then instruct your AI agent to post content—for example, “Post this image with this text on my Facebook, Instagram, Pinterest and LinkedIn”—and the MCP will use the correct endpoints to push the content to all requested platforms.
Key features of Woopsocial
- Posts to multiple social channels via one endpoint.
- Provides metadata for all supported platforms.
- Works with AI agents like Claude and ChatGPT.
- Automatic posting – no manual copy-paste.
- Supports Facebook, Instagram, Pinterest, and LinkedIn.
Use cases of Woopsocial
- An AI assistant publishes a promotional image and caption across Facebook, Instagram, Pinterest, and LinkedIn in one command.
- A content creator schedules multi-platform posts without leaving their AI chat interface.
- A marketing team automates social media updates from an internal AI agent using natural language.
よくある質問
Does Woopsocial actually post the content or just generate it?
It posts the content automatically using the unified social media API – not just generate drafts.
Do I need a separate account for each platform?
No. Woopsocial uses a single unified API endpoint that handles posting to all connected channels.
How do I tell my AI agent to post?
Use natural language commands like “Post this image with [text] on my Facebook, Instagram, Pinterest and LinkedIn.”
Does Woopsocial work with any AI assistant?
The README specifically mentions it works with AI agents like Claude and ChatGPT.
「その他」の他のコンテンツ
Klarix Intelligence Engine
KlarixB2B competitive intelligence, live sales battlecards, 5-axis ICP prospect fit scoring, and tech stack teardowns over MCP and REST with cited public-web evidence.
YOUB
Connect your AI assistant to your own YOUB endurance training account. Read recorded activities with full analysis, planned sessions, race goals, wellness (HRV, sleep, resting HR) and your athletic profile. Create or mov
Maestro
mobile-dev-incPainless E2E Automation for Mobile and Web
14.8K
Volley.sh
VolleyA good sequence diagram can solve almost any communication problem in engineering. Volley lets your agent write them as plain text, with the real request and response payloads on every arrow. It checks its own syntax wi
Reactive Resume
amruthpillaiA one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!
39.5K
コメント