OpenDealer MCP Server vs Codegraphcontext
A side-by-side look at the OpenDealer MCP Server and Codegraphcontext MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose OpenDealer MCP Server for developer tools work; choose Codegraphcontext 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?
OChoose OpenDealer MCP Server when
- You need dedicated capabilities in the Developer Tools domain.
Choose Codegraphcontext 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 | O OpenDealer MCP Server | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 37/100 · Fair | 59/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | 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 | — | 4,352 |
| Directory activity | 1 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View OpenDealer MCP Server | View Codegraphcontext |
Tools & capabilities
OpenDealer MCP Server tools
No tool names declared yet. Check the project README from the listing page.
Codegraphcontext 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.
OpenDealer MCP Server
No confirmed install command for OpenDealer MCP Server yet — follow the setup steps linked from its listing page rather than a guessed package name.
Codegraphcontext
{
"mcpServers": {
"shashankss1205-codegraphcontext": {
"command": "uvx",
"args": [
"kuzu"
]
}
}
}