Documentation Index

Fetch the complete documentation index at: https://docs.woopsocial.com/llms.txt

Use this file to discover all available pages before exploring further.

​

WoopSocial MCP

WoopSocial exposes a Model Context Protocol (MCP) server so AI assistants and autonomous agents can manage social content with structured tools instead of ad hoc HTTP calls.

​

Endpoint

This endpoint implements OAuth, so your MCP client will ask you to log into your WoopSocial account to establish the connection.

​

What the server does

The WoopSocial MCP server mirrors the same core capabilities as our API:

• Projects - manage your organization’s projects.
• Social Accounts - list connected social accounts and their platform-specific options.
• Posts - create, list, read, validate, and delete scheduled content.
• Media - upload files and manage media attached to posts.
• Webhooks - register delivery callbacks for post events.
• Health - verify connectivity.

​

Relationship to the REST API

• Parity: MCP tools use the same backend logic as https://api.woopsocial.com/v1.
• Choose MCP when you want your AI agent to talk to WoopSocial.
• Choose API for servers, webhooks, apps.

​

API key-based authentication fallback

WoopSocial implements OAuth for authenticating clients, so the https://api.woopsocial.com/mcp endpoint should just work. However, if your MCP client can’t connect to this URL, it’s possible to authenticate using API keys as a fallback mechanism. Create your API key in WoopSocial dashboard -> API. MCP uses the same API key and permissions as the REST API.

​

Next steps