Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

MCP not connected to Github Copilot agent runtime

Open
#118 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github, typescript, vscode

Research direction

Start by reproducing the issue in the reported devcontainer with VS Code 1.130.0 and DebugMCP 2.2.4, then follow the agent selection command and its configuration result. Done means GitHub Copilot retains its selection and can see the MCP tools without raw curl calls.

Written by the indexing model from the issue text.

Description

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
Dominant language
TypeScript
Stars
511
Forks
60
Avg merge
2d 1h
Merged PRs (30d)
18

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/DebugMCP

All issues in microsoft/DebugMCP

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.