npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

vscode-debug-mcp

v0.1.0

Published

MCP server that lets AI agents control the VS Code debugger — breakpoints, stepping, call stacks, variables, and expression evaluation

Readme

vscode-debug-mcp

MCP server that lets AI agents control the VS Code debugger — set breakpoints, launch/attach debug sessions, step through code, inspect call stacks and variables, and evaluate expressions in the paused frame.

Works as a pair with the Debug MCP Bridge VS Code extension:

AI Agent ──(stdio MCP)──> vscode-debug-mcp ──(HTTP 127.0.0.1:7779)──> VS Code extension ──> vscode.debug API

Setup

  1. Install the Debug MCP Bridge extension in VS Code (Marketplace / Open VSX: laststance.vscode-debug-mcp-bridge). It auto-starts and binds 127.0.0.1:7779.
  2. Register this server with your MCP client:

Claude Code (~/.claude.json or project .mcp.json) / Cursor (~/.cursor/mcp.json):

{
  "mcpServers": {
    "vscode-debugger": {
      "command": "npx",
      "args": ["-y", "vscode-debug-mcp"]
    }
  }
}

Codex (~/.codex/config.toml):

[mcp_servers.vscode-debugger]
command = "npx"
args = ["-y", "vscode-debug-mcp"]

If the bridge runs on a custom port, set VSCODE_DEBUG_PORT in the server's env.

Tools

| Tool | Description | |------|-------------| | set_breakpoint | Set a breakpoint (optional condition / hit count / logpoint) | | remove_breakpoint | Remove breakpoints at a file:line | | list_breakpoints | List all breakpoints | | launch_debug | Start a debug session (inline config or launch.json name) | | stop_debugging | Stop the active debug session | | debug_continue | Continue execution | | debug_step_over | Step over next statement | | debug_step_into | Step into function call | | debug_step_out | Step out of current function | | debug_pause | Pause execution | | get_debug_state | Get current state (inactive/running/stopped) | | get_call_stack | Get call stack frames | | get_variables | Get variables in scope | | evaluate_expression | Evaluate an expression in the paused frame | | expand_variable | Expand object/array children by variablesReference | | get_threads | List active threads |

Prefer zero configuration? The bridge extension also accepts plain HTTP (curl 127.0.0.1:7779) — see the endpoint table.

License

MIT © Laststance.io