Skip to main content
Glama
EtienneChollet

ontomics

by EtienneChollet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

Related Servers

Alternatives to ontomics

  • Code-Index-MCP

    Consiliency
    A
    license
    Not graded
    quality
    A
    maintenance
    Local-first code indexer that provides deep code understanding for Claude and other LLMs with symbol/text search across 48+ languages, semantic search capabilities, and real-time index updates through the Model Context Protocol.
    58
    MIT

Related Servers

  • codecortex

    rushikeshmore
    A
    license
    Not graded
    quality
    D
    maintenance
    Persistent codebase knowledge layer for AI agents. Pre-digests codebases into structured knowledge (symbols, dependency graphs, co-change patterns, architectural decisions) and serves via MCP. 28 languages, 14 tools, ~85% token reduction.
    12 npm
    8
    MIT

  • blastmap

    manorfm
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI coding agents to index codebases into a queryable knowledge model and ask for the smallest architectural surface a task likely touches, with evidence, confidence, and freshness, via MCP tools.
    Apache 2.0

  • RepoMap

    TusharKarkera22
    A
    license
    Not graded
    quality
    D
    maintenance
    Provides AI assistants with a structured, token-efficient map of a codebase's symbols, dependencies, and relationships via MCP tools like overview, query, and impact analysis.
    8
    MIT

  • ChunkHound

    chunkhound
    A
    license
    A
    quality
    A
    maintenance
    A local-first codebase intelligence tool that enables AI assistants to research codebases using semantic search, multi-hop relationship discovery, and structural parsing. It allows users to extract architectural patterns and institutional knowledge across 30+ programming languages through an MCP-compatible interface.
    2
    613 PyPI
    1,433
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.9/5.0

Scored across 19 tools

Disambiguation3/5

The tools are mostly distinct in intent, but several clusters are easy to confuse: describe_file vs describe_symbol vs describe_logic, query_concept vs locate_concept vs list_concepts vs concept_map, and type_flows vs trace_type. An agent would need to read descriptions carefully to pick the right one.

Naming Consistency3/5

Most tools follow a verb_noun pattern (query_concept, describe_file, trace_concept), but several use noun-ish names like type_flows, ontology_diff, concept_map, and vocabulary_health. The naming is descriptive and snake_case throughout, but the verb placement is inconsistent.

Tool Count3/5

19 tools is on the heavy side and there is functional overlap in the concept/type/naming clusters. However, the domain is broad enough that most tools have a distinct purpose, so the count is defensible but borderline.

Completeness4/5

The toolset covers file/symbol/logic description, concept queries, type flow tracing, naming-convention analysis, ontology diffing, and context generation. It's read-only and lacks direct code editing or ontology update tools, but for analysis-oriented ontology tasks it is quite complete.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources