Skip to main content
Glama
omkar9854

slimctx-token-optimizer

by omkar9854

Related Servers

Alternatives to slimctx-token-optimizer

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that reduces AI agent token usage by up to 90% through intelligent context compression. Enables efficient code exploration, multi-file refactoring, and debugging by providing tools for smart reading, searching, and managing code context.
      4
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Local-first MCP server that gives any AI coding agent per-project memory, workflow intelligence, and always-on, lossless token & context optimization.
      37
      12 npm
      5
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Semantic compression MCP server that reduces document token usage by 60-80% using structured symbolic notation, enabling Claude to efficiently store, retrieve, diff, and summarise documents across PRD, CODE, PAPER, and MEETING domains.
      -
    • A
      license
      A
      quality
      A
      maintenance
      An MCP server that preserves LLM context by intercepting large data outputs and returning only concise summaries or relevant sections. It enables efficient sandboxed code execution, file processing, and documentation indexing across multiple programming languages and authenticated CLIs.
      11
      15,417 npm
      22,986
      Elastic 2.0

    TDQS

    A3.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: compress creates a reference, retrieve recovers original content from a reference, and stats reports session token savings. No overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent 'slimctx_' prefix followed by a clear verb: compress, retrieve, stats. The pattern is uniform and predictive.

    Tool Count5/5

    Three tools is an ideal size for this focused server. Each tool is essential to the compression-retrieval-stats lifecycle, and no redundant or extraneous tools exist.

    Completeness5/5

    The tool surface fully covers the domain: compressing content, retrieving it when needed, and tracking token savings. There are no obvious workflow gaps for the stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues