← All integrations

Postiz MCP server

11 operations0 webhooks

Social media scheduling API for publishing, scheduling and managing posts across connected channels.

Try Postiz with your agent

Connect Postiz, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Postiz on my account, then run one read-only example and show me the result.

Runs once, when you ask

Postiz tools and triggers

Tools are what your agent can do in Postiz through Corsair's MCP server. Triggers are the Postiz events a routine can start from.

Posts

  • Change StatusDestructive

    Move a post between draft and scheduled. Scheduling queues it to publish at its stored date to every channel it targets

    posts.changeStatus

  • CreateDestructive

    Create a post as a draft, scheduled, or published immediately. A schedule or an immediate post goes out to every listed channel and cannot be recalled by this plugin once published

    posts.create

  • DeleteDestructive

    Delete a post, which also deletes every post in its group. A published post stays live on the platform

    posts.delete

  • ListRead-only

    List posts in a date window with their state, release URL and any platform error

    posts.list

Integrations

  • Find SlotRead-only

    Read a channel's next free posting slot

    integrations.findSlot

  • Is ConnectedRead-only

    Confirm the API key is valid and the workspace is reachable

    integrations.isConnected

  • ListRead-only

    List the connected channels, optionally narrowed to one customer group

    integrations.list

Media

  • ListRead-only

    Page through the organization's media library, optionally filtered by file name

    media.list

  • Upload From UrlWrite

    Copy a file from a public URL into the media library, for use as a post attachment

    media.uploadFromUrl

Analytics

  • PlatformRead-only

    Read one channel's analytics rows for a period

    analytics.platform

Notifications

  • ListRead-only

    Page through the organization notifications, newest first

    notifications.list

Connect Postiz to Claude, ChatGPT or Cursor

  1. 1

    Connect Postiz in Corsair

    Add your Postiz API key once in Corsair. Corsair stores the credential encrypted and makes the Postiz API calls for your agent, so it never goes into a prompt or a config file. Connect Postiz

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Postiz. On a ChatGPT personal plan, connect Postiz here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Postiz's read and write operations run right away and its 3 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/postiz, add the Postiz plugin, and connect with an API key. Then call methods like corsair.postiz.api.analytics.platform() from your app. Corsair keeps each tenant isolated.

Yes. Postiz requires an API key from your Postiz account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Postiz, GitHub, Notion, Stripe, and the rest. Trigger Postiz from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for social media scheduling API for publishing, scheduling and managing posts across connected channels. Common builds include sync jobs, admin tooling, and agents that call Postiz APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Postiz API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/postiz in the open repo. When Postiz ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Postiz data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Postiz data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Postiz on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 3 destructive Postiz operations. You can change a link's mode at hub.corsair.dev/me.