Back to blog

How to post to X from Windsurf and VS Code Copilot (MCP setup guide)

By Naod Tadele · · 5 min read

Loudcode guidePost to X fromWindsurf andVS Code

Windsurf's Cascade and Copilot in VS Code both do real work in your repo now. They read the code, make the change, and can explain why. By the end of a session, your editor knows more about what you shipped than your notes do. Then you close the window and that story is gone.

An MCP server lets your editor hand that context to an X tool before you close anything. This guide covers both editors: one JSON file each, the prompts to use, and how to keep your key out of git.

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

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

Step 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, so copy it now. You'll paste it into one of the files below in place of YOUR_KEY.

Windsurf setup

Windsurf keeps MCP servers in one file in your home folder: `~/.codeium/windsurf/mcp_config.json`. Create it if it doesn't exist, and add:

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

If the file already has other servers, add the `loudcode` block inside the existing `mcpServers` object instead of pasting a second one.

Then open Cascade and refresh its MCP servers. Loudcode should show up with its tools listed.

VS Code (Copilot) setup

VS Code reads MCP servers from `.vscode/mcp.json` in your project. Create it and add:

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

Two differences from Windsurf: the top key is `servers`, not `mcpServers`, and it needs `"type": "http"`.

Open Copilot Chat and switch it to Agent mode. MCP tools only work there, not in Ask or Edit mode. You can check the tools button in the chat box to confirm Loudcode's tools are on.

Prompts to use at the end of a session

  1. "Post about what we just shipped." The everyday one. Your editor summarizes the session and Loudcode turns it into a draft.
  2. "Post about the bug we fixed and what caused it." Debugging stories get replies, because other developers have hit the same wall.
  3. "Turn this week's work into a thread." For launches and big weeks.
  4. "I only did cleanup today. What could I post?" Loudcode suggests ideas from your product, numbers and repo.
  5. "Do my weekly Loudcode check-in." Your editor 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 incident summaries now show what changed right before the first alert. Deploys, config edits, feature flags. All in one list at the top. Most of our 3am pages turned out to be "someone shipped something at 2:50". Now you see it in 10 seconds.

Give your editor good material

A draft can only be as specific as the summary your editor sends. A few habits help:

  • Say who it's for. "On-call engineers see recent changes first" beats "improved summaries".
  • Include the why. If you picked one approach over another, say "mention why we chose this".
  • Keep the struggle. "Say it took three tries" turns a fix into a story.
  • Ask for one post. You can ask for alternatives after you've read the first.

Make it a habit

Both editors read project rules. In Windsurf, add a rule in Cascade's rules settings. In VS Code, add a line to `.github/copilot-instructions.md`. Either way, the line is the same:

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

The reminder now shows up while the details are fresh, and you can still say no.

Troubleshooting

  • Windsurf doesn't list loudcode. Check the path is `~/.codeium/windsurf/mcp_config.json`, the key is `serverUrl`, and the JSON is valid. Then refresh MCP servers again.
  • VS Code doesn't list it. Check the top key is `servers` and `"type": "http"` is there. Make sure Copilot Chat is in Agent mode.
  • It's listed but calls fail. The key may be revoked, mistyped, or missing the word Bearer. Create a new one and replace it.
  • Drafts stop arriving. Drafts from your editor count toward your plan like any other. The free plan includes 10 drafts a month.

How Loudcode fits in

Your editor brings the context of the session. Loudcode brings the rest: your Voice & tone settings, 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 forget to ask still have something to post about.

The setup docs show every snippet with your key filled in, plus Claude Code, Codex, Cursor and Cline.

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.

Keep reading

All posts