Skip to main content
Glama
janeksm

mcp-digger

by janeksm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-digger

No user-submitted related servers found.

    Related Servers

    • CodeMap MCP

      bbajt
      F
      license
      Not graded
      quality
      B
      maintenance
      CodeMap is a Roslyn-powered MCP server that lets AI agents navigate C# codebases by symbol, call graph, and architectural fact, instead of brute-force reading thousands of lines of source code. One tool call. Precise answer. No context flood.
      19
      -

    • mcp-intelligence-context

      LeoChimal09
      F
      license
      A
      quality
      C
      maintenance
      Provides codebase indexing and retrieval tools that give AI agents token-efficient, query-relevant context packages (symbols, imports, and dependencies) instead of scanning entire repositories.
      6
      -

    • CodeGraph

      andysom25
      A
      license
      Not graded
      quality
      D
      maintenance
      Supercharges AI coding agents with semantic code intelligence, providing pre-built knowledge graphs for surgical context, faster answers, and fewer tool calls.
      MIT

    • CodeGraph

      colbymchenry
      A
      license
      Not graded
      quality
      A
      maintenance
      Supercharges AI coding agents with a pre-indexed semantic code graph, enabling instant symbol relationships, impact analysis, and context retrieval across 20+ languages.
      70,850 npm
      71,313
      MIT

    • roz-mcp

      andypgray
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides C# coding agents with compiler-accurate symbol analysis, including references, renames, and impact analysis for .NET solutions.
      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 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: dig_init creates a starter config, while dig_status validates connectivity and configuration. There is no overlap.

    Naming Consistency5/5

    Both tools consistently use the 'dig_' prefix and verb_noun pattern (init, status) in snake_case, making the naming predictable.

    Tool Count2/5

    With only two tools, the server feels thin for a tool named 'digger' that presumably should provide git analysis capabilities. The description hints at more tools after configuration, but currently only init and status are defined.

    Completeness2/5

    The server lacks core digging functionality (e.g., analyzing commits, blame, changes). It only covers initialization and health-check, leaving a major gap in the expected tool surface.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources