Hi,
If I understood the documentation correctly the extension launches the mcp server automatically. I have a project running on a devcontainer, with the extension installed, and my github copilot agent says the mcp is not available in its environment (it does not see its tools, etc) but it can manually access it by doing raw curl calls to it (So the server is running). I have run the agent selection command multiple times, enabled the Github Copilot everytime, I see the successfull configuration pop up appearing but the agent still says it does not have access to the MCP. If I run the agent selection again I don't see the github copilot selected, like if the configuration is not being saved.
Version details:
VSCode
Version: 1.130.0
Commit: 1b6a188127eeaf9194f945eb6eb89a657e93c54c
Date: 2026-07-22T14:55:04Z
Electron: 42.6.0
ElectronBuildId: 14623276
Chromium: 148.0.7778.280
Node.js: 24.18.0
V8: 14.8.178.38-electron.0
OS: Linux x64 6.14.0-37-generic
DebugMCP
dentifier
ozzafar.debugmcpextension
Version
2.2.4
Last Updated
23 minutes ago
Hi,
If I understood the documentation correctly the extension launches the mcp server automatically. I have a project running on a devcontainer, with the extension installed, and my github copilot agent says the mcp is not available in its environment (it does not see its tools, etc) but it can manually access it by doing raw curl calls to it (So the server is running). I have run the agent selection command multiple times, enabled the Github Copilot everytime, I see the successfull configuration pop up appearing but the agent still says it does not have access to the MCP. If I run the agent selection again I don't see the github copilot selected, like if the configuration is not being saved.
Version details:
VSCode
DebugMCP