Skip to main content
Glama

Related Servers

Alternatives to tokensave-mcp-diet

  • A
    license
    B
    quality
    B
    maintenance
    Connects Blender to Claude AI through the Model Context Protocol (MCP), allowing Claude to directly interact with and control Blender for AI-assisted 3D modeling, scene manipulation, and rendering.
    21
    32,610
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    A
    maintenance
    Enables MCP-compatible developer environments to shrink verbose tool outputs—test logs, git diffs, directory listings, and file dumps—before they reach the context window, preserving compiler errors, failure signatures, and decisive anchors. It runs either as direct callable tools or as a transparent proxy wrapping other MCP servers such as filesystem, git, or terminal providers.
    1
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    Aggregator MCP proxy that collapses N downstream MCP servers into 4 meta-tools with progressive tool discovery, and compresses large tool outputs (HTML→Markdown, JSON summarization) with full-output retrieval via read_more and a per-session token-savings report.
    4
    53 npm
    2
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Intelligent MCP proxy server that reduces context bloat by serving only the tools your AI actually needs through semantic search and a fixed two-tool surface.
    13
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    A proxy server that wraps existing MCP servers to significantly reduce token consumption by compressing tool descriptions into a two-step interface. It enables users to integrate extensive toolsets without exceeding context limits or incurring high API costs.
    137
    Apache 2.0
  • A
    license
    Not graded
    quality
    D
    maintenance
    MCP proxy that reduces context usage through semantic tool routing, enabling on-demand discovery and routing of relevant tools.
    MIT

TDQS

B3.2/5.0

Scored across 27 tools

Disambiguation4/5

Most tools map to a distinct action (navigate, click, type, hover, select_option, wait_for, resize, close) and the descriptions actively steer choices, e.g. snapshot vs screenshot vs find vs snapshot_detail. A few boundaries blur: browser_evaluate vs browser_run_code_unsafe both execute JS, browser_drag vs browser_drop both involve dragging, and browser_snapshot vs browser_find vs snapshot_detail all read page structure.

Naming Consistency4/5

The set is overwhelmingly snake_case with a uniform browser_ prefix and a consistent verb_noun shape (browser_press_key, browser_navigate_back, browser_select_option). Deviations are minor: noun-only names like browser_snapshot and browser_tabs, and the two tokensave helper tools (snapshot_detail, result_detail) drop the browser_ prefix entirely.

Tool Count3/5

27 tools is heavy for a single server, though browser automation is a genuinely broad domain and nearly every tool covers a real capability. Some consolidation is possible (evaluate/run_code_unsafe, drag/drop, snapshot/find/snapshot_detail), so the surface sits above the comfortable range rather than clearly over-scoped.

Completeness4/5

Coverage is strong across the browser lifecycle: navigation, element interaction, form filling, file upload, drag/drop, dialogs, tabs, viewport, console, network inspection, media emulation, plus result-truncation helpers. Gaps are modest—no cookie/localStorage or session-state tools, no request interception, and scrolling must be done indirectly via evaluate or key presses.

Maintenance

ActivityMaintained
ResponsivenessNo issues