PhpCodeArcheology vs Fastmcp Sonarqube Met… | AllMCPs
Side-by-Side Model Context Protocol Comparison
PhpCodeArcheology vs Fastmcp Sonarqube Metrics
In-depth architectural comparison of the PhpCodeArcheology and Fastmcp Sonarqube Metrics MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
PhpCodeArcheology
Monitoring · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Fastmcp Sonarqube Metrics
Monitoring · Local stdio
Quality: 47/100 (Fair) | Auth: API Key required
Verdict Summary: Choose PhpCodeArcheology if you need specialized Monitoring tools running via a local process. Choose Fastmcp Sonarqube Metrics if your workspace requires Monitoring integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose PhpCodeArcheology when:
You need dedicated capabilities in the Monitoring domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You need dedicated capabilities in the Monitoring domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: SONARQUBE_URL, SONARQUBE_TOKEN, TRANSPORT.
Primary tools included: Expose SonarQube data through FastMCP, Retrieve current and historical project metrics, Collect paginated component-tree metrics.
PHP static analysis MCP server for architecture and maintainability. 11 tools exposing 60+ code quality metrics, problem detection, refactoring priorities, dependency graphs, git hotspots, test coverage, and impact analysis. Installable via Composer.
A Model Context Protocol (MCP) server that provides a set of tools for retrieving information about SonarQube projects like metrics (actual and historical), issues, health status.
Category & Scope
Tools & Capabilities Breakdown
PhpCodeArcheology Tools (11)
get_health_score
Overall code health score, grade, and project statistics
get_problems
Code quality problems, filterable by severity and type
get_metrics
Detailed metrics for a specific class, file, or function
get_hotspots
Git hotspots ranked by churn × complexity
get_refactoring_priorities
Ranked refactoring candidates with recommendations
get_dependencies
Class dependency analysis (incoming/outgoing)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
PhpCodeArcheology is categorized under Monitoring and uses a local stdio subprocess. In contrast, Fastmcp Sonarqube Metrics belongs to Monitoring using local stdio subprocess. Select PhpCodeArcheology when you need capabilities focused on monitoring and Fastmcp Sonarqube Metrics when you require tools for monitoring.