VSC MCP Diagnostics Server

Provides real-time access to diagnostics from VS Code and MCP-enabled tools for AI-assisted development.

typescript

19

GitHub Stars

typescript

Language

5 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "newbpydev-mcp-diagnostics-extension": {
      "command": "node",
      "args": [
        "scripts/mcp-server.js"
      ],
      "env": {
        "NODE_ENV": "production",
        "MCP_DEBUG": "false"
      }
    }
  }
}

You can expose real-time diagnostic data from your code editor to MCP-enabled tools and AI agents. This MCP Diagnostics Extension bridges your editor’s diagnostic stream with the Model Context Protocol, so your AI tools can react to errors, warnings, and linter feedback as you work, across multi-workspace projects and diverse environments.

How to use

You use the MCP Diagnostics Extension by connecting an MCP client to the local MCP server that the extension runs. Once connected, your client can query and subscribe to diagnostic data, including errors and warnings, filtered by file, severity, source, and workspace. You can access three core capabilities: fetch all matching problems, fetch problems for a single file, and obtain a summary of workspace diagnostics. Real-time notifications keep your AI tools synchronized with any changes in diagnostics as you edit or save files.

How to install

Prerequisites: Node.js must be available on your system. You should also have a compatible editor environment that can host MCP clients.

Step-by-step commands to install and run the MCP Diagnostics Extension in a development setup:

# 1) Clone the repository
git clone https://github.com/newbpydev/mcp-diagnostics-extension.git
cd mcp-diagnostics-extension

# 2) Install dependencies
npm install

# 3) Compile TypeScript
npm run compile

# 4) Launch Extension Development Host (in VS Code)
code --extensionDevelopmentPath=.

Configuration and usage notes

You can configure the MCP client to connect to the local MCP server exposed by the extension. The server runs as a standalone Node.js process and provides live diagnostic data. Use the provided configuration example to wire your MCP client to the server, then start querying tools to retrieve diagnostic data.

Security and reliability notes

The setup supports atomic writes and backup creation before making changes to configuration. It includes runtime safeguards to gracefully recover from errors and maintain stable operation across platforms.

Troubleshooting tips

If diagnostics aren’t appearing, verify that your editor is producing diagnostics and that the MCP client is connected to the local server. Check the status in the client and look for any error messages related to connection or permission issues.

Available tools

getProblems

Fetch all diagnostics with optional filters such as file, severity, workspace, and source, with pagination support.

getProblemsForFile

Retrieve diagnostics for a specific file path.

getWorkspaceSummary

Obtain a summary of workspace diagnostics including counts by severity and source.