Skip to main content
Glama
BenMousaAmine

mcp-tldr

by BenMousaAmine
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-tldr

No user-submitted related servers found.

    Related Servers

    • code-analyze-mcp

      clouatre-labs
      A
      license
      Not graded
      quality
      A
      maintenance
      Standalone MCP server for code structure analysis using tree-sitter. Directory trees, symbol definitions, and call graphs without reading raw source files. Supports Rust, Python, Go, Java, TypeScript, Fortran, JavaScript, C/C++, and C#. Benchmarked up to 68% fewer tokens vs native tools.
      6
      Apache 2.0

    • spider-map

      rofid-c
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that analyzes codebases to provide dependency graphs, impact analysis, and file insights across 15+ programming languages, enabling AI assistants to understand project structure and navigate code efficiently.
      MIT

    • solograph

      fortunto2
      A
      license
      A
      quality
      B
      maintenance
      Code intelligence MCP server for Claude Code providing multi-project code graph, semantic search, session history, knowledge base, and web search.
      15
      3
      MIT

    • code-intel

      team-harness
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for persistent code exploration and diff-aware review, exposing explore and review tools to map call paths, blast radius, and generate explainable risk-scored reports.
      22 npm
      2
      MIT

    • Satori

      ham-zax
      A
      license
      Not graded
      quality
      B
      maintenance
      Agent-safe code retrieval MCP server that indexes repositories and provides semantic search, file navigation, call graph analysis, and bounded file reading tools for coding agents.
      2,846,509 npm
      3
      AGPL 3.0
    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

    A3.8/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool has a clearly distinct and well-defined purpose, from architecture detection to semantic search. There is no overlap or ambiguity; even related tools like tldr_calls and tldr_impact are differentiated by directionality.

    Naming Consistency5/5

    All tools follow a consistent pattern: the prefix 'tldr_' followed by a snake_case name (e.g., tldr_change_impact). The naming convention is uniform and predictable.

    Tool Count5/5

    With 18 tools, the server covers a broad range of static analysis features without being overwhelming. Each tool serves a specific purpose, and the count is well-suited for a comprehensive code understanding toolset.

    Completeness5/5

    The tool set is remarkably thorough, covering file tree, structure, imports, call graphs, control and data flow, diagnostics, search, dead code, and more. There are no obvious gaps for the domain of code analysis and comprehension.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources