Blotato vs Postiz API + MCP

Blotato

One paid account gives an agent a REST API with a public OpenAPI document and an MCP server with 36 tools, with request limits and error codes documented in detail. No status page, changelog, security contact or free API access was found, and each account has a single key with full access.

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.

Blotato

1. Call blotato_list_accounts or GET /v2/users/me/accounts first, and fetch pageId or boardId before posting to a Facebook Page, LinkedIn company Page or Pinterest
2. Keep the postSubmissionId and poll the status until published, scheduled or failed. It is a receipt, not proof of publication
3. After a timeout on a create call, list existing posts before sending again, because there is no idempotency key
4. Do not generate an API key on a trial account unless the owner accepts the Starter charge
5. Keep REST bodies and MCP arguments apart. REST nests post.content and post.target, and the MCP tool takes flat arguments

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