github / github/copilot-cli

MCP servers from --additional-mcp-config are removed during startup reconciliation in 1.0.81-11

Abierto
#4,636 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

triage
Lenguaje dominante
Shell
Estrellas
11.2k
Forks
1.9k
Merge medio
14 h 16 min
PR fusionados (30 d)
6

Descripción

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

  1. Create mcp.json using a public MCP endpoint:
{
  "mcpServers": {
    "context7-test": {
      "type": "http",
      "url": "https://mcp.context7.com/mcp",
      "tools": ["*"]
    }
  }
}
  1. Launch Copilot with detailed logging:
copilot --log-level all --additional-mcp-config '@.\mcp.json'
  1. Wait for startup and inspect the server:
/mcp show context7-test
  1. 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.

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Línea de trabajo

Reproduce el problema con el mcp.json proporcionado y copilot --log-level all --additional-mcp-config '@.\mcp.json', y luego inspecciona los registros de inicio alrededor de mcp apply_session_settings y mcp discover_and_start_root. Sigue la reconciliación incremental que cambia la firma y verifica que el servidor adicional permanezca en el grafo MCP efectivo y que sus herramientas sigan disponibles después del inicio.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
powershell
Área
cli
Tipo de issue
Error
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Activo
Claridad
Bastante claro
Aptitud para principiantes
48/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.