Skip to main content
Glama
Sign In
OpenCode Context Optimizer (OCCE)

OpenCode Context Optimizer (OCCE)

by SammySN-car
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to OpenCode Context Optimizer (OCCE)

No user-submitted related servers found.

    Related Servers

    • mcp-context-condenser

      rafim-dev
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to reduce token usage by condensing source code into AST skeletons, extracting specific symbols, compressing logs, and estimating token budgets.
      4
      MIT

    • lean-context-mcp

      fejinrp
      A
      license
      B
      quality
      C
      maintenance
      Enables coding agents to reduce context tokens by requesting file outlines, individual symbols, compact searches, and condensed test, lint, and type-check failures instead of reading whole files or raw command output.
      6
      0
      MIT

    • cctx

      anil7948
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude Code to reduce token usage by 70-90% using a local LLM for codebase indexing, tool output compression, and turn summarization.
      33 npm
      3
      MIT

    • ctxtrim

      bayuh85
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to shrink bulky tool output, logs, test runs, and file dumps down to compact briefs, and to record and recall decisions in a small session ledger. This keeps long-running tasks within context limits while preserving errors, findings, and key notes.
      8 npm
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool has a distinct role: AST outline vs. single-symbol extraction vs. command execution vs. test output vs. diff vs. token accounting. The only mild overlap is code_skeleton vs. symbol_slice, where both read source code, but the outline-vs-implementation distinction in the descriptions resolves it.

    Naming Consistency4/5

    All names are snake_case two-word compounds in a modifier+noun style (code_skeleton, symbol_slice, test_compress, diff_compact, token_ledger), with smart_exec being the only slight deviation in verb-vs-noun form. Readable and predictable overall.

    Tool Count5/5

    Six tools for a context-optimization server is well-scoped: two for reading code, three for compressing execution/test/diff output, one for telemetry. No filler tools.

    Completeness4/5

    The surface covers code reading, command execution, test output, diffs, and token accounting, which are the core levers of context reduction. A small gap is the absence of a symbol/search tool to locate symbols across files before calling symbol_slice.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources