MCP servers from --additional-mcp-config are removed during startup reconciliation in 1.0.81-11
まだ誰も着手していません。
- 主要言語
- Shell
- スター
- 11.2k
- フォーク
- 1.9k
- 平均マージ
- 14時間 16分
- マージ済み PR(30日)
- 6
説明
Describe the bug
Copilot CLI initially discovers and connects an MCP server supplied through --additional-mcp-config. Later during startup, a second MCP reconciliation computes a configuration that no longer contains the additional server, cancels it, and emits session.mcp_server_removed.
This is not only a /mcp show display problem: after reconciliation, the server's tools are unavailable.
Affected version
1.0.81-11
The behavior was not observed on another machine running 1.0.81-3. This is currently version correlation rather than a controlled same-machine bisect.
Steps to reproduce
- Create
mcp.jsonusing a public MCP endpoint:
{
"mcpServers": {
"context7-test": {
"type": "http",
"url": "https://mcp.context7.com/mcp",
"tools": ["*"]
}
}
}
- Launch Copilot with detailed logging:
copilot --log-level all --additional-mcp-config '@.\mcp.json'
- Wait for startup and inspect the server:
/mcp show context7-test
- Check the debug log for MCP reconciliation and removal events.
Actual behavior
The server appears in the initial MCP configuration and begins connecting. A subsequent reconciliation changes the MCP graph from a signature containing the additional server to one that omits it:
MCP host start (trigger=startup, ...)
...
Service initialized as client
...
mcp apply_session_settings
mcp discover_and_start_root
previous_signature=<contains context7-test>
signature=<does not contain context7-test>
mcp discover_and_start_root: incremental reconcile path
...
session.mcp_server_removed
The server connection is cancelled and its tools are not available afterward.
The logs also report that configured MCP registries permit all servers, so the removal does not appear to be an intentional registry-policy block.
Expected behavior
MCP servers supplied through --additional-mcp-config should remain in the effective MCP graph for the lifetime of the session. Plugin activation, extension loading, managed-settings application, and other startup reconciliation should preserve them.
Additional context
OS: Windows
Architecture: ARM64
Shell: PowerShell 7.6.5
Terminal: Windows Terminal
Affected version: 1.0.81-11
Comparison version without observed failure: 1.0.81-3
The public Context7 configuration is a proposed minimal reproduction and has not yet been independently confirmed to trigger the same race.
コントリビューションガイド
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
調査の方向性
提供された mcp.json と copilot --log-level all --additional-mcp-config '@.\mcp.json' を使って再現し、その後、mcp apply_session_settings と mcp discover_and_start_root 周辺の起動ログを調査してください。シグネチャを変更する増分リコンシリエーションを追跡し、追加サーバーが起動後も実効 MCP グラフに残り、そのツールが引き続き利用可能であることを確認してください。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- powershell
- 領域
- cli
- issue の種類
- バグ
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 活発さ
- 活発
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 48/100