Instructions today · no local connection
Not as a local one that Postdom supports. Postdom ships a local stdio MCP server, and the clients it documents and has tested for that path are Claude Code, Codex and Cursor; ChatGPT is not one of them, so a ChatGPT MCP server connection here would be the remote kind. Postdom's hosted endpoint is live, but the ChatGPT connector flow has not been exercised, so this page does not claim it works. What does work today is the operating brief in Project instructions — instructions, not a connection. Publishing to TikTok, Instagram Reels, YouTube Shorts, LinkedIn, Facebook Reels, X, Snapchat Spotlight, Threads and Bluesky still runs through a client Postdom has connected.
Two things are true at the same time, and they are worth keeping apart.
Works today · instructions only
The brief is text. Adding it to Project instructions gives ChatGPT Postdom's operating rules — what to check before proposing a post, what a workflow state does and does not mean, and when to stop and ask a human. It connects nothing and calls nothing, and that is the whole of what it does.
Pending verification · remote connector
Live tools need a supported remote MCP connection. Postdom's hosted endpoint is live and answers an unauthenticated request with a correct authorization challenge, publishing the discovery documents an OAuth client follows. What has not been exercised is the ChatGPT side: creating the connector, granting consent, and seeing all 13 tools appear. Until that is done this page does not claim it works.
Endpoint: https://api.postdom.com/mcp
This is the mistake worth naming explicitly, because the block looks like something you connect with. It is a description of a process for a client to launch, and that launching is the part Postdom has not verified for ChatGPT. ChatGPT MCP connector documentation covers what a remote connector requires.
Paste the operating brief into Project instructions. That gives ChatGPT the rules Postdom expects an agent to follow: check workspace state before proposing anything, treat a workflow state as a state rather than a result, and stop when consent, audience or approval is unresolved.
The configuration shown in Postdom Accounts describes a local process for a client to start. Postdom has not verified that path for ChatGPT, so pasting the block is not a supported way to connect, and it puts a workspace key into a conversation. If you have already pasted a key anywhere, revoke it in Postdom Accounts and create a new one.
Claude Code, Codex and Cursor are the clients Postdom documents and has tested for the local path, and each exposes the full tool set. If the work needs Postdom to actually read state or submit a plan, run it in one of those and keep ChatGPT for drafting and reasoning.
Nothing about the brief changes who approves. The human owns credentials, connected accounts, policy, consent, audience and disclosures. An agent cannot approve its own plan or widen its authority, whichever client it runs in.
These are the clients Postdom documents and has tested for the local path, and each exposes the full tool set. The operating brief is the same text in every client including ChatGPT, so drafting in one and running in another costs nothing to move between.
Postdom publishes supplied finished video to these destinations. It does not generate video, add networks it has not shipped, or make every feature inside a destination available.
These hold wherever the call is made from, so they are worth reading before you wire anything to a client that can make one.
An accepted or requires_approval response is not provider publication. A scheduled state is not publication either. Keep the returned post ID and read that same post through to a terminal per-destination outcome before you call it published.
A failed or partial state does not prove a destination never published, so it is not a licence to retry automatically. Reconcile each destination first; retrying a request where one destination already succeeded is how duplicates get made.
When a platform does not report a value, Postdom keeps it unavailable with its reason attached and leaves it out of aggregates. null is not zero, and treating it as zero silently understates everything it touches.
The human owns credentials, connected accounts, policy, consent, audience and disclosures. Approval is enforced on the exact version and request that will be sent, and a drafting assistant with no connection cannot change that either way.
Not as a local one Postdom supports, and the remote route is not verified. The published @postdom/mcp@0.3.0 package is a local stdio server that a client starts on your machine, and Postdom has tested that path for Claude Code, Codex and Cursor rather than ChatGPT. The remote path is the one Postdom would support here, and while its hosted endpoint is live and answers correctly, the connector flow itself has not been exercised end to end.
Nothing Postdom supports. The block describes a local process for a client to start, and Postdom has not verified that path for ChatGPT. The real cost is that a workspace key ends up in a conversation. Revoke it in Postdom Accounts and create a new one if that has happened; Postdom shows a key once, so it belongs in a config file rather than a chat.
Rules, not reach. ChatGPT can use it to draft a plan in Postdom's vocabulary, name the destinations and settings a human would need to approve, and say what evidence it would want before calling something published. It cannot read your workspace or send anything, because it has no connection.
Claude Code, Codex or Cursor. Each starts the local server and exposes all 13 tools, and those are the three Postdom has tested for that path. The operating brief is the same text in all of them, so moving between them costs nothing.
No, and this matters wherever the call comes from. accepted, requires_approval and scheduled are workflow states, not provider publication. Keep the returned Postdom post ID and read that same post through to a terminal per-destination outcome before treating any destination as published.
They stay unavailable, with the reason attached. Postdom does not substitute a zero for a missing observation: null is not zero, and an unavailable metric is excluded from aggregates rather than quietly dragging them down.