Codegraphcontext MCP vs Ovecc
A side-by-side look at the Codegraphcontext MCP and Ovecc MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Codegraphcontext MCP for developer tools work over a hosted endpoint; choose Ovecc for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Codegraphcontext MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
repo_graph_query, symbol_impact_path, branch_context_pack.
Choose Ovecc when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 48/100 · Fair | 47/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 3 |
| Directory activity | 1 views 0 installs 0 upvotes | 6 views 2 installs 1 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Codegraphcontext MCP | View Ovecc |
Tools & capabilities
Codegraphcontext MCP tools 4
repo_graph_querysymbol_impact_pathbranch_context_packdependency_hotspot_report
Ovecc tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Codegraphcontext MCP
{
"mcpServers": {
"codegraphcontext-mcp": {
"url": "https://codegraphcontext.clauxel.com/mcp"
}
}
}
Ovecc
{
"mcpServers": {
"ovecc": {
"command": "npx",
"args": [
"-y",
"ovecc"
]
}
}
}
Frequently asked questions
Codegraphcontext MCP is categorized under Developer Tools and uses a remote HTTP/SSE transport. Ovecc belongs to Developer Tools and uses a local stdio subprocess. Pick Codegraphcontext MCP for developer tools work and Ovecc for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Codegraphcontext MCP has no declared pricing — check the project's own site. Ovecc is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add codegraphcontext-mcp and ovecc as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Codegraphcontext MCP has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Ovecc has 47/100 (Fair) with 6 views, 2 installs and 3 GitHub stars.