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

X MCP

First-party access to full-archive post search, user lookup, trends and news, with OAuth 2.0 PKCE scopes and per-resource prices published without a login. Every user must create a paid X developer app, the tool list isn't published, and the documented tools don't create posts.

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

X MCP

1. Use the app-only Bearer header for read-only work. Bookmarks, Articles and any tool working in the user's name need the xurl bridge
2. Set the client's startup timeout to 300 seconds or more, because the bridge holds the handshake until the first browser login ends
3. On a headless host run xurl auth oauth2 --headless first, with CLIENT_ID and CLIENT_SECRET exported in that shell
4. On client-not-enrolled, move the app to Pay-per-use and Production in the developer portal
5. On 429, wait until the Unix time in x-rate-limit-reset. No Retry-After header is documented