breakpoint-mcp-tools-guide

Manage VS Code breakpoints and debug sessions through Copilot MCP tools.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/fangfuzha/vscode-debug-tools-for-copilot --skill breakpoint-mcp-tools-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: breakpoint-mcp-tools-guide
Source: https://github.com/fangfuzha/vscode-debug-tools-for-copilot/tree/main/src/lm/skills/breakpoint-mcp-tools-guide
Command: npx skills add https://github.com/fangfuzha/vscode-debug-tools-for-copilot --skill breakpoint-mcp-tools-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps Copilot choose and call the extension's breakpoint and debug-session MCP tools correctly so users can inspect, modify, and control VS Code breakpoints and debug sessions without ambiguity or parameter errors.

Core Features & Use Cases

  • Tool selection guidance: Recommends which MCP tool to call first (for example, list_breakpoints or list_debug_sessions) based on the user's intent.
  • Parameter and resolution rules: Explains filePath vs workspaceFolderPath, functionName, 1-based line/column semantics, sessionId usage, and list-first discovery for ambiguous targets.
  • Recommended workflows: Stepwise patterns for listing state, updating by key, using update_breakpoint vs add/remove, and controlling debug sessions (pause/continue/step/restart).
  • Use case: When a user asks to add or remove breakpoints across a multi-root workspace, the guide ensures Copilot collects the correct workspaceFolderPath, resolves the target file path, and chooses the appropriate add_source_breakpoint or remove_breakpoint call.

Quick Start

Ask Copilot to list all breakpoints in the workspace and then specify the exact add, update, or remove action including filePath or key and a 1-based line number.

Frequently Asked Questions about breakpoint-mcp-tools-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage VS Code breakpoints with Copilot?

To manage VS Code breakpoints with Copilot, use MCP tools to list, add, remove, enable, or disable breakpoints by specifying the filePath and 1-based line number to avoid parameter errors.

How does Copilot resolve debug sessions and breakpoints in a multi-root workspace?

Copilot resolves breakpoints in a multi-root workspace by requiring the workspaceFolderPath and target filePath. It uses a list-first discovery approach to identify ambiguous targets before applying add, update, or remove actions.

Can I control debug sessions like pause and continue through VS Code Copilot?

Yes, you can control debug sessions through Copilot by driving pause, continue, step, and restart operations. You need to provide the optional sessionId to target the correct active debug session.

What is the best way to update an existing breakpoint in VS Code using MCP tools?

The best way to update an existing breakpoint is to use the update_breakpoint MCP tool rather than removing and re-adding it, ensuring you pass the correct key and precise 1-based line and column parameters.

Why does adding a source breakpoint fail when using Copilot in VS Code?

Adding a source breakpoint fails when the filePath or workspaceFolderPath is incorrect. Copilot requires accurate parameter resolution including 1-based line semantics and list-first discovery to avoid errors.

Do I need launch configurations to query breakpoints per file in VS Code?

You do not need active launch configurations to query per-file breakpoints. Copilot can list breakpoints across single or multi-root workspaces by resolving the filePath, but active sessions require a sessionId.