Loudcode
Back to blog

How to post to X from Cursor (MCP setup guide)

By Naod Tadele · · 5 min read

Loudcode guidePost to Xfrom Cursor

If you build in Cursor, your chat already holds the best record of your day: what you built, why, and what broke along the way. With an MCP server, Cursor can hand that straight to an X tool, so posting becomes one sentence at the end of a session.

Here's how to set it up with Loudcode, and how to get posts that don't sound like AI.

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" for bigger days.
  • Say "queue it for tomorrow at 9" to schedule it on X.
  • Ask "how did my posts do this week?" without opening X.

Your AI never posts on its own. It writes drafts and queues them only when you ask.

Setup (about 2 minutes)

1. Create a key. In Loudcode, open Account settings, find "Use Loudcode in your AI tools (MCP)" and click Create API key. Pick Cursor, and the config is filled in for you.

2. Add it to Cursor. Paste this into ~/.cursor/mcp.json (for all projects) or .cursor/mcp.json (for one project), with your key:

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

3. Turn it on. Open Cursor Settings, then MCP, and check that loudcode is enabled. Restart Cursor if it doesn't show up.

The full guide, including Claude Code, Codex, Windsurf, VS Code and Cline, is in the setup docs.

Prompts that work well

  • "Post about what we just shipped." The everyday one.
  • "Post about the bug we fixed today, and why it took so long." Struggle posts get the most replies.
  • "Turn this week into a thread."
  • "I only refactored today. What could I post?" Ideas from your product, numbers and repo.
  • "Do my weekly Loudcode check-in." Cursor answers four questions about your week, and Loudcode plans a week of posts.

Keep it sounding like you

  • Give it specifics. "We fixed the timezone bug that broke signups for EU users" beats "made some fixes".
  • Set your voice once. In Loudcode's Voice & tone, pick your tone, add phrases you never use, and paste a few past posts.
  • Describe your product. Loudcode adds your product context to every draft, so strangers understand what you built.
  • Edit before posting. Drafts wait in Loudcode. Change a word, rewrite it, or skip it.

Why not just ask Cursor to write the tweet?

You can. But each chat starts from zero: it doesn't know your product, your voice, or your rules, and it can't schedule anything. With MCP, Cursor brings the context of the session and Loudcode brings everything else, then queues the post for your posting times.

Want 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.