mcp-context-condenser
Related Servers
Alternatives to mcp-context-condenser
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to efficiently analyze codebases by extracting AST skeletons, reducing token usage while preserving type contracts and interfaces.5 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to compress terminal output and file context in real time, preserving full error tracebacks while reducing token consumption by 60-85%.34MIT
- AlicenseBqualityCmaintenanceMaximizes AI agent context window by enabling compact code reading and editing, reducing tokens by 40% for deeper codebase understanding.1957 npm3MIT
- AlicenseNot gradedqualityBmaintenanceReduces token consumption for AI coding agents by 50-70% through intelligent code context filtering, Git delta tracking, and local SQLite/Tree-sitter indexing.167 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to efficiently query code context via a symbol graph, reducing token usage by up to 20x.534 npm487-
- AlicenseBqualityBmaintenanceEnables LLMs to efficiently read, write, and refactor code using precise AST-based operations, reducing token usage and context window waste.2519 npm3MIT
TDQS
Scored across 4 tools
Most tools target clearly distinct inputs: source files, individual symbols, logs, and token analysis. Condense_source and extract_symbol both reduce source token usage, but their different approaches (structural skeleton vs. exact symbol extraction) are described well enough to distinguish them.
Three tools follow a clean verb_noun snake_case pattern (condense_source, extract_symbol, compress_log). Token_budget_view breaks the pattern by leading with the noun rather than an action verb, creating a minor inconsistency.
Four tools is an ideal size for a focused context-condensing utility. Each tool serves a distinct, practical purpose and none feel redundant or unnecessary.
The set covers source reduction, symbol extraction, log compression, and token-budget analysis, which addresses the main context-overload scenarios. Minor gaps exist, such as no multi-file or project-wide condensation tool, but the core workflows are well covered.