M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionDebugMCPGift your VS Code agent a real debugger: breakpoints, stepping, inspection.GitHub MCP ServerGitHub's official MCP server for managing repos, issues, PRs, and workflows via natural language
FMRS62 / 100 · C76 / 100 · B
Reliability9 / 2013 / 20
Security and permissions13 / 2014 / 20
Maintenance12 / 2018 / 20
Documentation15 / 2017 / 20
Setup experience13 / 2014 / 20
Best for
  • Developers using AI coding agents in VS Code who want real debugging capability
  • Scenarios needing automated root-cause analysis instead of reading logs
  • Users working in VS Code Remote SSH, Codespaces, or WSL remote environments
  • Teams wanting one unified debugging tool across many programming languages
  • Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
  • Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
Not for
  • Users who do not use VS Code or any MCP-compatible AI assistant
  • Scenarios that need to expose the debugging service to other machines on a network (loopback-only by default; rebinding carries unauthenticated risk)
  • Users who will not install the corresponding VS Code debugger extension for their language
  • Users expecting an externally hosted or cloud-based debugging service (the extension runs locally only)
  • Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
  • Environments with strict network isolation for private repos that can't reach the official remote endpoint
Required permissions
  • Listen on an HTTP port on loopback addresses (127.0.0.1 and ::1), default 3001, configurable via debugmcp.serverPort
  • Read the source files being debugged and any .vscode/launch.json configuration in the project
  • Call the VS Code Debug API to start/stop debug sessions, set breakpoints, and step through code
  • Read variable values in debug context and evaluate expressions (with secret redaction applied)
  • Install the debug-live skill file into standard skills directories (~/.agents/skills/, plus ~/.copilot/skills/ when present)
  • A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
  • Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
Risks and side effects
  • The MCP endpoint is unauthenticated by default, so any local process that can reach the loopback port can call powerful debugger primitives such as evaluate_expression
  • Changing debugmcp.bindHost to 0.0.0.0 or a LAN address exposes the unauthenticated debugger to anything that can route to that address
  • Evaluating expressions through the debugger can have side effects depending on the debugged program, and agent auto-approval reduces human confirmation
  • Variable redaction relies on names and credential shapes, so it can miss secrets; null-ish values are deliberately not redacted, which may leak sensitive data in edge cases
  • The extension modifies AI assistant MCP registration configuration (with a prompt)
  • Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
  • In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
Supported clientsGitHub Copilot, GitHub Copilot CLI, Cline, Cursor, Codex, Windsurf, Roo Code, AntigravityClaude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains IDEs, Zed, Amp
Tools1615