Umami MCP vs PhpCodeArcheology — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Umami MCP vs PhpCodeArcheology
In-depth architectural comparison of the Umami MCP and PhpCodeArcheology 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
Umami MCP
Monitoring · Local stdio
Quality: 57/100 (Good) | Auth: API Key required
PhpCodeArcheology
Monitoring · Remote HTTP/SSE
Quality: 63/100 (Good) | Auth: No auth required
Verdict Summary: Choose Umami MCP if you need specialized Monitoring tools running via a local process. Choose PhpCodeArcheology if your workspace requires Monitoring integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Umami MCP when:
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: UMAMI_URL, UMAMI_USERNAME, UMAMI_PASSWORD, UMAMI_API_KEY.
Full-coverage MCP server for Umami Analytics API v2 — 66 tools for websites, stats, sessions, events, reports, users, teams, and realtime monitoring.
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.
Category & Scope
Tools & Capabilities Breakdown
Umami MCP Tools (66)
list_websites
List all tracked websites
get_website
Get website details by ID
create_website
Create a new website
update_website
Update website configuration
delete_website
Delete a website
get_active_visitors
Get current active visitor count
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).
Umami MCP is categorized under Monitoring and uses a local stdio subprocess. In contrast, PhpCodeArcheology belongs to Monitoring using remote streaming HTTP/SSE transport. Select Umami MCP when you need capabilities focused on monitoring and PhpCodeArcheology when you require tools for monitoring.