Skip to main content
Glama
breca

mcp-codemap

by breca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-codemap

No user-submitted related servers found.

    Related Servers

    • repo-map

      noambinabout-boop
      A
      license
      Not graded
      quality
      B
      maintenance
      A navigable symbol map of your codebase for coding agents, enabling efficient code navigation and reading only relevant symbols instead of entire files.
      MIT

    • ctx-gen-mcp

      liubinmaster
      A
      license
      A
      quality
      B
      maintenance
      Generates progressive-disclosure code context documentation (L0/L1/L2/L3) for large projects, helping AI coding agents understand codebases efficiently.
      3
      MIT

    • 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

    • OpenLore

      clay-good
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides persistent architectural memory and structural cognition for AI coding agents, enabling efficient orientation, graph-aware context, and drift detection across codebase evolution.
      1,150 npm
      303
      MIT

    • mcp-code-indexer

      fluffypony
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to intelligently navigate and understand codebases by providing instant file descriptions, semantic search, and context-aware recommendations, eliminating the need to repeatedly scan files.
      20
      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

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: map provides an overview, query inspects a specific entity, and reindex refreshes the index. There is no functional overlap.

    Naming Consistency4/5

    All tool names are single lowercase verbs, which is consistent in style. However, they don't follow a verb_noun pattern, which is common in MCP tools, but still predictable and clear.

    Tool Count5/5

    With only 3 tools, the server is highly focused on codebase exploration and indexing. Each tool serves a necessary role without redundancy, making the set well-scoped.

    Completeness4/5

    The tools cover orientation, deep inspection, and index refreshing. Minor gaps exist, such as lacking a search tool, but the core workflows are complete for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources