Skip to main content
Glama
KaryawanSurga

TokenSaver MCP

Related Servers

Alternatives to TokenSaver MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to pre-compute repository structure and access structured intelligence briefs, including dependency graphs, hotspots, and blast radius, reducing token usage and improving code understanding.
      104 npm
      1
      -
    • A
      license
      A
      quality
      B
      maintenance
      Provides coding agents with a compact map of a TypeScript/TSX codebase, enabling direct answers about symbol locations, imports, dependencies, and references while reducing token usage.
      5
      3 npm
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Provides coding agents with repository-aware tools to understand code structure, find existing patterns, and review plans, architecture, and diffs, enabling a consistent engineering workflow across Cursor, Codex, and Claude Code.
      7
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to retrieve compact, cited repository maps through MCP tools such as search, symbol inspection, flow investigation, and deep context loading.
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to interrogate a local repository deterministically for symbols, dependencies, call paths, routes, tests, and Git impact, returning verified structured evidence with exact line citations instead of requiring the whole codebase to be read.
      3
      MIT

    TDQS

    A4.2/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool targets a distinct concern: repo_map gives a whole-repo overview, find_symbol locates a named symbol across files, file_outline shows one file's structure, and entry_points finds execution starts. There is minor overlap between repo_map and entry_points (both orient you in a repo), but the descriptions make the difference clear.

    Naming Consistency4/5

    All tool names use a consistent noun-based pattern (repo_map, find_symbol, file_outline, entry_points) with snake_case. The pattern is predictable, though the verbs are not uniform (find vs. implicit get/list), which is a minor deviation.

    Tool Count5/5

    Four tools is a well-scoped set for a code-navigation/exploration server. Each tool covers a distinct need without redundancy, and the count feels appropriate for the stated purpose.

    Completeness4/5

    The server covers the main exploration workflow: orient (repo_map, entry_points), locate (find_symbol), and inspect (file_outline). A minor gap is the lack of a tool to read file contents or search by text/pattern, but the server's stated purpose is navigation, not full code retrieval.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues