Feedback on MCP Configuration Experience in Windows Environment - Seeking Guidance

Discussion
1

After attempting to configure MCP on Windows for Cursor editor, I’d like to share my experience and seek community support. Here are the key challenges I encountered:

  1. Lack of Windows-specific Documentation
    The current MCP documentation appears primarily focused on Unix-based systems. As a Windows user, I had to spend considerable time searching through forum archives (special thanks to @secprobe for sharing helpful insights) to piece together configuration steps.
  2. Multiple Terminal Popup Issue
    Post-installation of three MCP tools, I’m experiencing three blank terminal windows upon editor launch. This recurring visual disruption significantly impacts the user experience. Has anyone else encountered similar behavior? I’m wondering if this indicates a configuration error on my end.
  3. Documentation Version Mismatch
    The available MCP documentation doesn’t appear to align with the current tool version. Several configuration flags and parameters mentioned seem deprecated or non-functional.
1 Like
2

Totally agree, MCP in Windows (especially with WSL) is a sadly a confusing mess.

I had some success using the Gmail SSE-type from composio, and some brief success with browsertools using the odd cmd /c npx -y … command, but this means we have to maintain Node on Windows as well as WSL.

Also, with the latest 0.47 release, the adding MCP UI has gone in favour of separate global / project json files.

1 Like
3

Some progress with Win + WSL:

2 Likes