PhpCodeArcheology vs Roslyn Codelens MCP | AllMCPs
Side-by-Side Model Context Protocol Comparison
PhpCodeArcheology vs Roslyn Codelens MCP
In-depth architectural comparison of the PhpCodeArcheology and Roslyn Codelens MCP 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
Roslyn Codelens MCP
Monitoring · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Verdict Summary: Choose PhpCodeArcheology if you need specialized Monitoring tools running via a local process. Choose Roslyn Codelens MCP 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: No auth required (Free / Open Source).
Primary tools included: Roslyn-based semantic symbol analysis, Call graphs and type hierarchy inspection, Diagnostics, code fixes, and refactoring actions.
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.
⃣ 🏠 🍎 🪟 🐧 - Roslyn-based MCP server with 22 semantic code intelligence tools for .NET. Type hierarchies, call graphs, DI registrations, diagnostics, code fixes, complexity metrics, and more. Sub-millisecond lookups via pre-built indexes.
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, Roslyn Codelens MCP belongs to Monitoring using local stdio subprocess. Select PhpCodeArcheology when you need capabilities focused on monitoring and Roslyn Codelens MCP when you require tools for monitoring.