Post about what you shipped, straight from Claude Code

By Naod Tadele · October 12, 2026 · 4 min read

The best moment to post about your work is right after you ship it. You know exactly what changed, why it was hard and why it matters. An hour later you're on the next thing, and the post never happens.

If you build with Claude Code or Cursor, there's another problem: all that context lives in your AI chat. Your assistant watched you build the feature, argued with you about the approach and fixed the bug at 1am. Then you open a blank post and try to remember what you did.

So Loudcode now has an MCP server. Your AI can hand that context straight to Loudcode, and Loudcode turns it into a post in your voice.

What it looks like

You finish a session and type one line to your assistant: "Post about what we just shipped."

Your AI summarizes what you built, Loudcode writes the post with your tone, your product description and your past posts, and saves it as a draft. You review it in Loudcode, tweak a word if you want, and queue it. Nothing goes to X until you say so.

Here's a real draft it wrote after we built this exact feature:

Set it up in two minutes

1. In Loudcode, open Account settings, find Use Loudcode in Claude and click Create API key.
2. Copy the setup line for your editor. It's shown right there with your key filled in.

For Claude Code, run this in your terminal:

claude mcp add --transport http loudcode https://loudcode.dev/mcp --header "Authorization: Bearer YOUR_KEY"

For Cursor, add this to .cursor/mcp.json:

{
  "mcpServers": {
    "loudcode": {
      "url": "https://loudcode.dev/mcp",
      "headers": { "Authorization": "Bearer YOUR_KEY" }
    }
  }
}

That's it. Restart your editor if it doesn't show up right away.

What you can ask

• "Post about what we just shipped." A draft from this session, in your voice.
• "Make it a thread." Same idea, as 3 to 5 posts.
• "Show my drafts." Everything waiting for review, plus what's queued.
• "Queue that one for tomorrow at 9." Only when you ask.
• "How did my posts do this week?" Views, likes and replies, best post first.
• "I didn't ship much. What should I post?" Ideas from your product, numbers and repo.
• "Do my weekly check-in." Your AI answers the four check-in questions from what it saw, and Loudcode plans a week of posts.

What it won't do

Your AI never posts to X on its own. It writes drafts and, when you ask, queues them for your posting times. You can always edit, skip or unqueue them in Loudcode.

Your key is yours: Loudcode only stores a fingerprint of it, shows it once, and you can revoke it any time in Account settings. Drafts written from your editor count toward your plan like any other draft, so there are no surprise costs.

Why this matters if you vibe code

Most of the building now happens in a conversation with an AI. That conversation is the best record of your week that exists: every feature, every dead end, every decision. Build in public used to mean remembering all of that at the end of the week and writing it up. Now it means asking.

If you build every day but your X account is quiet, this is the shortest path we know from shipping to posting. For more on what makes a good update, see how to turn commits into posts people read.