Skip to main content
Glama

Related Servers

Alternatives to codebase-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      A local-first MCP server that provides AI agents with safe codebase access through file discovery, hybrid lexical-semantic search, and project introspection. It features durable local memory and semantic indexing while keeping all data and processing entirely on your local machine.
      74
      22 npm
      6
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A self-hosted MCP server that indexes your codebase and provides AI assistants with deep context including file tree, full-text search, git history, dependencies, and stack detection, all without sending your code to third parties.
      7 npm
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      A local-first MCP server that enables AI tools to safely inspect and search code repositories, providing indexing, deterministic BM25 search, code outlining, and context bundles without code modification.
      9
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A self-hosted MCP server that lets ChatGPT securely read, edit, search, and run code in your local projects via an owner-approved connection.
      800 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      This self-hosted MCP server connects an MCP client such as ChatGPT to approved local project folders, enabling file reading and editing, code search, shell command execution, and Git worktree workflows without uploading code to a third party. It also supports mounting external stdio or Streamable HTTP MCP servers as dynamic capabilities.
      800 npm
      MIT

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of codebase exploration: tree structure, content search, file reading, and dependency analysis. There is no overlap in purpose or output.

    Naming Consistency5/5

    All tool names follow a clear verb_noun pattern with snake_case (get_project_tree, search_codebase, read_project_file, inspect_tech_stack). The verbs are distinct and accurately describe the action.

    Tool Count5/5

    Four tools is well-scoped for a codebase exploration server. Each tool provides a necessary and non-redundant capability, without being overly sparse or bloated.

    Completeness4/5

    The set covers common read-only codebase tasks: structural overview, searching, reading files, and identifying tech stack. A minor gap is the lack of direct directory-level file listing or metadata, but the overall surface is sufficient for typical exploration.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues