Start-Copilot: map copilot --enable-mcp-server (re-enable a settings-disabled MCP server for one run)

[shmuelie]

Summary

Start-Copilot has an -EnableMcpServer parameter, but it only overrides the launcher's own path-glob autoConnect policy — it affects which --disable-mcp-server flags get emitted for the current directory. It does not emit the Copilot CLI's native --enable-mcp-server, so there is currently no way through Start-Copilot to re-enable, for a single run, an MCP server that is disabled in the user's persistent ~/.copilot settings.

Feature

copilot --enable-mcp-server <server-name> enables an MCP server that is disabled in settings, for this run only (nothing is persisted). This is a distinct source of "disabled" from Start-Copilot's in-launcher autoConnect path-glob policy.

Observed on GitHub Copilot CLI 1.0.81.

Proposal / acceptance criteria

• Provide a way to emit the native --enable-mcp-server <name> for servers disabled in the CLI's own settings, while preserving the existing autoConnect-override behavior.
• Resolve the naming overlap clearly: either extend -EnableMcpServer to also emit --enable-mcp-server, or add a distinct parameter. Document the two different "disabled" sources (persistent settings vs. Start-Copilot's path-glob autoConnect policy) so the behavior is unambiguous.
• Comment-based help, README (the MCP autoConnect section), and an [Unreleased] CHANGELOG.md entry.
• Tests asserting the native flag is emitted for a settings-disabled server without disturbing the autoConnect/--disable-mcp-server computation.