Mixpost API + MCP vs Postiz API + MCP

Mixpost API + MCP

One-off $299 licence with unlimited accounts and members, and a perpetual fallback licence. No API or MCP in the free Lite edition.

Postiz API + MCP

AGPL-3.0 and self-hostable with the API and MCP included, 34 platforms. Create-post capped at 90 requests an hour on every Cloud plan.

Mixpost API + MCP

1. Call list-workspaces first. Workspace endpoints sit under /api/{workspaceUuid}
2. Check MIXPOST_CORE_PATH. It's empty by default from Pro v7 but defaults to mixpost in older versions and Lite
3. Create the token as a Viewer-role user when the agent only needs to read
4. Use unschedule-post rather than delete-post when a person wants a post pulled back to draft
5. Expect HTTP 422 with an errors.limit entry when a Cloud plan limit is hit

Postiz API + MCP

1. Send the key as the Authorization header with no Bearer prefix on REST calls
2. Batch several posts into one create request to stay under 90 an hour
3. Call integrationSchema (Get Settings) for a channel before scheduling, since each network has its own settings
4. Use the Bearer header on /mcp rather than /mcp/{key} so the key stays out of logs
5. Read output.errors on a failed schedule call and retry with the corrected fields