YOLO mode doesn't auto-run MCP tools

Feedback
1

Dunno if it’s just me but even though YOLO mode is enabled with no restrictions and works fine for normal commands, it still asks for manual approval for any MCP tools which can be extremely annoying with stuff like sequential thinking (for example.)

Is this intentional? Future planned feature? If this is intentional I’d definitely love to see an option to just auto-approve MCP tool requests (hence why I’m posting this in feedback, though if it’s not intentional then I guess bug reports would’ve been a better location…)

I’d like it to use sequential thinking, memory, and whatever else automatically as it deems necessary but having to approve it every single time it wants to use an MCP tool feels like unnecessary friction if I’ve already indicated it can run all commands automatically.

Also: Related to MCP servers, I noticed two problems and I’m not sure if they’re just something on my end or not, but:

  1. It seems like cursor can’t run npx-based stdio MCP servers even though they work fine in my terminal. This might be something wrong with my setup but if anyone knows what the deal is suggestions to fix it would be most appreciated.
  2. When running MCP servers via docker, it starts up an empty terminal for each MCP server. I haven’t seen this happen until the most recent version (0.45.11) or in stuff like Cline, so this might just be a bug. Dunno, but it would definitely be nice if those could just be hidden in the background rather than appearing in the foreground. I have 3 MCP servers configured, and every window of Cursor opens 3 new blank terminals for them running docker.exe from Chocolatey’s directory in ProgramData.

Additional somewhat unimportant MCP feedback: Please let us edit MCP servers via a JSON file similar to other IDEs/Claude/Cline/etc. with support for env variables and all that so we don’t need to make wrapper scripts :frowning:

9 Likes
2

I agree with everything you said. Having to independently click approve 5 times every time sequential thinking runs is a huge PITA!

3 Likes
3

I use cli tools even if there is a better MCP because I can yolo the cli tools.

2 Likes
4

Something I tried was getting it to use echo as a replacement for sequential thinking so it could have a “thought” and break up it’s generation a bit since it would then have to read the response similar to a tool call, which worked really well. Only issue is, while this worked fine in the composer chat I tested it in, it seems to totally ignore this instruction when it’s added to the rules. Very annoying either way, and could be easily solved by just adding the option to auto-run MCP tools…

Edit: got it to do sequential thinking (sortof) via echo by adding the instruction for it to the yolo prompt. Dunno if this helps anyone equally annoying as I am at having to manually accept every single sequential thinking request, but there you go. Seems to be basically the same effect albeit not as nice.

5

MCP not running automatically is running the vibe coding :face_with_symbols_over_mouth:

2 Likes
6

Strongly agree - this issue goes beyond just sequential thinking. The real impact is on automated workflows where multiple MCP tools need to chain together. Having to manually approve each tool (brave search + notion + jira + github + filesystem + aws, etc.) completely breaks the flow that YOLO mode is meant to enable. Current workarounds like using echo or falling back to CLI tools show how much this affects productivity.

This should be prioritized as it’s fundamentally undermining YOLO mode’s purpose for power users who rely on tool chaining and automation.

2 Likes
7

Hey, v0.46 now support YOLOing MCP tools, so once it’s available to everyone, do give it a try!

1 Like