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

Standalone MCP Service

Open
#31 0 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript, vscode
Domain
devtools

Research direction

Start by inspecting how the MCP server is bundled in the VSCode extension and how DebugMCP core logic reaches debuggers through DAP. Determine the boundaries for a standalone MCP server and how language-specific debuggers would be managed without VSCode. Done means the service can provide the MCP abilities independently of VSCode with a defined debugger integration approach.

Written by the indexing model from the issue text.

Description

Currently the MCP server is bundled in the VSCode extension. This forces users to use VSCode for the MCP abilities.
I suggest to create another offering of the DebugMCP core logic, that will be served as a standalone MCP server.
One challenge I see here is how to manage the different debuggers, previously easy to reach via DAP against VSCode (since the common pattern is that users install a language-specific extensions that adds a debugger under the hood, which then VSCode exposes via DAP).

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.