Claude Code 路 Release workflow
How to post to social media from Claude Code
Release day has two jobs: ship the code and tell people. Claude Code already has the context for the second one. This guide connects it to SimplePost and walks through a release announcement from changelog to scheduled posts.
About 10 minutes the first time 路 Free 7-day trial, no credit card
Quick answer
Can Claude Code post to social media?
Yes, with SimplePost's MCP server. Add it with one command, authenticate with /mcp, and Claude Code can draft, preview and schedule posts on the accounts you connected in SimplePost.
Before you start
What you need
- Claude Code installed, in the repository you are releasing.
- Accounts connected in SimplePost (this example uses X, LinkedIn and Bluesky).
- Public URLs for any images, such as release assets; the hosted server cannot read local files.
Workflow
Step by step: how to post to social media from Claude Code
Add SimplePost to Claude Code
Run the command once; add --scope user to use it in every project.
claude mcp add --transport http simplepost https://app.simplepost.social/mcpAuthenticate
In Claude Code, run /mcp, select simplepost and sign in to SimplePost in the browser.
/mcpSummarize the release
Ask Claude Code to read the changelog and commits and write the user-facing highlights. Correct anything it gets wrong before drafting posts.
Prompt Read CHANGELOG.md and the commits since the last tag. Give me three user-facing highlights for this release.
Draft one post with per-network versions
Ask for a single SimplePost post: a summary for LinkedIn and a short thread for X and Bluesky, saved as a draft.
Prompt List my SimplePost accounts. Save one draft: a LinkedIn summary, and a three-post thread for X and Bluesky as per-account overrides. Link the GitHub release. Show me every version.
Schedule for the release time
Use an exact time. Ask for a new idempotency key so a retry never creates a duplicate.
Prompt Schedule the draft for 15:00 UTC today with a new idempotency key.
Verify after publishing
Ask for the per-account results and links.
Prompt After 15:00, inspect the post and list the result and link for each account.
Before you schedule
Check these details
- Version numbers, links and product names match the repository exactly.
- Each network's version fits its limit; the thread is only on X, Bluesky, Threads or Telegram.
- The scheduled time matches the release, in UTC or an explicit timezone.
- Images, if any, are public URLs.
Want to check the text first without an account? Use the Thread generator.
Troubleshooting
If something gets in the way
simplepost needs authentication
Run /mcp again and complete the browser sign-in.
A local screenshot failed
Upload it as a release asset or elsewhere public, then use its URL.
The release slipped
Ask Claude Code to reschedule or discard the post; it works until the post starts publishing.
FAQ
Questions about this workflow
Can this run in CI without Claude Code?
Yes, with the SimplePost CLI (Advanced and Pro) or the HTTP API (Pro). The CLI publishes immediately; the API can schedule.
Does Claude Code need an API key?
No. It uses OAuth with the hosted MCP server.
Can Cursor do the same?
Yes. Add the same server URL to Cursor's mcp.json; the workflow is the same.
Try this workflow with your own accounts
7 days free 路 No credit card 路 10 posts per platform during the trial