Skip to main content
Glama

Related Servers

Alternatives to Codebase MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      A Model Context Protocol server that enhances AI agents by providing deep semantic understanding of codebases, enabling more intelligent interactions through advanced code search and contextual awareness.
      90
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that enables AI applications to access and analyze local code repositories without manual uploads, providing file listing, content reading, code searching, and project structure analysis capabilities.
      7
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that analyzes application codebases with real-time file watching, providing AI assistants like Claude with deep insights into project structure, code patterns, and architecture.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A semantic code context server that connects your local repository to AI assistants via the Model Context Protocol, enabling dynamic codebase exploration without copy-pasting.
      5
      23 npm
      3
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An enterprise-grade Model Context Protocol server that provides comprehensive GitHub repository analysis and AI-powered development assistance through 11 streamlined tools.
      11
      2
      MIT

    TDQS

    B3.1/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools have distinct purposes: retrieving local codebase, retrieving remote codebase, and saving codebase. While 'getCodebase' and 'getRemoteCodebase' both retrieve code, the local/remote distinction is clear. There's minor potential confusion about whether 'saveCodebase' saves the local or remote version, but overall boundaries are well-defined.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with camelCase styling: getCodebase, getRemoteCodebase, saveCodebase. The naming is predictable and follows the same grammatical structure throughout, making it easy for agents to understand the action-object relationship.

    Tool Count3/5

    With only 3 tools, this feels quite minimal for a 'Codebase MCP' server. While the tools cover basic retrieval and saving operations, the scope seems limited - there are no tools for searching, analyzing, modifying, or managing codebase components. The count is borderline thin for what could be expected from a codebase management system.

    Completeness2/5

    For a codebase management server, there are significant gaps in functionality. The tools only provide retrieval and saving operations using RepoMix, but lack any tools for code analysis, search, modification, version control operations, or component management. This creates a dead-end surface where agents can only get and save entire codebases without any ability to work with code meaningfully.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues