Post your release notes from Claude Code

When you ship something, the announcement is usually an afterthought: someone writes it a day later, or nobody does. If you work in Claude Code, the commits are already in front of it. With SocialHelper connected, Claude Code can turn a release into posts for LinkedIn, Bluesky or anywhere else you’ve connected, show you the drafts, and publish them after you approve.

Add SocialHelper to Claude Code

Create an API key on the API & MCP page in SocialHelper, then add the server once:

claude mcp add --transport http socialhelper https://socialhelper.app/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Replace YOUR_API_KEY with your key. To share the setup with your team instead, commit a .mcp.json that reads the key from an environment variable; the Claude Code integration guide shows both. Check it works by asking Claude Code to list your SocialHelper accounts.

Announce a release

From your repository, after tagging the release:

Write a short post about what changed since v2.3 for LinkedIn and Bluesky. Lead with what users can do now, skip internal refactors. Show me both drafts before posting.

Claude Code reads the commits itself, writes the drafts and checks them against each platform’s limits. Bluesky allows 300 characters and LinkedIn 3,000, so it will usually write two versions. When you say yes, it publishes and reports back with the links.

Images need a public URL, such as a screenshot in your docs or release assets. Claude Code can’t upload a file from your disk to SocialHelper directly.

Time it with the launch

If the release goes out tomorrow morning, ask for the post to be scheduled instead:

Schedule it for tomorrow at 10 am UTC, after the deploy.

If the deploy slips, ask Claude Code to move the post or cancel it. Scheduled posts can be changed until a minute before they go out.

Make it part of the release script

Once the wording settles into a pattern, you might want the post without opening Claude Code at all. The same thing is one request to the REST API, which you can call from CI after a successful deploy:

curl https://socialhelper.app/api/v1/posts \
  -H "Authorization: Bearer $SOCIALHELPER_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
      "text": "Fresh out of the oven: our cinnamon rolls are back for autumn 🍂 Get them warm from 7am, while they last.",
      "accounts": [
          "ACCOUNT_ID_1",
          "ACCOUNT_ID_2"
      ]
  }'

Keep the key in your CI secrets. The Idempotency-Key header means a re-run of the job returns the first post instead of publishing it twice. The posting docs cover scheduling, media and per-platform text.