At the wheel
Behind the scenes · published Monday 1 September
| When | Views | Watch time |
|---|---|---|
| +1h | 310 | 31m |
| +6h | 980 | 1h 39m |
| +24h | 2,140 | 3h 33m |
| +72h | 3,600 | 5h 59m |
| +7d | 4,120 | 6h 54m |
Median for this account's product posts, same week620
Draft, schedule and publish with your AI agent. It learns from performance to improve what comes next—with you in control.
A few words. A whole workflow.
Tell it what the brand is about. It plans the week, drafts the captions, picks the slots and publishes to TikTok, Instagram Reels, YouTube Shorts, LinkedIn, Facebook Reels, X, Snapchat Spotlight, Threads and Bluesky. You read results, not a queue.
Postdom Chat with no setup, or Claude, ChatGPT, Cursor or any MCP client.
Schedule these videos using the captions and posting windows in my Postdom brief.
Postdom Chat shown as designed, ahead of release.
One post, start to finish
Views and watch time come back after every publish. A metric the platform withholds comes back with its reason, never a zero.
1Here is what happened
At the wheel
Behind the scenes · published Monday 1 September
| When | Views | Watch time |
|---|---|---|
| +1h | 310 | 31m |
| +6h | 980 | 1h 39m |
| +24h | 2,140 | 3h 33m |
| +72h | 3,600 | 5h 59m |
| +7d | 4,120 | 6h 54m |
Median for this account's product posts, same week620
2Here is what changed
WasOpen with the finished piece.
NowOpen with the hands at work.
Your brief is versioned, so the line that changed and the results behind it stay together.
Explore insights3Here is the next post
Sixty seconds at the wheel. Hands first, glaze last, and the finished cup only at the end.
Monday 15 September, 09:00
Your trust level decides whether a draft like this waits for you.
Explore approvalsExample workspace · illustrative data, not a customer’s results, and not a promise about yours.
“We used to do everything by hand and hope for the best. Now we approve our agent’s work and learn what worked, what didn’t, and what to try next. Every week, it gets better. Nothing comes close to Postdom. Everything else feels built for another era.”
Your content. Your agent’s plan.
You choose what goes out.
3 proposed posts · Times in UTC
Meet Postdom. Your content, with a plan.
Your next post starts with a plan.
A new way to work with your agent.
Four trust levels.
From review every post to fully autonomous.
Explore trust levelsWindows, caps and quiet hours.
Set per account, not once for everything.
Explore policyAn approval queue.
For anything that matters.
Explore approvalsA runs ledger.
It records what each platform confirmed, never more.
Explore runsConnect
Claude, ChatGPT, Cursor or any MCP client, or Postdom Chat with no setup.
One URL, fifteen tools, your policy either way. Connect it to Postdom and approve its access, and your brief and publishing rules give it the context to plan.
Connect your agentConnect Postdom.
Example connection: add Postdom using https://api.postdom.com/mcp in your agent’s connection setup, then authorize workspace access. Once connected, the agent reads your Workspace Brief and publishing rules. I’ve read your brief. I’ll plan up to 3 videos a day in your 3-hour posting windows, Pacific time. You’ll review posts before they go out. No connection or authorization is performed by this illustration.
Example connection · configured rules
Using an AI agent? Connect it to your Postdom workspace, then keep publishing inside human-approved boundaries.
Sign in or create a workspace, then choose the setup route for your client. A pasted prompt on its own does not connect anything.
For the documented local Codex setup, open Advanced: Use a workspace key in Agents. An authorized workspace administrator creates the key; its configuration is shown once.
Use Node.js 22 or newer and the Codex guide to add Postdom to your existing MCP configuration. Keep credentials in private configuration or your secret manager, never in chat or source control.
Add the operating brief to AGENTS.md. Ask Codex to call get_workspace_status and read the Workspace Brief before planning; a human keeps approval authority.
npx -y @postdom/mcp@0.4.0Agents → Advanced: Use a workspace key shows the full configuration once, when an authorized administrator creates the key. Add it to your existing private MCP configuration, not a chat message. Node.js 22 or newer.
Sign in or create a workspace, then choose the setup route for your client. A pasted prompt on its own does not connect anything.
For Claude Code's documented local setup, open Advanced: Use a workspace key in Agents. An authorized workspace administrator creates the key. For Claude on the web, Agents offers a separate OAuth connector under Set up in Claude.
Before starting Claude Code, load POSTDOM_API_KEY into its private environment using your secret manager, then register Postdom with the command below.
Use Node.js 22 or newer, add the operating brief to CLAUDE.md, then ask Claude Code to call get_workspace_status and read the Workspace Brief before planning. Keep approval with a human.
claude mcp add --transport stdio --scope local postdom -- npx -y @postdom/mcp@0.4.0Before starting Claude Code, load POSTDOM_API_KEY into its private environment using your secret manager. This command contains no credentials.
Sign in or create a workspace, then choose the setup route for your client. A pasted prompt on its own does not connect anything.
In Agents, choose Install in Cursor. Review the remote MCP server, complete OAuth when prompted and approve access to the intended Postdom workspace. Your workspace may restrict server installation.
This OAuth route does not require copying a workspace key. The Cursor guide below covers the separate local setup if you need it; keep any local credentials outside chat and source control.
Add the operating brief to a Postdom project rule, then ask Cursor to call get_workspace_status and read the Workspace Brief before planning. Keep approval with a human.
Sign in or create a workspace, then choose the setup route for your client. A pasted prompt on its own does not connect anything.
Agents shows the remote ChatGPT setup. It requires Developer mode on the web, an eligible plan and permission under your ChatGPT workspace policy. Check the ChatGPT guide for verification limits.
Follow the ChatGPT steps in Agents to add the public MCP URL and authorize the intended Postdom workspace through OAuth. Do not paste a local MCP configuration or workspace key into ChatGPT.
Select Postdom in the chat and verify get_workspace_status before relying on the 15 tools. Project instructions carry the operating brief, not credentials; a human retains publishing approval.
Supported social networks
One place. All your channels.
The Postdom journal
The last caption I wrote by hand. A month of letting an AI agent run our own social accounts. The week of checking everything, what got worse, what went quiet, and what I still do by hand.
Guides for connecting accounts and publishing your first post.
QuickstartSetup instructions for using Postdom with your preferred AI tools.
Agent setupQuestions about whether Postdom fits your workflow?
Book a callA few things worth knowing
From connecting your agent to keeping control of what goes out.
Explore the docsPostdom lets an AI agent publish to nine social platforms inside the rules you set, and learn from what each post did. Draft, schedule and publish with your AI agent. It learns from performance to improve what comes next—with you in control. Publish agent-provided video to TikTok, Instagram Reels, YouTube Shorts, LinkedIn, Facebook Reels, X, Snapchat Spotlight, Threads, and Bluesky. Postdom does not generate video. The REST API also accepts text-only posts where the destination supports them. The published MCP publish_video tool still requires video.
Yes, by different routes. Codex and Claude Code have documented local MCP setups using a workspace key from Agents → Advanced: Use a workspace key. Keep credentials in private configuration or your secret manager, never in chat or source control. For Cursor and ChatGPT, Agents offers remote OAuth setup without copying a workspace key; client plan and workspace-policy requirements still apply. Claude on the web also has a separate OAuth connector. Check each guide's prerequisites and verification limits. Verify get_workspace_status before relying on the 15 Postdom tools. A human authorizes workspace access and retains publishing approval; pasting text alone connects nothing.
Postdom never stores your passwords. For eight of the nine destinations the login happens on the platform's own OAuth screen and Postdom only ever receives the authorization. Bluesky is different: it has no OAuth screen, so you generate an app password in Bluesky's settings and can revoke it there at any time. It is used once to establish the connection and is not kept. You choose per-account autonomy levels: review individual posts, approve plans with time and post limits, or set account-level rules.
Schedules survive restarts and sleeping agents. A missed publishing slot stops safely rather than publishing late. Every post ends published, rejected, or blocked, with the reason. A failed post is not an ending — it can be rescheduled or retried. Every metric carries an availability state — when a platform does not expose a number, Postdom returns null and says why, instead of inventing a zero. Agents never learn from made-up data.
Yes. Use the Postdom dashboard to compose a post, add your media, choose connected accounts and schedule it yourself. Your account permissions and publishing rules still apply.
Postdom has a permanent Free plan and paid monthly plans for larger workspaces. Current tiers, included usage, and overage pricing are published on the Pricing page.
Your agent. Your rules.
Connect your agent, bring your content, and keep publishing on your terms.
Connect your accounts
Your accounts.
Ready to publish.
Choose where you publish. Authorize each account, with your publishing approvals still in place.
Connect your accountsSocial accounts
Northstar · Example workspace
TikTok
@northstar.studio
YouTube Shorts
@northstarstudio
Instagram Reels
@northstar.studio
Continue to Instagram to review and authorize access. Then return to Postdom.
Example connection · no account access
Illustration: two example accounts are connected. A person adds Instagram, authorizes access on Instagram, and returns to Postdom. The selected example account @northstar.studio then appears as Connected. This preview performs no connection or authorization.