Postiz API + MCP vs Publer API + MCP

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.

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.

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

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