Current availability · 26 August 2026
Setup availability
A human creates one workspace key and pastes the generated MCP configuration. The agent can inspect setup, discover destinations, and start the human authorization handoff.
Public evidence
Documented now
Public MCP package
@postdom/mcp@0.3.0 is public, requires Node.js 22 or newer, and is pinned in the configuration generated by Accounts.
Thirteen configured tools
Accepted fields and authority boundaries match the current MCP contract.
Workspace agent keys
Owners and admins create or revoke scoped keys in Accounts; Postdom stores only their SHA-256 hashes.
Three documented destinations
TikTok, Instagram Reels, and YouTube Shorts have reference pages in the current platform model. LinkedIn, Facebook Reels, X, Snapchat Spotlight, Threads, and Bluesky are publicly supported destinations without reference pages yet.
Destination connection
Authenticated workspaces can connect eligible destination accounts. A human completes OAuth on the provider screen.
Twenty-seven availability mappings
Nine fields across three documented destinations describe modeled availability, not guaranteed operational values.
Access boundary
Workspace scope
The MCP package is public. Each connection still needs the workspace-scoped API URL and one-time key generated in Accounts.
Tool access
A human pastes the generated configuration; the thirteen tools then expose setup status, exact destination IDs, direct media upload, and evidence-backed comparisons.
Media source
upload_media returns a short-lived workspace-scoped PUT contract; get_media verifies the stored handle before publishing.
Visibility defaults
TikTok uses SELF_ONLY and YouTube uses private. The Instagram adapter does not expose a visibility field. LinkedIn is different again: its Posts API requires a visibility value, so one is always set — by LinkedIn, on the account’s behalf. Postdom neither chooses nor reads it, so an absent value here is unknown rather than unsupported.
Facebook Reels, X and Snapchat Spotlight each publish under the account’s own audience settings and Postdom sends no visibility value for any of them. Facebook’s only setting is the fixed Reel format. Snapchat additionally needs a Public Profile on the account before it can publish at all.
Threads is the same again — Postdom sends no Threads settings and Meta’s posting endpoint exposes no visibility field. What differs is why an absent value is honest here: a Threads profile is public or private, and the post inherits that from the account. The audience control is real and it is one level up, so Postdom neither sets nor reads it.
Bluesky is the genuinely-absent case rather than the unknown one: an app.bsky.feed.post carries no visibility field, so every post is public and there is nothing to choose. Reply gating lives in separate threadgate and postgate records that Postdom does not write.
Measurement
Never and unverified fields retain reasons. Other null values may have no reason.
Current limits
Remaining setup limits
The agent connection is installable. These steps still need human or workspace-specific setup.
- 01
Social connections
A human completes destination OAuth; agents receive the authorization handoff without seeing social credentials.
Available actions
Start with truth
Create a workspace by email, then create a one-time agent key in Accounts. Paste the generated configuration and ask the agent to check workspace status.