Skip to main content
Glama
EDMMY

codebase-bridge-mcp

by EDMMY
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to codebase-bridge-mcp

No user-submitted related servers found.

    Related Servers

    • bigmac-mcp

      TrueNorthIT
      A
      license
      Not graded
      quality
      C
      maintenance
      A small MCP server that turns a shared Ollama box into a team resource for Claude Code, providing typed tools and delegated read-only repo exploration using local models.
      MIT

    • throughline

      devznsh
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that indexes local code repositories, extracting symbols and call graphs to give Claude precise, structural answers with real file paths and line numbers. Runs entirely locally with no network requests, for privacy-focused code understanding.
      290 npm
      MIT

    • repo-intelligence-mcp

      georg-nikola
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives LLMs structured, read-only insight into local code repositories — directory tree, languages, dependencies, scripts, and config files.
      MIT

    • sove-mcp

      JrKrishh
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that gives Claude structural understanding of a codebase—dependency graph, entry points, complexity ranking, and import cycles—without reading every file into context.
      4
      MIT

    • Codelens-MCP

      Yashkashte5
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives Claude Desktop complete intelligence about any public GitHub repository. Research libraries, compare packages, audit dependencies, and explore codebases through natural conversation.
      1
      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.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools have clearly distinct purposes: ask_codebase for Q&A with turn-based steering, bridge_cost for cost reporting, and bridge_forget for thread management. There is no overlap in functionality.

    Naming Consistency4/5

    Tool names follow a predictable pattern with an underscore separator, though the primary tool uses 'ask_' while the auxiliary tools use 'bridge_' prefix. This is a common and acceptable namespace convention but slightly deviates from a fully uniform verb_noun pattern.

    Tool Count5/5

    With three tools, the count is appropriate for the server's focused scope of codebase Q&A with supporting cost and thread management. Each tool serves a necessary function without redundancy.

    Completeness5/5

    The toolset covers the full workflow: asking questions with thread support, tracking costs, and forgetting threads when needed. No obvious gaps exist for the stated purpose of exploring a codebase with a conversational agent.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources