Separate "Auto-run MCP" Option from "Enable auto-run mode"

Hi there guys,

I’d like to suggest an improvement that I think would really help everyone out. Can you guys please add an option to separately select the “auto-run MCP” Option setting from the “Enable auto-run mode”?

Honestly, having to manually turn on “auto-run MCP” each time is annoying and interrupts my workflow.

Many users, including myself, prefer having “MCP auto-run” enabled without necessarily wanting all the features bundled with “Enable auto-run mode”.

This has been brought up multiple times already, so it’s definitely something the most of us agrees on.

6 Likes

There is a Auto run setting to allo it to access MCPs.

image

Let me know if that answers your question.

If it doesnt work, you can file a detailed bug report so it can be analyzed and the cause found.

Thanks for your reply,

I think there might have been a misunderstanding. The existing option, “MCP tools protection,” is only designed to prevent the agent from running MCP tools automatically once the general “Enable auto-run mode” is activated.

However, point and what others have also requested is precisely to be able to enable “auto-run MCP” independently, without having to activate the general “Enable auto-run mode”.

Currently, everytime i turn on the “auto-run mode” setting to have MCP tools run automatically, it brings along several additional behaviors from the iA

I’m sure this would help us have greater control and flexibility, avoiding unnecessary workflow disruptions.

2 Likes

I agree, I dont want to use any other auto run settings, only allow automatic access to MCP… +++

3 Likes

yep
+1

2 Likes

it should be separated +1

1 Like

Agree. Voted.

Better yet, put it in the actual MCP interface.
Each MCP server should have its own option (auto run)

I might not want some to be auto run.

1 Like

I wanna make a Quote"", about this brilliant idea…

I was the last one to reply it, then i wanna bring up again!

To emphasize the real need for a fully independent “Auto-Run MCP” control, separate from the global “Auto-Run Mode”. Right now, when I disable “Auto-Run Mode”, all automations are turned off (MCPs included). And when I enable the global auto-run just to allow MCPs, I end up bringing along every other automated behaviors (command execution, file writes, linters, etc..). So, the only related option today is the “MCP Tools Protection” checkbox, but it only blocks MCPs once the general auto-run is active. In other words, it doesn’t solve our use case of wanting to keep only MCP auto-run enabled without activating full auto-run.

I think we need a standalone “Auto-Run MCP” toggle outside of “Enable auto-run mode,” with the ability to whitelist by URL or server.

2 Likes