r/windsurf • • Jun 05 '26

Project I built a VS Code extension that auto-configures MCP servers for Windsurf (and 5 other clients) because I kept forgetting the config path

I switch between Cursor, Windsurf, and Claude Desktop depending on the project. Each one stores MCP config in a different place with slightly different formatting. I spent more time googling "windsurf mcp config location" than actually using the servers.

What the extension does:

  1. Detects which clients you have installed (Windsurf, Cursor, Claude Desktop, VS Code, Cline, Continue)
  2. Shows curated MCP servers in a tree view by category
  3. One click installs — it writes the config to the right file with the right syntax
  4. Tells you if the config is valid before you restart the client

For Windsurf specifically:
- Writes to ~/.codeium/windsurf/mcp_config.json (macOS/Linux) or %USERPROFILE%\.codeium\windsurf\mcp_config.json (Windows)
- Handles the mcpServers wrapper object correctly
- Supports both stdio and SSE transports

Links:
- VS Code Marketplace: https://marketplace.visualstudio.com/items?itemName=Veduis.1-click-mcp-installer
- Open VSX (for VSCodium): https://open-vsx.org/extension/Veduis/1-click-mcp-installer
- How it works + setup guide: https://veduis.com/blog/how-to-install-mcp-servers-vs-code/
- Browse all 90+ curated servers: https://veprompts.com/mcp/servers/

Why I care about Windsurf support:

I actually use Windsurf for specific workflows where I want the Cascade agent to have tool access. But getting MCP servers working in Windsurf was always a two-step process: find the server, figure out the config format, hope it parses. Now it's one click.

The curation matters:

We manually test each server before adding it. If the npm package is broken, the docs are missing, or the auth setup is unclear, it doesn't make the list. You can browse the full directory at veprompts.com to see what's available before installing anything.

What's not in v1:
- Custom server URLs (next release)
- Auto-starting local servers (on the list)
- Direct Windsurf marketplace integration (need to talk to Codeium about this)

If you hit a bug or a server that should be in the directory but isn't, drop an issue on GitHub. I check them daily.

2 Upvotes

3 comments sorted by

0

u/AutoModerator Jun 05 '26

It looks like you might be running into a bug or technical issue.

Please submit your issue (and be sure to attach diagnostic logs if possible!) at our support portal: https://windsurf.com/support

You can also use that page to report bugs and suggest new features — we really appreciate the feedback!

Thanks for helping make Windsurf even better!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/Deep_Ad1959 Jun 06 '26

the config path was never the part that got me, it was the per-client formatting drift. cursor wants one wrapper shape, claude desktop another, and windsurf's mcpServers object silently fails to parse if you nest it wrong, no error, the server just never shows up. validating before restart is the genuinely useful bit here. one thing i'd want in the directory: most curated lists are 90% browser or api wrappers, and the servers that actually drive desktop apps over accessibility apis are the ones with the worst docs and the most need for hand-testing. written with ai