Skip to main content
Glama

Related Servers

Alternatives to lossless-context-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Turn any folder or Git repository into token-efficient context for Claude Code, Codex, and Cursor: up to 40% fewer tokens than Repomix, secrets always masked. MCP server with code search, a dependency graph, Git diff review, and Live Context. No embeddings, no vector database.
      8
      6
      41
      Apache 2.0
    • A
      license
      C
      quality
      A
      maintenance
      Local-first MCP server that turns project documentation and source code into durable, evidence-backed context for AI agents, with bounded retrieval and explicit gap reporting.
      8
      256 npm
      Apache 2.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Agent Context OS that compiles engineering docs into a knowledge graph, detects code drift, and serves token-budgeted context packs to AI coding agents via MCP.
      -
    • A
      license
      A
      quality
      B
      maintenance
      A zero-dependency MCP server that exposes a tiered context format so agents can load an always-available L0 index and one-line abstracts, drill into signatures and dependency edges, and pull exact source-line slices instead of whole files. It adds hybrid search, polyglot repository maps, reverse-dependency impact analysis, and write-back memory, cutting agent token usage by roughly 86%–97%.
      12
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Smart MCP server that reads your code, understands file connections, and provides precise context to AI coding assistants, reducing token usage and preventing errors from outdated or irrelevant files.
      21
      73 PyPI
      3
      MIT

    TDQS

    A4.3/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: single-file read, batch read, structural outline, usage statistics, receipt creation, and receipt verification. The only overlapping pair is read_file/read_files, but the plural and description make the batch distinction unambiguous.

    Naming Consistency4/5

    The naming is mostly predictable but mixes verb-led tools (read_file, read_files, verify_context_receipt) with noun-led tools (outline, context_stats, context_receipt). The underscore convention is consistent, but the lack of a uniform verb_noun pattern is a minor deviation.

    Tool Count5/5

    Six tools is well-scoped for a file-context ledger server, covering reading, outlining, batching, statistics, and audit without unnecessary bloat or obvious omissions.

    Completeness5/5

    The server covers the full intended workflow: navigate with outline, read with read_file/read_files, monitor usage with context_stats, and audit with context_receipt/verify_context_receipt. No critical operations are missing for its stated purpose.