Announce your product with Claude Code or Codex

Start with one product announcement

This walkthrough creates one Threads post, starting with text alone. You provide the product facts, account and time. Your agent drafts the post, schedules it after your confirmation if it has publishing access, and checks the result. For another platform, check its format and media requirements first.

Have your product URL, a factual description of the update and the social account you want to use ready. You use your own coding agent for the draft. If you grant only draft/read access, submit the finished post from the SosoAPI app.

• Check supported platforms and formats
• Compare agent publishing tools

1. Connect your assistant and sign in

For local MCP, use Node.js 20 or later and the command for Claude Code or Codex below. For hosted MCP, a compatible client can use the remote URL below with OAuth and automatic client registration; no local Node.js installation or pasted API key is needed.

Ask your agent to follow the setup document. When the browser opens, sign in and choose its workspaces and access. Read, create and edit access covers preparation; add Schedule and publish access if you want the agent to submit the post.

ChatGPT custom MCP apps require a compatible plan and developer-mode access. Complete the client’s trust steps and SosoAPI consent, then check that tools appear and an authorized account read works. Check your own client rather than assuming all clients support the same setup.

Set up SosoAPI from https://sosoapi.ai/setup.md. Keep my current content and task. I will sign in and approve access when asked. Do not publish anything during setup.

claude mcp add sosoapi -e SOSOAPI_TOOL_PROFILE=core -- npx -y sosoapi

codex mcp add sosoapi --env SOSOAPI_TOOL_PROFILE=core -- npx -y sosoapi

https://gqeshlawtcexsapabaui.supabase.co/functions/v1/remote-mcp

• Set up your own AI agent
• Machine-readable setup instructions

2. Ask for a draft with a visible review boundary

Ask the agent to find the workspace and connected account you want to use, read relevant context and draft the post in your conversation. Drafting there does not create a Scheduled Post or submit anything to a platform.

• Review factual claims, rights to media and the destination.
• Upload/import selected media and await readiness before scheduling.
• Ask the agent to check full-draft eligibility and quota; the read-only preview reserves nothing.

Help me announce <product or update> on my Threads account. First show the Workspace and exact account you found. Draft one post using only the facts I provide. Show the caption, media, local time and timezone. Do not create a Scheduled Post, publish, reply, or change an account until I confirm the exact action.

3. Confirm one exact action

Once you are happy with the draft, confirm the account, content and future publishing time. With publishing access and an eligible account, your agent can create the schedule using sosoapi_create_scheduled_post.

The access you approve during sign-in continues until you revoke it. SosoAPI does not open a new browser approval for each post, so tell your agent when you want it to wait for your review.

I approve the displayed draft and ready media for <exact account> at <future local date and time> in <IANA timezone>. Create this one Scheduled Post once. Keep its ID and stable idempotency key. Show the returned state; do not describe it as published until the provider outcome confirms it.

4. Follow the original post and handle uncertainty

Ask the agent to call sosoapi_get_scheduled_post and read the version, delivery state, available actions and outcomes. Scheduled means it is waiting to run; publishing means the platform has not confirmed the result yet. Report published only after the platform-confirmed outcome is available.

If a request times out, check the same post or repeat the same idempotent request to find its result. Do not create a replacement post or import the media again just because the response was lost. To retry a failed post, select the retry action offered for that existing post.

To use a different destination, cancel the unpublished post and confirm a new one. Revoking the agent stops its future access, but it does not cancel schedules SosoAPI has already accepted; manage those separately.

• Publishing API reference
• Threads text and image recipe

5. Keep access revocable

Use Settings → Agents & API Access to inspect and revoke the device or key. For local sign-out, run npx sosoapi auth logout. Keep tokens out of prompts, repository files and screenshots.

The core profile keeps the visible tool list short; it does not change the permissions you have granted. Check your agent’s draft for factual accuracy and follow the actual publishing result.