PhpCodeArcheology vs CodeMCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
PhpCodeArcheology vs CodeMCP
In-depth architectural comparison of the PhpCodeArcheology and CodeMCP 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
Developer Tools · Remote HTTP/SSE
Quality: 56/100 (Good) | Auth: No auth required
CodeMCP
Developer Tools · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose PhpCodeArcheology if you need specialized Developer Tools tools running via a hosted cloud SSE transport. Choose CodeMCP if your workspace requires Developer Tools 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 Developer Tools domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
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.
Code intelligence MCP server with 80+ tools for semantic code search, impact analysis, call graphs, ownership detection, and architectural understanding. Supports Go, TypeScript, Python, Rust, Java via SCIP indexing.
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 Developer Tools and uses a remote streaming HTTP/SSE transport. In contrast, CodeMCP belongs to Developer Tools using local stdio subprocess. Select PhpCodeArcheology when you need capabilities focused on developer tools and CodeMCP when you require tools for developer tools.