A side-by-side look at the Vexor and Ontomics MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Vexor for developer tools work as a local process; choose Ontomics for developer tools as a local process. You can also run both side by side in one mcpServers block.
query_concept, locate_concept, describe_symbol.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 59/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 245 | 43 |
| Directory activity | 2 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 19 |
| Full listing | View Vexor | View Ontomics |
No tool names declared yet. Check the project README from the listing page.
query_conceptFind all variants, related concepts, and occurrences of a termlocate_conceptFind the key signatures, classes, and files for a conceptdescribe_symbolGet the signature, docstring, and relationships for a function or classtrace_conceptTrace how a concept flows through the codebase via call chainslist_conceptsList the top domain concepts by frequencylist_conventionsList all detected naming patterns (prefixes, suffixes, conversions)list_entitiesList code entities (classes, functions) filtered by concept, role, or kindcheck_namingCheck an identifier against project conventions; suggests the canonical formsuggest_nameGenerate an identifier name that fits the project's vocabularyvocabulary_healthMeasure convention coverage, naming consistency, and cluster cohesionontology_diffShow new, changed, or removed domain concepts since a git refexport_domain_packExport domain knowledge as portable YAML for use in other reposPaste 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.
{
"mcpServers": {
"scarletkc-vexor": {
"command": "uvx",
"args": [
"vexor"
]
}
}
}
{
"mcpServers": {
"etiennechollet-ontomics": {
"command": "npx",
"args": [
"-y",
"@ontomics/ontomics"
]
}
}
}