OneUp API + MCP vs Postiz API + MCP

OneUp API + MCP

API and MCP on every plan from $25 a month ($15 billed yearly). API key in the query string on REST and in the MCP URL, with no scopes.

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.

OneUp API + MCP

1. Call listcategory, then listcategoryaccount, then schedule. Pass social_network_id as ALL to post to every account in a category
2. Keep the ?apiKey= URLs out of logs and shared configs, and regenerate the key on the API Access page if one leaks
3. Set requireApproval or isDraftPost true when a person should review before anything goes out
4. Page through lists with start, 50 posts at a time
5. Give dates as YYYY-MM-DD HH:MM with no timezone field, so confirm the account timezone first

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