Build in Public From Claude Code and Cursor

Why do it from the editor

The moment you ship is the moment you know what changed, why, and what it took. A day later it's a vague "shipped some improvements". Claude Code already has the diff, the commit messages and the conversation about the bug, so the post can carry the details people actually read: the number that moved, the cause of the bug, the trade-off you picked.

Set it up

You need a Postel account with X or LinkedIn connected under Settings > Channels.

Claude Code (plugin). The plugin adds the server and a writing skill that knows LinkedIn's and X's formatting rules:

/plugin marketplace add robinfaraj/postel-mcp
/plugin install postel@postel

Claude Code (server only):

claude mcp add --transport http postel \
  https://www.postel.app/api/mcp

Run /mcp in a session and sign in to Postel in your browser. Add --scope user to use it in every project. To use an API key instead (Settings > API Keys in Postel):

claude mcp add --transport http postel \
  https://www.postel.app/api/mcp \
  --header "Authorization: Bearer pstl_YOUR_API_KEY"

Cursor:

{
  "mcpServers": {
    "postel": {
      "url": "https://www.postel.app/api/mcp"
    }
  }
}

Cursor signs you in with OAuth. VS Code, Windsurf and other clients are in the full install guide.

Prompts that turn commits into posts

Paste these into Claude Code or Cursor's agent chat in the repo you shipped from:

• "Read the commits since the last tag. Pick the one change a user would notice and draft an X post about it: what it does, and the one detail that made it hard. Lowercase, no hashtags."
• "Turn CHANGELOG.md's latest section into a LinkedIn post for founders who use our product. Lead with the problem it fixes, not the feature name. Put the release link in the first comment."
• "We fixed the memory leak in the importer today. Write a short X thread on what caused it and how we found it, from this session."
• "Draft three posts from this week's merged PRs, one per day Tuesday to Thursday at 9am, X and LinkedIn each. Save them as drafts so I can read them first."
• "Show me what's scheduled next week, and which days are still free."

Claude writes the text itself and saves it with create-post, or asks Postel to write it in your saved voice with generate-post (1 AI credit). Either way it lands as a draft in Postel until you say when it goes out.

One release, a post per network

Ask for a week of posts at once and Claude saves them in one call: create-posts takes up to 25 posts, each with its own network, date, media and LinkedIn first comment. Posts with a date are scheduled; the rest wait as drafts. Threads work on X, Bluesky and Mastodon.

Screenshots and demo videos

Postel attaches images and video from public URLs: your docs site, a GitHub release asset, a CDN link. Up to 4 per post when it's created, then more with attach-media within each network's limits (X: 4 images or one video or GIF; LinkedIn: up to 20 images or one video). JPEG, PNG, WebP, GIF, MP4, MOV and WebM, up to 100 MB.

A screenshot that only exists on your laptop can't be passed through. Upload it somewhere public first, or add it in the Postel editor.

What to post when you build in public

Posts from your own work do well when they're specific. A few that come straight out of a coding session:

• The fix with a surprising cause. "Search was slow because of one missing index on a column we filter by in every query."
• A number that moved. Build time, bundle size, a cost per request, a conversion rate after a change.
• The decision. What you chose not to build this week, and why.
• The shipped thing, shown. A short clip or screenshot with one line on who it's for.
• The mistake. What broke in production and what you changed so it can't happen again.

Ask Claude to keep only what's true from the session. If a draft claims a result you don't have, cut it.

What you need to know

• You start it. Nothing posts on every commit. You ask, review the draft and approve the schedule.
• Claude asks first. Claude Code and Cursor ask before running a tool unless you've allowed it, so keep that on for schedule-post and publish-post.
• Scheduling needs a plan. Scheduling and publishing need a paid plan or the trial: $1 for 7 days, then from $29 a month. Cancel anytime.
• X link posts are capped. X posts that contain a link count against a monthly limit: 30 on Starter, 100 on Pro and unlimited on Team.
• LinkedIn goes to your personal LinkedIn profile. First comments are LinkedIn only, up to 1,250 characters.

Frequently asked questions

Updated Oct 30, 2026.

Can Claude Code post to X or LinkedIn?

Yes, with an MCP server that can publish. With Postel added, Claude Code drafts the post, saves it in Postel and schedules or publishes it after you approve. Postel holds the X and LinkedIn connections, so you don't need an X developer account.

Does it work in Cursor, VS Code or Windsurf?

Yes. Any MCP client that supports remote servers with OAuth or an API key works. Setup for each is on the Postel MCP server page.

Can it post automatically every time I deploy?

Not by itself. Postel's server gives your assistant tools; it doesn't watch your repo. You ask for the posts when you want them, and you can ask for a week of them at once.

Will the posts sound like a changelog?

Only if you ask for one. Tell Claude who reads the post and what they care about, and give it the detail that makes the change interesting. Postel's generate-post writes in the voice it learned from your own posts.

Can it write threads?

Yes. Ask for a thread and generate-post writes and saves it as one draft that's scheduled as a unit on X, Bluesky and Mastodon.

What does it cost?

$1 for 7 days, then from $29 a month. Cancel anytime. The MCP server is in every plan. Saving text Claude wrote uses no AI credits; Postel writing a post uses 1.