Skip to main content
Glama
Kevin-CNC

repo-map-mcp

by Kevin-CNC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to repo-map-mcp

No user-submitted related servers found.

    Related Servers

    • vibeframe

      jubayertalha
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agentic coding tools to maintain a living, in-repo model of intent, architecture, and code, with deterministic indexing, bidirectional linking, and continuous drift detection for task-scoped context and reconciliation.
      MIT

    • codebase-rag

      Ar-maan05
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLM agents to efficiently understand and navigate a codebase by providing semantic search over symbols and a reference graph, replacing expensive grep/glob calls with structured tools like definition lookup, caller/callee queries, and change-impact analysis.
      2
      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

    • Headless Codebase Indexer

      y1hanh
      F
      license
      Not graded
      quality
      D
      maintenance
      A minimalist indexing tool that provides AI agents with semantic search and structural AST parsing for deep codebase understanding. It enables autonomous agents to navigate large codebases predictably using vector embeddings and native language server capabilities like definition and reference tracking.
      -
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a distinct responsibility: setting descriptions, indexing, fetching the map, searching, and retrieving stale files. No overlap or ambiguity exists between them.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (set_description, index_repository, get_repo_map, search_files, get_stale_files). Predictable and uniform.

    Tool Count5/5

    5 tools is a well-scoped size for a focused repository indexing server. Each tool earns its place with a clear role, no redundancy.

    Completeness5/5

    The tool surface covers the core workflow: indexing, description management, retrieval, search, and staleness detection. No obvious gaps; the lifecycle is fully addressed.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources