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.Context7Upstash's official server providing up-to-date third-party library docs for AI coding assistants
FMRS62 / 100 · C80 / 100 · B
Reliability9 / 2014 / 20
Security and permissions13 / 2016 / 20
Maintenance12 / 2017 / 20
Documentation15 / 2015 / 20
Setup experience13 / 2018 / 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
  • Developers using fast-moving frameworks/libraries worried about the AI suggesting stale code
  • Scenarios wanting zero-config documentation lookup
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)
  • Looking up internal/private codebase documentation (Context7 targets publicly published open-source libraries)
  • Cases needing very high coverage of obscure, niche libraries (coverage depends on what Context7's platform has indexed)
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)
  • Usable without an API key (subject to a free-tier rate limit); CONTEXT7_API_KEY is an optional credential for higher quota
  • Read-only documentation lookup — no code execution or local filesystem access involved
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)
  • The free tier has limited quota — high-frequency use may hit rate limits
  • Documentation content comes from Context7's platform index, so its accuracy and freshness depend on that platform's crawl cadence
Supported clientsGitHub Copilot, GitHub Copilot CLI, Cline, Cursor, Codex, Windsurf, Roo Code, AntigravityClaude Code, VS Code, Cursor, Cline, Amp
Tools162