REST versus MCP

Choose REST or MCP and keep authentication, request nesting, polling, and capability differences separate.

Both interfaces use your Blotato account and subscription. Choose the interface your assistant or automation uses.

	MCP	REST API
Use from	An assistant with MCP tools	HTTP code, n8n, Make, or other workflow tools
Connect to	https://mcp.blotato.com/mcp	https://backend.blotato.com/v2
Authenticate	OAuth or an API key, depending on the client	blotato-api-key header
Publish input	Tool arguments such as accountId, platform, text, and mediaUrls	A JSON body containing post.accountId, post.content, and post.target
Account lookup	blotato_list_accounts includes subaccounts	Fetch accounts, then fetch subaccounts when needed
Immediate post and source completion	Tools wait internally for up to 20 seconds, then return the available result	Submit, save the returned ID, and poll the status endpoint
Visual generation	Not supported at this time	Create with POST /v2/videos/from-templates, then poll the visual status endpoint
Reference	MCP tools	OpenAPI

MCP tools expose a selected set of workflows. An endpoint in OpenAPI does not imply a corresponding MCP tool. For example, REST includes schedule-slot management and a webhook publishing target. MCP manages scheduled posts and publishes to the 9 listed social platforms, but does not expose these 2 REST capabilities.

Choose your setup

1. If your assistant already has blotato_ tools, call those tools directly using their schemas.

2. If you are adding Blotato to an assistant, follow MCP setup.

3. If you are building HTTP requests, follow the REST quickstart.

4. If you use workflow software, follow the n8n or Make guide.

Keep the 2 request shapes separate. Copying a REST post object into an MCP tool call fails when the tool expects flat arguments.