fix: default MCP tools to [*] when not specified#352
Open
fix: default MCP tools to [*] when not specified#352
Conversation
Matches copilot-cli behavior where missing tools field defaults to all tools enabled. This allows MCP configs created outside Cooper to work without explicit tools array.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Problem
MCP servers configured without a tools field would fail to work in Cooper, even though they worked fine in copilot-cli.
Root Cause
The copilot-cli defaults missing tools to all tools enabled. Cooper was passing the config through as-is, which the SDK rejected for missing the required tools field.
Solution
Updated readMcpConfig() in src/main/main.ts to default tools to all tools for any server that doesn't specify it, matching copilot-cli behavior.
Testing