Make MCP configuration default in init command, add --no-mcp flag #7001
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.
The
initcommand now enables MCP (Model Context Protocol) configuration by default, replacing the opt-in--mcpflag with an opt-out--no-mcpflag. The--mcpflag is kept for backward compatibility but hidden from help.Changes
--no-mcpflag to skip MCP setup, kept--mcpflag hidden for backward compatibilitygh aw initnow creates.vscode/mcp.jsonand.github/workflows/copilot-setup-steps.ymlautomatically--mcpflag still works but is hidden from--helpoutputTestInitRepositoryWithNoMCPandTestInitRepositoryWithMCPBackwardCompatibilityExample
The implementation handles both flags with
--mcptaking precedence when explicitly set for backward compatibility.Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.