Phpgraph vs Ovecc — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Phpgraph vs Ovecc
In-depth architectural comparison of the Phpgraph and Ovecc 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
Phpgraph
Developer Tools · Local stdio
Quality: 47/100 (Fair) | Auth: No auth required
Ovecc
Developer Tools · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Phpgraph if you need specialized Developer Tools tools running via a local process. Choose Ovecc 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?
P
Choose Phpgraph when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Persistent repository index of files, imports, symbols, and calls, MCP access to the CLI command surface over stdio, Architecture contracts with dependency and complexity rules.
Start here: Composer stack, namespace tree with layers, bounded contexts, layer-rule violations, messages, HTTP routes (each with method, path, controller and file up to 30, else grouped by path prefix), services, and what the graph cannot see.
query_graph
Find the code about a topic when you do not know the class names, by the words of their names (validated finds `Validator`), with the classes of the feature around the ones it names. A question about routes (*"mooc courses routes"*, *"GET /courses"*) returns the matching routes and their controller…
outline
Before explaining a feature: its structural outline, enough to read only the few files with non-obvious logic. The classes it is made of, by namespace and layer, with the first sentence of their docblock, their public signatures, constants and enum cases; the interfaces and base classes around it w…
get_node
Read one class, method, route or channel with all its relations; tests using it are counted by module.
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).
Phpgraph is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Ovecc belongs to Developer Tools using local stdio subprocess. Select Phpgraph when you need capabilities focused on developer tools and Ovecc when you require tools for developer tools.
See what uses a node (`in`) or what it depends on (`out`).
impact_of
Before a change: every class that depends on a class or method, nearest first, with the lines of the calls; callers through the interface it implements; code depending on the state it writes; the routes reaching it, with each chain; and the tests to run, found through test helpers. It flags the cla…
shortest_path
See how two pieces of code are connected.
god_nodes
Find the hubs most of the code depends on.
Ovecc Tools (6)
Persistent repository index of files, imports, symbols, and calls
MCP access to the CLI command surface over stdio
Architecture contracts with dependency and complexity rules
Impact, cycle, coupling, and hotspot analysis
Security, audit, dead-code, duplicate-code, and health checks
Text, JSON, NDJSON, Markdown, SARIF, and Code Climate output