getProblemsLABSCO SUMMARY
The agent sees the same errors you do, at the same time.
The gap it closes is specific: an assistant suggesting a fix while blind to the compiler's actual complaint is guessing. Push notifications on change matter as much as the query tools — the agent finds out an edit introduced three new errors without being asked to check. Filtering by source is the practical one, since separating TypeScript errors from ESLint warnings is usually the first thing you want.
What it is
A VS Code extension that exposes the editor's diagnostics over MCP. Whatever appears in the Problems panel — compiler errors, ESLint warnings, any language server's output — becomes queryable, so an agent stops asking you to paste error messages.
What you get
- getProblems returns diagnostics filtered by filePath, severity (Error, Warning, Information or Hint), workspaceFolder and source, with limit and offset for paging
- getProblemsForFile returns everything for one absolute file path
- getWorkspaceSummary returns totals grouped by severity, source or workspace folder
- Each problem carries its file path, severity, message, exact range, source and code
- Resources at diagnostics://summary, diagnostics://file/{encodedFilePath} and diagnostics://workspace/{encodedWorkspaceName} expose the same data
- A problemsChanged notification is pushed to connected clients when diagnostics change
- A colour-coded status bar shows the current error and warning counts at a glance
- Diagnostic events are debounced, at 300 milliseconds by default
Requirements
VS Code 1.96.0 or newer — installed from the Marketplace, from a .vsix release, or built from source with Node.js 22. It registers itself as an MCP server automatically on activation. Settings cover the server port (6070 by default), the debounce interval, and maxProblemsPerFile, which defaults to 1000.
Setup effort
Build from source — git clone https://github.com/newbpydev/mcp-diagnostics-extension.git
USE CASES
Fixing errors without pasting them
The agent reads the Problems panel directly, with the exact range and code.
Judging how bad it is right now
Totals grouped by severity, source or workspace folder.
Separating compiler errors from lint noise
Filter by source and severity rather than reading a mixed list.
Catching what a change just broke
Diagnostics changes are pushed to the client as they happen.
3 tools
Listed in project docs. Your client may show a different list.
getProblemsForFilegetWorkspaceSummaryBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
node on PATH
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
From VS Code Marketplace (Recommended)
In VS Code open Extensions (Ctrl+Shift+X / Cmd+Shift+X), search for "MCP Diagnostics Extension", click Install and reload VS Code if prompted. It activates and registers itself as an MCP server.
From Source (Development)
git clone https://github.com/newbpydev/mcp-diagnostics-extension.git
cd mcp-diagnostics-extension
npm install
npm run compileThe client configs below start scripts/mcp-server.js from this checkout.
MCP Clients
VS Code
{
"servers": {
"vscode-diagnostics": {
"command": "node",
"args": [
"scripts/mcp-server.js"
],
"cwd": "<YOUR_PATH_TO_MCP_DIAGNOSTICS_EXTENSION>",
"env": {
"NODE_ENV": "production",
"MCP_DEBUG": "false"
}
}
}
}<YOUR_PATH_TO_MCP_DIAGNOSTICS_EXTENSION> is the folder you cloned and built above.
Cursor
{
"mcpServers": {
"vscode-diagnostics": {
"command": "node",
"args": [
"scripts/mcp-server.js"
],
"cwd": "<YOUR_PATH_TO_MCP_DIAGNOSTICS_EXTENSION>",
"env": {
"NODE_ENV": "production",
"MCP_DEBUG": "false"
}
}
}
}<YOUR_PATH_TO_MCP_DIAGNOSTICS_EXTENSION> is the folder you cloned and built above.