MCP Catalogs
Home

mcp-diagnostics-extension

by newbpydev·22·Score 42

VS Code extension that exposes diagnostic problems via MCP for AI agents to access in real-time.

developer-toolsai-llmmonitoring
5
Forks
11
Open issues
7 mo ago
Last commit
2d ago
Indexed

Overview

The MCP Diagnostics Extension bridges VS Code's diagnostic system with the Model Context Protocol, enabling AI agents to access code problems in real-time. It works with any VS Code diagnostic provider including TypeScript, ESLint, and custom linters. The extension features production-quality architecture with 810 passing tests and 97.99% code coverage, along with advanced features like real-time notifications, performance monitoring, and automatic server registration.

Try asking AI

After installing, here are 5 things you can ask your AI assistant:

you:AI agents can access real-time TypeScript and ESLint errors to provide contextual debugging assistance
you:Development teams can integrate diagnostics into their AI-powered workflows for faster issue resolution
you:IDE extensions can leverage MCP to share diagnostic information across development tools
you:What diagnostic providers does this extension support?
you:How do I verify the extension is working?

When to choose this

Choose this if you're using VS Code and want your AI assistants to have real-time visibility into your code diagnostics without manual intervention.

When NOT to choose this

Don't choose this if you need diagnostic access from IDEs other than VS Code, or if you require write capabilities to diagnostic information (this is read-only).

Tools this server exposes

3 tools extracted from the README
  • getProblems

    Get all diagnostic problems with filtering capabilities

  • getProblemsForFile

    Get diagnostic problems for a specific file

  • getWorkspaceSummary

    Get workspace-wide diagnostic statistics and summary

Comparable tools

vscode-mcpmcp-file-systemcursor-ide-integration

Installation

Installation

From VS Code Marketplace

  1. Open VS Code
  2. Go to Extensions (Ctrl+Shift+X / Cmd+Shift+X)
  3. Search for "MCP Diagnostics Extension"
  4. Click Install
  5. Reload VS Code if prompted

From Source

git clone https://github.com/newbpydev/mcp-diagnostics-extension.git
cd mcp-diagnostics-extension
npm install
npm run compile
code --extensionDevelopmentPath=.

Claude Desktop Configuration

Add to your Claude Desktop config.json:

{
  "mcpServers": {
    "vscode-diagnostics": {
      "command": "node",
      "args": ["scripts/mcp-server.js"],
      "cwd": "/path/to/mcp-diagnostics-extension",
      "env": {
        "NODE_ENV": "production"
      }
    }
  }
}

FAQ

What diagnostic providers does this extension support?
The extension works with any VS Code diagnostic provider including TypeScript, ESLint, custom linters, and any extension that registers with VS Code's diagnostic system.
How do I verify the extension is working?
Look for the status bar item showing $(bug) MCP: XE YW where X is the error count and Y is the warning count. You can also check the server status through the command palette with 'MCP Diagnostics: Show Status'.

Compare mcp-diagnostics-extension with

GitHub →

Last updated · Auto-generated from public README + GitHub signals.