Postiz MCP: How to Schedule Social Posts with AI

Postiz MCP lets you ask Claude, ChatGPT, or Cursor to schedule social media posts in plain English. No API keys to paste into chat. No switching between tabs. You tell your AI agent what to post, to which platforms, and when. The agent handles the rest across 30+ channels: X, LinkedIn, Instagram, TikTok, Reddit, YouTube, and more. That is the whole idea.

What Is MCP and Why Postiz Built It

Model Context Protocol (MCP) is an open standard from Anthropic that lets AI models interact with external tools and data sources. Think of it as a controlled way for Claude (or ChatGPT, or any AI) to actually DO things in the real world, not just talk about them.

Before MCP, if you wanted an AI agent to schedule a social post, you had two options: (1) give it your API credentials and hope it uses them correctly, or (2) have it draft text and you manually copy it into Postiz. Both are friction.

MCP solves that. The AI agent gets a sandbox of specific actions it can take, with strict permission boundaries. Postiz MCP exposes a handful of tools: schedule a post, list your channels, check draft history, read basic analytics. The agent can only use those tools. It cannot access your password, delete your account, or post to networks you did not connect.

For you, the upside is obvious: you type one request in Claude and 30 seconds later your post is scheduled across five platforms, ready for you to review and publish. No API debugging. No manual copy-paste. No hiring someone to build a custom integration.

Postiz built MCP because it is the technical future of social scheduling. AI agents are only useful if they can actually affect the world. MCP is the safe, standard way to let them.

How to Set Up Postiz MCP in 3 Steps

Setting up MCP takes less than five minutes.

First, log in to Postiz and go to your MCP settings. Copy the MCP server URL (it looks like https://your-instance.postiz.com/mcp). If you are running Postiz Cloud, Postiz provides this URL directly. If you are running Postiz self-hosted, you need to have it set up on a server with HTTPS.

Second, open Claude, ChatGPT, Cursor, or whichever AI client you use. Navigate to the app's settings or integrations panel and look for the option to add a custom tool or protocol. Paste the Postiz MCP URL. The AI client will validate the URL and connect. You may see a brief loading screen as the client fetches the available Postiz MCP tools.

Third, sign in with OAuth. The AI client will prompt you to authenticate with Postiz using your existing login. You are not giving the AI your password; OAuth ensures the agent gets only the permission it needs (scheduling and drafting). Approve it. You are done.

At this point, type something like: "Schedule a post on LinkedIn about remote work culture for tomorrow at 9am." The AI will ask you a couple of follow-up questions (tone, any hashtags, etc.), then confirm the post in your Postiz queue. You review it in the Postiz UI and publish when ready.

Connecting Postiz MCP to Each AI Agent

The setup process is nearly identical across all AI clients, but the UI differs slightly. Here is the step-by-step for the major ones.

Claude (web): Go to claude.ai. Click your username, then Settings > Connected apps. Paste the Postiz MCP server URL under "Custom MCP servers". Claude validates the connection and asks you to sign in via OAuth. Approve, and you are live.

ChatGPT (web): Open chatgpt.com. Click your profile > Settings > Beta features > Model Context Protocol. Toggle on. Paste the Postiz MCP URL. ChatGPT will fetch the available tools and show them in your chat history. The first time you ask ChatGPT to schedule a post, it will prompt you to authenticate via OAuth.

Cursor (IDE): If you use Cursor as your code editor, you can add Postiz MCP there too. Open Settings > Features > MCP Servers. Add a new server and paste the Postiz MCP URL. Sign in with OAuth. Now when you ask Cursor to "help me schedule a social media post", it can actually do it.

Codex (via GitHub Copilot): GitHub Copilot integrates MCP servers via a mcp_servers.json config file in your project. Add Postiz to the list. Authenticate once, and Copilot chat can schedule posts while you work.

Grok, Gemini, DeepSeek, OpenClaw, Hermes, and others: The process is the same: find the integrations or MCP settings, paste the URL, authenticate with OAuth, done. Postiz supports 15+ AI agents as of late 2026.

Pro tip: If you use multiple AI agents, add Postiz MCP to all of them. They each work with the same Postiz account, so every agent sees your channels, drafts, and scheduling history. Useful if you want Claude handling brainstorming and ChatGPT handling scheduling, or vice versa.

What Can Postiz MCP Actually Do?

Postiz MCP exposes a small, focused set of tools designed for scheduling and drafting. You do not get everything Postiz can do; you get a curated subset that makes sense for AI agents.

Schedule a post: Tell the agent what to post, which platforms, and when. The agent composes the text, picks the optimal time slot, and queues it for review. Postiz MCP does not auto-publish; you always see the post in your Postiz dashboard before it goes live.

List your channels: Ask the agent "which platforms am I connected to?" and it will return X, LinkedIn, Instagram, TikTok, Reddit, YouTube, Pinterest, Mastodon, Threads, and 20+ more (Postiz supports 30+ total). Useful for the agent to understand what is available before drafting.

Read draft history: The agent can check recent drafts you created, either via MCP or manually in Postiz. Helps it avoid redundant posts.

Basic analytics: The agent can pull engagement metrics: likes, comments, shares, followers gained in the last 7 days. Not detailed reporting (use the Postiz dashboard for that), but enough for the agent to understand what content resonates.

Upload media: Some AI clients allow Claude or ChatGPT to generate images on the fly. With MCP, the agent can attach generated images to your post.

Manage channel settings: The agent can toggle channel-specific options: "turn off LinkedIn auto-replies for today" or "set Instagram to draft-only mode". Useful for fine-grained control.

What the agent cannot do: change your password, delete your account, access other users' data, or bypass channel permissions. MCP enforces these boundaries at the protocol level.

Writing Prompts That Actually Work

The best prompts are specific about what, where, and when. Vague prompts produce vague results.

Good prompt: "Schedule a LinkedIn post for Tuesday at 10am about the challenges of async communication in distributed teams. Keep it professional but conversational, 150-200 words, include one relevant article link."

Weak prompt: "Post something about remote work."

The first one tells the agent: platform (LinkedIn), time (Tuesday 10am), topic (async communication), tone (professional but conversational), length (150-200 words), and includes guidance (link). The agent will draft a post that actually fits your brand.

Multi-platform posting: You can ask the agent to post to multiple platforms at once with variations. "Schedule a post about our new feature launch. For X, make it punchy and link to the launch thread. For LinkedIn, make it formal and link to the press release. For Instagram, make it visual and link to a demo video. Post all three tomorrow at 9am."

The agent will draft three separate posts, optimized for each platform's style and audience, all scheduled for the same time.

Media generation: If your AI client supports image generation (Claude, ChatGPT, Cursor do), you can ask it to generate a cover image, schedule a post with that image attached, all in one request. "Schedule a LinkedIn post about Q4 growth. Generate a simple blue-and-white chart graphic showing 25% YoY growth. Post tomorrow at 2pm."

Claude will generate the image, attach it, and queue the post.

Scheduling frequency: You can batch-schedule posts for an entire week or month. "Schedule four social media posts for next week: Monday about hiring, Tuesday about a product update, Wednesday about customer wins, Thursday about company culture. Vary the platforms: LinkedIn on Monday, X on Tuesday, Instagram on Wednesday, TikTok on Thursday."

The agent will draft all four and queue them.

Multi-Platform Posting and Batch Scheduling

One of the most powerful features of Postiz MCP is its ability to coordinate posts across multiple platforms in one request. This is where it saves the most time for growing teams.

Scenario: You are a SaaS founder with 15 minutes before a meeting. You want to announce a product launch to your audience on six platforms. Normally, this takes: drafting on X, adapting for LinkedIn, adapting for Instagram, uploading images, scheduling each one, updating your website. Total: 30-45 minutes.

With MCP: "I am launching a new feature called Smart Scheduling. Draft and schedule announcement posts for X (thread format), LinkedIn (article-style), Instagram (carousel with images), TikTok (video hook), Reddit (r/SaaS and r/ProductManagement), and email (via our newsletter integration). Post X and LinkedIn tomorrow at 9am, Instagram and TikTok tomorrow at 7pm, Reddit tomorrow at 6pm. Make each version match the platform's native format and audience expectations."

Claude will draft six variations, generate any needed images or video hooks, and queue them all. You review them in Postiz in five minutes and publish. Entire workflow: 20 minutes.

Brand consistency across platforms: One risk of batch scheduling is that tone and messaging drift across channels. MCP mitigates this by drafting each platform version from the same brief. The agent understands context: it knows that a LinkedIn post should be formal, an Instagram post should be visual, and a TikTok post should be casual. It enforces consistency at the brand level while adapting to platform norms.

Platform-specific capabilities: Postiz MCP is aware of platform limits: X has 280 characters, LinkedIn has no character limit, Instagram has caption character limits, TikTok is video-first. The agent respects these constraints automatically. You do not need to tell it; it knows.

Security, Authentication, and Best Practices

OAuth is the security backbone of Postiz MCP. Instead of giving Claude or ChatGPT your Postiz password, OAuth issues a scoped token that grants only the permission the agent needs: schedule posts, read drafts, upload media. The token cannot change your password, delete your account, or access other people's data.

Token management: Postiz issues MCP tokens with expiration dates (typically 90 days). When a token expires, you re-authenticate in your AI client and Postiz issues a fresh one. You cannot give a token an unlimited lifespan, and you should not paste tokens into prompts. Treat tokens like passwords: share them with AI agents only via secure channels (your AI client's integration UI, not chat).

Human in the loop: Postiz MCP never auto-publishes. Every post the agent schedules goes into your Postiz draft queue for review. You see it, edit it if needed, then manually publish. This is intentional. An AI agent should not post to your audience without your approval.

What NOT to do: Do not paste your Postiz API key directly into a ChatGPT prompt. Do not tell Claude "here is my password, schedule a post." Do not store tokens in environment variables that are visible in your code. Use MCP's OAuth flow; it is designed for this.

Audit trail: Every action taken by an MCP agent is logged in your Postiz account. You can see which agent scheduled which post, when, and what it said. Useful for compliance or if something goes wrong.

Running Postiz MCP on Managed Hosting

For most small teams, Postiz Cloud is simple enough. You pay a subscription, Postiz handles servers and updates, your MCP endpoint is ready to go.

But if you need more control, or if you are already running Postiz on your own infrastructure, you can run Postiz MCP on a managed Postiz instance. Opsily offers managed Postiz hosting: we run the Postiz server, handle backups and updates, and you get a dedicated MCP endpoint with HTTPS and OAuth already configured. Zero configuration required.

The benefits: Your MCP endpoint is always available and stable. Postiz instances on Opsily scale automatically as you add more scheduled posts. OAuth tokens are issued by a production-grade server. You do not have to manage SSL certificates, server patches, or database backups. Opsily does it.

Alternatively, if you prefer full control, you can self-host Postiz on your own server (AWS, DigitalOcean, Hetzner, etc.). You run the Postiz app yourself, configure HTTPS (required for MCP), set up OAuth clients for your AI agents, and manage backups and updates. This takes more work, but gives you complete data sovereignty.

For teams under 50 people, managed hosting is usually the right choice. It is cheaper than hiring someone to manage Postiz infrastructure, and faster than troubleshooting HTTPS and OAuth yourself.

For teams over 100 people, or if you have regulatory requirements (HIPAA, FedRAMP, PCI DSS), self-hosted Postiz on your own infrastructure might make sense.

Frequently Asked Questions

What is the difference between Postiz MCP, the CLI, and the API?

MCP is for AI agents: natural language scheduling via Claude, ChatGPT, Cursor, etc. The CLI is for developers: run postiz schedule --text "Hello" --platforms x,linkedin from your terminal. The API is for custom integrations: call REST endpoints to build your own UI or workflows. Use MCP when you want to talk to your AI agent. Use the CLI when you want to script scheduling. Use the API when you want to build a custom app.

Do I need an API key to use Postiz MCP?

No. MCP uses OAuth, not API keys. You sign in with your Postiz credentials once per device, and Postiz issues a scoped token. The AI agent uses that token, not a password or key. Much safer.

Can Postiz MCP generate images and videos?

Postiz MCP cannot generate media itself, but if your AI client supports image generation (Claude, ChatGPT, Cursor do), the agent can generate images and attach them to posts. Video generation depends on your AI client (ChatGPT Plus supports video generation, Claude does not). The MCP handles scheduling; the AI client handles media generation.

Is Postiz MCP available for all AI agents?

Postiz MCP is supported by 15+ AI agents as of late 2026: Claude, ChatGPT, Cursor, Codex, Grok, Gemini, DeepSeek, and others. If your AI client supports MCP (most do now), Postiz MCP will work. Check your client's documentation for MCP support.

What platforms can I post to through Postiz MCP?

30+ platforms: X, LinkedIn, Instagram, TikTok, Reddit, YouTube, Pinterest, Mastodon, Threads, Bluesky, Bereal, Lemmy, and 16+ more. Postiz adds new platforms regularly. Your AI agent can see the full list by asking "which platforms am I connected to?"

Can Postiz MCP post to private accounts or finsta?

Yes, as long as you have connected those accounts to Postiz and authenticated them via OAuth. Postiz sees all accounts you have authenticated, including private and business accounts. The agent can schedule to any of them.

What happens if the AI agent makes a mistake in a scheduled post?

Nothing is published until you approve it in Postiz. Every post the agent schedules goes into your draft queue. Review it, edit if needed, then publish. If it is terrible, delete it and try again.

The Bottom Line

Postiz MCP is a direct path from thought to published post across 30+ platforms. It works because it is specific: the AI agent can schedule posts, not rewrite your website. It is safe: OAuth and human review prevent accidents. It is fast: minutes instead of hours.

If you are already using Claude or ChatGPT daily, adding Postiz MCP takes five minutes. You get the same AI agent, plus the ability to schedule social media without leaving the chat. For founders and marketers drowning in context-switching, that alone is worth it.

Start with Postiz Cloud (simplest). If you need more control or scale, move to managed hosting on Opsily or self-hosted on your own infrastructure.