Postiz

Postiz schedules and publishes to more than thirty social networks, with a visual calendar for review and editing, and AI generation for drafting. What separates it from the established schedulers is the surface it exposes: an MCP server, a CLI, a public API with OAuth2 and an SDK, and native hooks into n8n, Make and Zapier. It is open source and can be self-hosted.

That combination changes what the tool is for. Conventional schedulers are destinations — a human logs in, plans a calendar, and clicks publish. Postiz can be treated as infrastructure that an agent operates, with Claude or another assistant drafting and scheduling through the MCP server while the calendar remains the human review layer. For a team already running AI content workflows, this closes the last manual gap between a generated post and a published one, without surrendering oversight.

The self-hosting option carries the usual bargain: no per-seat ceiling and full data control, in exchange for operating it yourself. Two cautions apply regardless of how you deploy it. Social platform APIs change constantly and every scheduler inherits that fragility, so verify coverage for the specific networks that matter to you rather than trusting a headline count. And the easier publishing becomes, the more important the review step gets — an agent that can post to thirty networks unattended is a brand risk if nobody is reading the calendar. Keep the human gate that the visual calendar is there to provide.