Allow marking servers/tools MCP for enabled/auto-allow in mcp.json

[digitarald]

tl;dr: Manage enabled and allowed state for servers/tools in the server configuration.

Servers with many tools impact the usability of the tool picker; requiring repeated grooming of the list. Some servers start to provide command line flags to reduce tools; but as a client we can help here.

Out of the box, every single MCP invocation requires a confirmation now. While MCP servers could eventually provide "risk" signals, this should be a configurable user/team-choice in mcp.json to reduce the amount of confirmations.

[connor4312]

I think a storage-based system is better, as it lets users set up trust ad-hoc without trying to figure out tool names in advance and edit JSON configs

[digitarald]

Storage-based solves this for a single user, that hopefully take the time to click through the dropdown. But its not allow to capture prior decisions from a team setting up a repo/codespace for MCP tools.

Could we keep this open to capture interest in a declarative approach?