← All integrations

PostOnce MCP server

25 operations0 webhooks

Publish and schedule posts with text and media to LinkedIn, X, Threads, Bluesky, Facebook Pages, Instagram, TikTok, YouTube and Pinterest, keep drafts, upload media, read post analytics and manage cross-posting workflows and webhooks.

Try PostOnce with your agent

Connect PostOnce, 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 PostOnce on my account, then run one read-only example and show me the result.

Runs once, when you ask

PostOnce tools and triggers

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

Posts

  • CancelDestructive

    Cancel a scheduled or still-pending post. The post record is kept with status cancelled; content already published on a network stays live.

    posts.cancel

  • CreateDestructive

    Create one post for one or more connected accounts, with text and media URLs. Without publish_at it publishes immediately and cannot be recalled once live; with publish_at it is scheduled. An idempotencyKey makes a retry return the original post.

    posts.create

  • GetRead-only

    Get one post with its per-account delivery state: status, platform post URL and any platform error.

    posts.get

  • Get AnalyticsRead-only

    Views, likes, comments, shares and saves for each published copy of one post (TikTok, Instagram, YouTube and Facebook). Cached for up to an hour.

    posts.getAnalytics

  • ListRead-only

    List the profile's posts, newest first, including dashboard and workflow posts. Page with after = meta.next_cursor.

    posts.list

  • PublishDestructive

    Publish a scheduled post right now. It goes live on every target and cannot be recalled.

    posts.publish

  • Retry TargetDestructive

    Retry one failed destination of a post (targetId from the post's targets). Published destinations are not posted again.

    posts.retryTarget

  • UpdateWrite

    Change a scheduled post before it runs: text, accounts, media or publish time. Only the fields sent change.

    posts.update

Workflows

  • CreateDestructive

    Create a cross-posting workflow. While active, PostOnce publishes every new post from the source account to the target accounts automatically.

    workflows.create

  • DeleteDestructive

    Delete a cross-posting workflow and its queued items.

    workflows.delete

  • GetRead-only

    Get one cross-posting workflow.

    workflows.get

  • ListRead-only

    List cross-posting workflows: each copies new posts from a source account to target accounts.

    workflows.list

Connect PostOnce to Claude, ChatGPT or Cursor

  1. 1

    Connect PostOnce in Corsair

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

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs PostOnce. On a ChatGPT personal plan, connect PostOnce 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, PostOnce's read and write operations run right away and its 8 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/postonce, add the PostOnce plugin, and connect with an API key. Then call methods like corsair.postonce.api.accounts.list() from your app. Corsair syncs data per tenant.

Yes. PostOnce requires an API key from your PostOnce 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 PostOnce, GitHub, Notion, Stripe, and the rest. Trigger PostOnce from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for publish and schedule posts with text and media to LinkedIn, X, Threads, Bluesky, Facebook Pages, Instagram, TikTok, YouTube and Pinterest, keep drafts, upload media, read post analytics and manage cross-posting workflows and webhooks. Common builds include sync jobs, admin tooling, and agents that call PostOnce APIs from your backend. Local DB entities let you query synced PostOnce records without hitting the API on every read.

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 PostOnce 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/postonce in the open repo. When PostOnce 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 PostOnce data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store PostOnce 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 PostOnce 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 8 destructive PostOnce operations. You can change a link's mode at hub.corsair.dev/me.