[FEATURE] Enable unloading mcp tools with /mcp to be able to reduce context bloat easily.
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
I use Atlassian and Gitlab MCP tools and sometimes a few more. I was shocked to see how much of /context it consumes. Context rot degrades performance and loading expensive tool descriptions in context, when not useful is a quick way to degrade performance. I would like to be able to connect mcp tools when I expect to be using them with /mcp. To have them available, but be able to turn them off for conversation and turn them on, when and if I will need them.
Proposed Solution
Just a new button like "reconnect", but "disconnect". E.g. with Atlassian I can achieve this by "removing authentication". It removes the tools and frees up /context. However, gitlab mcp that I run locally cannot clear any authentication and I do not have other way of removing the tools other than removing mcp from the config. I would like to simply "disconenct" with a buttoon mcps I don't expect to use any time soon and connect them, when I do.
Alternative Solutions
The only workaround I have now to achieve this is to painfully look for the mcp config file, remove the mcp there, start a new convo and it's gone. Or for mcps with authentication I can remove authentication as workaround
Priority
High - Significant impact on productivity
Feature Category
MCP server integration
Use Case Example
I'm starting a new convo. I give jira id. It looks up the ticket. I do not expect to need jira any time soon afterwards for the rest of the work. I do /mcp, select Jira and "unload" mcp tools. /context shows that mcp tools for Jira are no longer there, having a very free /context. Nice. I do work without context rot. At the end I want it to send a comment to jira as part of closing the work. I reload Jira via /mcp. Since I did not use clear authentication workaround, it simply loads the tools to context again, no need to re-authenticate.
Additional Context
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗