WoopSocial Social Media MCP MCP server
Post to social media (Facebook, Instagram, LinkedIn, Pinterest, YouTube, TikTok, X/Twitter and more).
verified publishersource repositorytool list publishedhosted endpointactive entryno credentials1 stars
Hosted VERIFIED Other
Details
- Registry name
- com.woopsocial/mcp
- Publisher
- woopsocial
- Version
- 1.0.8
- Distribution
- Hosted. the publisher runs this server and your client connects to their URL over HTTP. Nothing to install, but your requests go to a third party.
- Transports
- streamable-http
- Source repository
- WoopSocial/mcp
- First published
- Registry updated
- Credentials required
- -
- Schema generation
- 2025-12-11
Hosted endpoints
Endpoint 1
- URL
- https://api.woopsocial.com/mcp
- Transport
- streamable-http
- Authentication
- api-key
Install WoopSocial Social Media MCP
Pick your client. The configuration below is generated from this server's published package and endpoint data.
Claude Code command line
Configuration file: .mcp.json or ~/.claude.json
claude mcp add mcp-woopsocial --transport http https://api.woopsocial.com/mcpNothing to install. The client connects to the publisher's URL.
Check it worked: Run claude mcp list and check the server reports connected.
Cursor IDE
Configuration file: .cursor/mcp.json or ~/.cursor/mcp.json
{
"mcpServers": {
"mcp-woopsocial": {
"type": "http",
"url": "https://api.woopsocial.com/mcp"
}
}
}Nothing to install. The client connects to the publisher's URL.
Check it worked: The server appears under Settings, then MCP with a green dot.
Claude Desktop desktop app
Configuration file: ~/Library/Application Support/Claude/claude_desktop_config.json or %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"mcp-woopsocial": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.woopsocial.com/mcp"]
}
}
}Nothing to install. The client connects to the publisher's URL.
Quit the app completely and reopen it.
Check it worked: Look for the tools icon in the message composer.
Visual Studio Code IDE
Configuration file: .vscode/mcp.json or user settings.json under mcp
{
"servers": {
"mcp-woopsocial": {
"type": "http",
"url": "https://api.woopsocial.com/mcp"
}
}
}Nothing to install. The client connects to the publisher's URL.
Check it worked: Open the Copilot chat tools picker and confirm the server is listed.
Codex CLI command line
Configuration file: ~/.codex/config.toml
codex mcp add mcp-woopsocial --transport http https://api.woopsocial.com/mcpNothing to install. The client connects to the publisher's URL.
Check it worked: Run codex mcp list and check the server is present.
More clients (9), including automation platforms
ChatGPT web app
This client does not support the transport this server offers.
Cline IDE
Configuration file: cline_mcp_settings.json, reachable from the MCP Servers pane
{
"mcpServers": {
"mcp-woopsocial": {
"type": "streamableHttp",
"url": "https://api.woopsocial.com/mcp"
}
}
}Nothing to install. The client connects to the publisher's URL.
Check it worked: The server appears in the MCP Servers pane with its tool count.
Goose desktop app
Configuration file: ~/.config/goose/config.yaml
extensions:
mcp-woopsocial:
type: streamable_http
uri: https://api.woopsocial.com/mcp
enabled: trueNothing to install. The client connects to the publisher's URL.
Check it worked: Run goose session and confirm the extension loads.
LangChain agent framework
Install the MCP adapter package and construct a client in code
client = MultiServerMCPClient({
"mcp-woopsocial": {
"url": "https://api.woopsocial.com/mcp",
"transport": "streamable_http",
}
})Nothing to install. The client connects to the publisher's URL.
Check it worked: Print the loaded tool list before running the agent.
Make automation platform
This client does not support the transport this server offers.
n8n automation platform
This client does not support the transport this server offers.
Windsurf IDE
Configuration file: ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"mcp-woopsocial": {
"serverUrl": "https://api.woopsocial.com/mcp"
}
}
}Nothing to install. The client connects to the publisher's URL.
Check it worked: The server appears in the Cascade plugin list.
Zapier automation platform
This client does not support the transport this server offers.
Zed IDE
This client does not support the transport this server offers.
Tools
18 tools, from the publisher's manifest. A parameter marked with an asterisk is required. By intent: 9 answer and 9 act.
Intent says what a tool does with the world. Answer reads and returns information and changes nothing. Act changes state somewhere, by writing, creating, sending or deleting. Transact moves money, buys something or commits to a cost. A value marked declared is the publisher's own annotation on their own tool. A value marked inferred is this catalogue reading the tool name and description, and is not a claim by the publisher. Where neither settles it, the tool is left unclassified rather than guessed at.
| Tool | What it does | Intent | Parameters |
|---|---|---|---|
| health_get | Returns a minimal response proving the WoopSocial API is reachable. | answer inferred | none |
| media_uploads_complete_session | Call this to finalize the upload started by calling [`/media/upload-sessions`](/api-reference/media/start-media-upload-session). | act inferred | uploadSessionId |
| 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. | act inferred | projectId, fileSizeInBytes |
| media_uploads_get_session | Get media upload session status | answer inferred | uploadSessionId |
| 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. | act inferred | platform, projectId, redirectUrl |
| 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. | act inferred | content, schedule, socialAccounts |
| 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`. | act inferred | postId |
| posts_get | Returns one post with its social account posts inline. | answer inferred | postId |
| 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. | answer inferred | content, schedule, socialAccounts |
| 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. | act inferred | name |
| projects_delete | Permanently deletes one project and its related data, including connected social accounts, OAuth grants, media references, and posts. | act inferred | projectId |
| projects_list | Returns projects that belong to the same organization as the API key. A project corresponds to a "Business Profile" in the UI. | answer inferred | none |
| 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. | answer inferred | limit, cursor, postId, platform, projectId, deliveryStatus, socialAccountId |
| 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`. | answer inferred | socialAccountId |
| 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. | answer inferred | projectId |
| 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>` | act inferred | url, eventTypes |
| webhooks_delete_endpoint | Delete webhook endpoint | act inferred | webhookId |
| webhooks_list_endpoints | Returns all registered webhook endpoints for the organization. The `signingSecret` field is omitted. | answer inferred | none |
Command line alternative
Could not determine. The available signals were not conclusive enough to say either way, so this is left open rather than guessed.
Repository
Read from github on 2026-08-06.
- Stars
- 1
- Forks
- 0
- Open issues
- 0
- Primary language
- not detected
- Licence
- not declared by the publisher
- Last commit
- 2026-04-28
- Latest release
- no tagged release
- Created
- 2026-04-26
- Repository files
- readme
Security, privacy and enterprise use
The publisher's website links no privacy policy, terms, security page or enterprise information that could be found automatically. It may still exist somewhere less obvious on their site.
Publisher
- Website
- docs.woopsocial.com
- Profiles
- none listed on the publisher's site
- Community
- no subreddit linked from the publisher's site
Review platforms
Ratings are not shown. G2, Trustpilot and Capterra all prohibit republishing their scores without a licence, and marking up a borrowed rating as our own would breach search engine policy. These are profile links only, and a profile may not exist for every publisher.
Frequently asked questions
- What does the WoopSocial Social Media MCP MCP server do?
- Post to social media (Facebook, Instagram, LinkedIn, Pinterest, YouTube, TikTok, X/Twitter and more).
- Do I need to install anything to use WoopSocial Social Media MCP?
- No. WoopSocial Social Media MCP is published as a hosted endpoint, so a compatible client connects to it over the network.
- How do I install WoopSocial Social Media MCP?
- Point your client at the hosted endpoint https://api.woopsocial.com/mcp. No local install is needed.
- Which transport does WoopSocial Social Media MCP use?
- Streamable http. Your client has to support that transport to connect.
- Where is the source code for WoopSocial Social Media MCP?
- The publisher lists https://github.com/WoopSocial/mcp as the source repository.
- Is WoopSocial Social Media MCP an official server?
- It is published under the namespace com.woopsocial, which means the publisher proved control of that domain when registering. That confirms who published it, not that it has been reviewed for quality or security.
- Which version of WoopSocial Social Media MCP is listed here?
- Version 1.0.8, taken from the latest registry entry.
Other servers in Other
航班管家航空数据 MCP | Flight Master Aviation Data MCP
航班管家 DAST 官方航空数据 MCP,支持 Remote HTTP 与 npm STDIO,提供航班动态、天气、轨迹及延误风险。Official Flight Master MCP.Kin
The system of record for AI-written software.Inite Diagnostic
Takes a business process apart and says what to automate first. Eight questions free, 43 paid.ApyHub Utility Tools (EU)
GDPR-compliant ApyHub utility APIs hosted in the EU. Requires an EU-generated ApyHub API key.Federal Grant Evidence
Find U.S. federal grants and return cited hard-gate and award-history evidence packs.SAP ABAP MCP
Develop, test, analyze, and operate SAP ABAP systems through ADT from AI coding agents.Crossave import duty & VAT
EU import duty & VAT calculator (rules since 1 July 2026), real shop origins and shipping rates.ToolsMonk tool catalog
Find the right ToolsMonk tool for a task: 255 free browser-based tools, read-only lookups.