Mixpost API + MCP vs Publer 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.

Publer API + MCP

Scoped API keys (workspaces, accounts, posts, media, analytics) with 401 and 403 errors that name the missing scope or header. API and MCP only on Business and Enterprise, and the free plan has no API.

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

Publer API + MCP

1. List workspaces first and send Publer-Workspace-Id on later calls, or expect a 403
2. Poll /job_status/{job_id} after posts/schedule and read payload.failures, since status reads complete even when posts failed
3. Use the Bearer-API scheme, not Bearer
4. Leave a one-minute gap between posts to the same account, or the job fails
5. Read X-RateLimit-Reset after a 429 and wait until then, as there's no Retry-After