MCP (Model Context Protocol) lets AI agents interact with Postiz directly — listing integrations, scheduling posts, generating images and videos — all through a standardized tool-calling interface. This means you can connect Claude, ChatGPT, Cursor, or any MCP-compatible client to your Postiz account and manage your social media through natural language.Documentation Index
Fetch the complete documentation index at: https://docs.postiz.com/llms.txt
Use this file to discover all available pages before exploring further.
How It Works
Postiz exposes an MCP server that provides 8 tools to AI agents. The agent discovers these tools, understands their schemas, and calls them on your behalf.Available Tools
| Tool | Description |
|---|---|
integrationList | List all connected social media accounts |
integrationSchema | Get platform-specific posting rules and settings schema |
triggerTool | Execute platform-specific helpers (e.g., list Discord channels) |
schedulePostTool | Schedule, draft, or immediately publish posts |
generateImageTool | Generate AI images for posts |
generateVideoOptions | List available video generation options |
videoFunctionTool | Get video generator settings (e.g., available voices) |
generateVideoTool | Generate videos for posts |
Authentication
There are two ways to authenticate with the MCP server:API Key
Get your API key from Settings > Developers > Public API in Postiz. Use it directly in the MCP endpoint URL or as a Bearer token.OAuth Token
If you’re building an app for other Postiz users, use OAuth2 to obtain tokens. OAuth tokens start withpos_ and work the same way as API keys.
Connecting
- Bearer Token
- API Key in URL
Use the This method supports both API keys and OAuth tokens (prefixed with
/mcp endpoint with your API key or OAuth token as a Bearer token:pos_).For self-hosted instances, replace
https://api.postiz.com with your NEXT_PUBLIC_BACKEND_URL.Quick Example
Here’s what a typical interaction looks like when an AI agent uses Postiz MCP:- Agent calls
integrationList— gets back your connected accounts (X, LinkedIn, etc.) - Agent calls
integrationSchemawithplatform: "x"— learns X’s character limits, settings, and rules - Agent calls
schedulePostTool— schedules your post with the correct format
“Schedule a post to X for tomorrow at 10am: Excited to announce our new feature!”
FAQ
Do I need an OpenAI key to use Postiz MCP?
No. The MCP server just exposes Postiz’s tools — your AI client (Claude, ChatGPT, Cursor, etc.) provides the model. Postiz only needs anOPENAI_API_KEY if you use Postiz’s own AI features (image generation, copilot) which are separate from the MCP tools surfaced to your client.
What happens when my API key expires or is rotated?
Postiz API keys don’t auto-rotate, but if you regenerate one in Settings → Developers → Public API, every MCP client using the old key stops working until you update its config. Update the URL or theAuthorization header in your client config and reconnect.
Self-hosted: how do I expose the MCP endpoint?
The MCP server starts as part of the Postiz backend and is reachable at/mcp (Bearer auth), /mcp/:apiKey (key in URL), and /mcp-oauth (OAuth-protected). Your reverse proxy must forward these paths to the backend and support streaming HTTP (Transfer-Encoding: chunked). See Reverse Proxies.
Can MCP read or reply to comments?
Not today. The current tool set is read-only on integrations and write-only on posts/media — there’s nogetComments or replyToComment exposed via MCP. Comment replies must be triggered through the Postiz UI.