Blotato vs Buffer 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.

Buffer API + MCP

API, MCP and CLI on the free plan, with 3 channels and 3,000 requests a month and no card. 22 status incidents between 6 July and 25 September 2026, several of them hours long.

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

Buffer API + MCP

1. Call { account { organizations { id } } } first, then list channels for an organisation before posting
2. Include ... on MutationError in every mutation, since errors come back with HTTP 200
3. On 429, wait Retry-After plus a few seconds of jitter. The 429 itself doesn't cost quota
4. Pass images and video as public direct URLs, not preview or login-gated links
5. Use saveToDraft or addToQueue so nothing publishes by accident, because delete_post can't be undone