Post to Social Media from Claude Code

How to post to social media from Claude Code

1. Prepare the workspace and video

A human connects the destination in Postdom Accounts, selects per-post review (L1), and loads the workspace key into the terminal environment as POSTDOM_API_KEY. Start with a finished video at an accepted URL or a workspace media handle already marked stored.

Have Claude Code and Node.js 22 or newer installed; that Node requirement belongs to the released MCP package. In Postdom Accounts, a human connects the social account and creates the workspace key. Do not share social passwords with Claude.

Load the key through your approved secret manager or private terminal setup before starting Claude. Keep it out of shell-history commands, chat, CLAUDE.md and source control. This guide's command contains no key. If Accounts supplies a custom API URL, set POSTDOM_API_URL to that value in the same private environment.

2. Connect Claude Code and check its status

From your project terminal, run the local-scope stdio command below for @postdom/mcp@0.3.0, then claude mcp get postdom. Continue only when the connection reports Connected. Launch Claude Code from the same prepared terminal; /mcp shows its connection status.

claude mcp add --transport stdio --scope local postdom -- npx -y @postdom/mcp@0.3.0
claude mcp get postdom

Added confirms a configuration write, not a connection. Local scope is private to you for this project; it is not the team-shared .mcp.json file. If Postdom already exists in your configuration, inspect it before replacing anything. Claude Code's MCP setup reference explains scopes and connection checks, and Postdom as a Claude Code MCP server covers both transports, every tool the connection exposes, and what to check when it does not connect.

Give Claude a video, an account and a stopping point

3. Ask Claude to read before it writes

Use the prepared-video prompt below. Claude reads workspace status, connected accounts and the operating brief, then shows the exact destination, video, caption and settings. Confirm the video review and the applicable audience, disclosure and consent choices before allowing submission.

Here is a first request for a private YouTube walkthrough. Replace the example URL with your accepted media source. Claude must obtain the account's providerAccountId from list_accounts, not guess it from a channel name or use the internal id.

Use Postdom to prepare one YouTube post, not a public release.
First call get_workspace_status, list_accounts and get_brief.
Show me the connected YouTube account and its providerAccountId.
Stop if the connection is locked, the account is missing, or its policy
does not require human approval for each post (L1).

Video: https://media.example.com/finished-demo.mp4
Caption: A closer look at our new workspace
A finished walkthrough for the team.

This is an example URL: ask me for my accepted video URL or stored
media handle before submitting. Do not generate or upload a new video.
Show me the exact video, account, caption and tool settings for review.
Ask me to confirm I watched the video and that private visibility,
not-made-for-kids and synthetic-media disclosure are correct.
Stop if I have not confirmed, or any setting is wrong.

After that confirmation, submit exactly once with publish_video and a
stable idempotency_key for this request. Return the post ID and status.
If requires_approval, wait for my separate approval in Postdom.
Then read get_publish with that same post ID. Report its actual status
and destination result; do not call it publicly live or retry blindly.

For repeated work, place the review and stop rules in CLAUDE.md. That file provides working context, not enforced controls. Postdom's account policy—not the prompt—must require human approval. Claude's permission to call a tool does not establish consent to the content.

{
  "id": "internal-example-id",
  "providerAccountId": "example-youtube-channel",
  "platform": "youtube",
  "status": "connected"
}

{
  "account_ids": [
    "example-youtube-channel"
  ],
  "video_url": "https://media.example.com/finished-demo.mp4",
  "caption": "A closer look at our new workspace\nA finished walkthrough for the team.",
  "intent": "Submit the human-reviewed supplied video to the selected L1 YouTube account as a private, AI-disclosed, not-made-for-kids upload.",
  "idempotency_key": "claude-demo-review-001"
}

{
  "id": "11111111-1111-4111-8111-111111111111",
  "status": "requires_approval",
  "message": "Approve this exact request in Postdom."
}

Read the outcome without posting twice

4. Approve the post, then read the outcome

Claude submits once and returns the post ID. On the L1 account used here, requires_approval means the post is waiting for a human in Postdom. After human approval, Claude reads get_publish for the same ID and reports the returned post and destination states. Approval is not publication.

get_publish({
  "post_id": "11111111-1111-4111-8111-111111111111"
})

A tool permission prompt, approval of a plan, and approval of an individual post are different decisions. This example does not need a plan. Claude cannot grant itself approval or expand its account policy.

If a result is missing or unfamiliar, show it as unresolved and hand it back to the human. Do not guess success. For a published post, inspect each destination's result; YouTube's private visibility has not become public just because the post says published.

For scheduled work, agree on the local time and timezone, then use the YouTube scheduling guide to distinguish a UTC provider handoff from a public release. If you later read performance, preserve missing values as missing: a null is not zero.

Questions before you connect

Start with one reviewed video

Connect the destination, select per-post review, and prepare the media source. Then use the command and first request above. Expand the workflow only after you can trace one request to its actual outcome.