Windows: MCP path with spaces fails; please add in-app bug reporting

Support Bug Reports
,
1

Describe the Bug

1. Bug: MCP server does not start when executable path contains spaces (Windows)

Environment: Windows 10/11, Cursor (current)

What happens:
If the MCP server command in mcp.json points to an path with spaces (e.g. C:\Program Files\Vendor\mcp-server.exe), Cursor spawns the process by building a single command string. The path is not quoted, so it is split at the first space. The system then tries to run C:\Program and fails.

Repro:

  • Put an MCP server in a path with spaces (e.g. under C:\Program Files\...).
  • In ~/.cursor/mcp.json:
    "mcpServers": {
  "my-server": {
    "command": "C:\\Program Files\\Vendor\\Product\\mcp-server.exe",
    "env": {}
  }
}
  • Restart Cursor and use MCP.

Result:
Log shows: Starting new stdio process with command: C:\Program Files\...
Error: 'C:\Program' is not recognized as an internal or external command (or spawn C:\Program ENOENT).

Expected:
The executable path should be passed as one argument (proper argv or quoted string) so that C:\Program Files\... works. Default Windows install paths have spaces; this should be supported without workarounds.

Workaround: Use Windows 8.3 short path (e.g. C:\PROGRA~1\...) — fragile when folder contents change.

2. Feature request: In-app one-click bug / feedback reporting

Problem:
Reporting a bug (like the one above) requires signing up and posting on the forum. There is no way from inside Cursor to submit a bug with one click.

Request:
Add an in-app “Report a bug” or “Send feedback” (e.g. under Help or status bar) that:

  • Opens a simple form or pre-filled issue draft.
  • Optionally attaches basic context: Cursor version, OS, and optionally recent log/config (user consent).
  • Submits to your backend or pre-fills a GitHub issue so paying users can report issues without extra accounts or steps.

Why it matters:
Paying users hit bugs and want to help improve the product. Friction (forum signup, manual logs, no in-app path) makes feedback rare and makes the product feel less user-friendly. A one-click path would improve both signal and perception.

Summary:

  • Bug: Fix MCP spawn on Windows so paths with spaces (e.g. Program Files) work.
  • Feature: Add in-app one-click bug/feedback reporting for all users, especially paying ones.

Thanks for considering both.

Steps to Reproduce

add windows mcp Program Files in path

Operating System

Windows 10/11

Version Information

Version: 2.5.26 (user setup)
VSCode Version: 1.105.1
Commit: 7d96c2a03bb088ad367615e9da1a3fe20fbbc6a0
Date: 2026-02-26T04:57:56.825Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

3

Hey, thanks for the detailed report.

MCP and spaces in paths

This is a known issue. When args is missing, Cursor uses legacy command parsing, which doesn’t handle spaces correctly. Besides using an 8.3 short path, there’s another workaround. Wrap the call with cmd.exe:

"mcpServers": {
  "my-server": {
    "command": "cmd",
    "args": ["/c", "C:\\Program Files\\Vendor\\Product\\mcp-server.exe"],
    "env": {}
  }
}

This lets you pass the full path as a single argument, without it being split on spaces. A similar bug was reported in this thread: Local MCP servers with absolute paths with spaces do not work.

In-app bug reporting

Cursor already has a basic feedback option. In chat, you can open the context menu in the top right and give feedback or thumbs down specific answers. But I agree it’s not a full bug reporter. A similar request is already on the forum: Please add an in-app bug report feature.

Let me know if the cmd workaround helped.