Hi there!
Apart from #432, one feature I’m missing is a global overview of all available tools across all configured MCP servers, with options to filter, sort, and possibly batch-edit them.
Mockup:
Use case
In my setup, I currently have 12 MCP servers configured, which results in almost 500 available tools.
I do not need all of them, and many tools likely overlap across servers. However, it is currently difficult to audit and manage them because the tools are spread across individual server views.
It would be very useful to have a single table-style overview where I can go through all tools and decide which ones should be enabled, disabled, hidden, tagged, or prioritized.
Suggested functionality
A global tools page could include:
- A table listing all tools from all configured servers
- Filtering by server, tool name, enabled/disabled state, category, risk level, etc.
- Sorting by name, server, usage count, last used date, or enabled state
- Batch actions, such as:
- enable/disable selected tools
- permanent hide selected tools
- assign tags or categories
- reset tool permissions
- Configurable columns
Some potentially useful columns:
- Tool name
- MCP server
- Description
- Enabled/disabled state
- Hidden/visible state
- Usage count
- Last used
- Risk level / potentially dangerous tool indicator
- Custom tags
- Approval status
Why this would help
This would make it much easier to manage larger MCP setups where many servers expose overlapping tools.
For example, if multiple MCP servers provide similar GitHub, filesystem, browser, or search tools, I may want to intentionally prefer one implementation over another. A global overview would make that much easier than managing each server in isolation.
It would also help with security and cleanup, since risky or rarely used tools could be found and disabled more easily.
In the future, this could maybe also support custom organization features, such as tagging tools by purpose, grouping tools by category, or showing usage analytics.
This is quite a big feature, but I assume all the data is already there so it's a matter of displaying it differently. Time willing I would be able to work on this.
Hi there!
Apart from #432, one feature I’m missing is a global overview of all available tools across all configured MCP servers, with options to filter, sort, and possibly batch-edit them.
Mockup:
Use case
In my setup, I currently have 12 MCP servers configured, which results in almost 500 available tools.
I do not need all of them, and many tools likely overlap across servers. However, it is currently difficult to audit and manage them because the tools are spread across individual server views.
It would be very useful to have a single table-style overview where I can go through all tools and decide which ones should be enabled, disabled, hidden, tagged, or prioritized.
Suggested functionality
A global tools page could include:
Some potentially useful columns:
Why this would help
This would make it much easier to manage larger MCP setups where many servers expose overlapping tools.
For example, if multiple MCP servers provide similar GitHub, filesystem, browser, or search tools, I may want to intentionally prefer one implementation over another. A global overview would make that much easier than managing each server in isolation.
It would also help with security and cleanup, since risky or rarely used tools could be found and disabled more easily.
In the future, this could maybe also support custom organization features, such as tagging tools by purpose, grouping tools by category, or showing usage analytics.
This is quite a big feature, but I assume all the data is already there so it's a matter of displaying it differently. Time willing I would be able to work on this.