🤖 feat: add ability to disable MCP servers #1091
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a toggle to disable MCP servers without removing them from config. Disabled servers retain their configuration but don't inject tools into conversations.
Why: Tool definitions consume context tokens. When you don't need a server's tools for a particular task, disabling it avoids unnecessarily blowing up the context. This mirrors similar functionality in Claude Code.
Changes:
{ command, disabled: true }when disabledCI fix: Also fixes a caching bug in
setup-muxaction where restore-key matches (partial cache hits) would skipbun install, causing builds to fail when new dependencies were added. Now runs install on any non-exact cache hit while preserving the Windows optimization that skips bun cache decompression whennode_modulesalready exists.Generated with
mux