Loudcode
Back to blog

How to post to X from Claude Code (MCP setup guide)

By Naod Tadele · · 5 min read

Loudcode guidePost to X fromClaude Code

Claude Code sees everything you build in a session: the files it touched, the bug you chased, the reason you picked one fix over another. That is exactly what a good build in public post needs. The problem is that the session ends, you close the terminal, and the post never gets written.

With an MCP server, Claude Code can hand that context to an X tool before you close anything. This guide shows how to connect Claude Code to Loudcode in one command, what to say at the end of a session, and how to keep the result sounding like you.

What you'll be able to do

  • Say "post about what we just shipped" and get a draft in your voice.
  • Say "make it a thread" when the day was bigger than one post.
  • Say "queue it for tomorrow morning" to schedule it on X.
  • Ask "how did my last few posts do?" and see views, likes and replies.

Claude Code never posts on its own. It saves drafts, and it queues one only when you ask.

Setup

1. Create a key. In Loudcode, open Account settings, find "Use Loudcode in your AI tools (MCP)" and click Create API key. Loudcode shows the key once, with the Claude Code command already filled in. Copy it.

2. Add the server. Run this once in your terminal, with your key in place of YOUR_KEY:

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

The `--scope user` flag makes Loudcode available in every project on your machine, so you set it up once.

3. Check it. Run `claude mcp list` in your terminal, or type `/mcp` inside Claude Code. You should see loudcode listed as connected.

The setup docs also cover Codex, Cursor, Windsurf, VS Code and Cline if you use more than one tool.

Prompts to use at the end of a session

  1. "Post about what we just shipped." The everyday one. Claude Code writes a summary of the session and Loudcode turns it into a draft.
  2. "Post about the bug we fixed today, and why it took so long." Struggle posts invite replies, because other developers have hit the same wall.
  3. "Turn this week into a thread." For launches and big weeks.
  4. "I only refactored today. What could I post?" Loudcode suggests ideas from your product, numbers and repo.
  5. "Do my weekly Loudcode check-in." Claude Code answers the check-in questions from what it knows, and Loudcode plans a week of posts.

Here's the kind of draft a session like that can produce, for a fictional on-call tool called Nightshift:

Example post
Nightshift now groups related alerts into one incident summary. Last week a single bad deploy paged our test team 14 times. Now it's 1 summary with the deploy linked at the top. On-call should mean fixing things, not reading the same alert 14 times.

Give Claude Code good material

The draft can only be as specific as the summary Claude Code sends. A few habits help:

  • Say who it's for. "Fixed alert grouping so on-call engineers get one page per incident" beats "improved alerts".
  • Mention the why. If you argued about an approach in the session, say "include why we chose this".
  • Name the struggle. "Mention that it took two tries" gives the post a story.
  • Ask for one post, not five. You can always ask for alternatives after.

Make it a habit with CLAUDE.md

Claude Code reads a CLAUDE.md file for instructions. Add one line so you don't have to remember:

When we finish shipping a user-facing change, ask if I want a Loudcode draft about it.

Now the reminder shows up right when the details are freshest, and you can still say no.

Keep it sounding like you

  • Set your voice once. In Loudcode's Voice & tone, pick a tone, list phrases you never use, and paste a few of your past posts.
  • Describe your product. Loudcode adds your product context to every draft, so a stranger on X understands what you built.
  • Edit before it goes out. Drafts wait in your Loudcode queue. Change a word, rewrite it, or skip it.

Troubleshooting

  • loudcode doesn't show up. Run `claude mcp list`. If it's missing, run the add command again and check the key has no extra spaces.
  • It shows but fails. The key may be revoked or mistyped. Create a new one and replace it.
  • Drafts stop arriving. Drafts from Claude Code count toward your plan like any other. The free plan includes 10 drafts a month.

How Loudcode fits in

Claude Code brings the context of the session. Loudcode brings the rest: your voice, your product description, your posting times, and a queue where you approve every post before it reaches X. It also reads your GitHub commits, pull requests and releases, so the weeks you don't ask still have something to post about.

For the bigger picture, read build in public without leaving Claude Code, Codex or Cursor.

You ship the code. We write the posts.

Your commits, revenue, traffic and a 30-second weekly check-in become build-in-public posts for X, in your voice. You approve every post.

Start your free trialTry the live demo

Keep reading

All posts
Loudcode guideBuild in publicmistakesBuild in public mistakes that cost founders followers (and what to do instead)Building in public works until it doesn't. These are the habits that quietly make people unfollow, and what to do instead.Loudcode guideX threadsdevelopers readHow to write X threads developers actually read (structure and examples)Most developer threads lose people after the first post. Here's how to write one they finish.Loudcode guidePost to X fromWindsurf andVS CodeHow to post to X from Windsurf and VS Code Copilot (MCP setup guide)Cascade and Copilot already know what you shipped today. One JSON file lets them turn it into a post you approve.