Does this skill require Docker to be running?

While it can audit local IDE processes independently, Docker is required to inspect MCP containers and perform the cross-reference diagnostics.

Can it fix port mismatches automatically?

No, the skill is read-only for safety. It generates the necessary Docker or configuration commands to fix issues, but the user must review and execute them.

What IDEs does this skill support?

It automatically identifies embedded servers for VS Code, IntelliJ, and Eclipse by parsing process command strings during the collection phase.

Why am I seeing an 'Orphaned container' warning?

This occurs when multiple MCP containers are running with the same configuration, which often happens if Claude Code sessions are not closed properly, leading to resource waste.

How does this improve my Claude Code workflow?

It eliminates the 'black box' problem of AI agents being unable to reach local analysis servers, ensuring that commands like 'analyze_file_list' work reliably.

SonarQube Environment Diagnostic

Name: SonarQube Environment Diagnostic
Author: denniscalazans

bydenniscalazans

•

Security & Testing

Diagnoses and audits local SonarQube infrastructure by mapping IDE embedded servers to MCP container port configurations.

This skill provides a comprehensive health check for your local SonarQube ecosystem, identifying connectivity gaps between your IDE and Claude Code. It automatically detects listening ports for VS Code, IntelliJ, and Eclipse, cross-references them with active MCP Docker containers, and flags critical issues like port mismatches or orphaned containers. By providing clear diagnostics and corrective commands, it ensures your AI agent can successfully communicate with local analysis tools without silent failures or resource waste.

Key Features

013 GitHub stars

02Automated detection of IDE embedded servers (VS Code, IntelliJ, Eclipse)

03Read-only system inspection with suggested corrective commands

04Diagnostic flagging for port mismatches and unconnected IDEs

05Real-time mapping of SONARQUBE_IDE_PORT environment variables

06Identification of orphaned or redundant MCP containers

Use Cases

01Auditing and cleaning up orphaned Docker containers from previous sessions

02Managing multi-IDE environments to ensure correct port wiring

03Troubleshooting silent connection failures between Claude and SonarQube

Key Features

013 GitHub stars

02Automated detection of IDE embedded servers (VS Code, IntelliJ, Eclipse)

03Read-only system inspection with suggested corrective commands

04Diagnostic flagging for port mismatches and unconnected IDEs

05Real-time mapping of SONARQUBE_IDE_PORT environment variables

06Identification of orphaned or redundant MCP containers

Use Cases

01Auditing and cleaning up orphaned Docker containers from previous sessions

02Managing multi-IDE environments to ensure correct port wiring

03Troubleshooting silent connection failures between Claude and SonarQube