ctxcap
Related Servers
Alternatives to ctxcap
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA local MCP server that gives AI coding agents precise, symbol-level context instead of whole-file reads, packing a target symbol with its causal neighborhood (callers, callees, imports, tests) and reporting token savings versus reading the file. It also enables surgical in-place edits of only the target symbol's byte range, impact analysis before signature changes, health review, and project gate execution.MIT
- AlicenseAqualityCmaintenanceAn MCP server giving coding agents context-window-aware code search and safe, atomic multi-file edits — built to cut token usage on large codebases without sacrificing correctness.359 npm5MIT
- AlicenseNot gradedqualityCmaintenanceMCP 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.4MIT
- AlicenseAqualityBmaintenanceA 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%.12MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that cuts AI coding-agent token usage by 60–80% via framework-aware context optimization.-
- AlicenseBqualityDmaintenanceA lightweight MCP server that enables AI agents to perform deep codebase analysis by leveraging Gemini's massive context window for cross-file analysis and intelligent file selection.428MIT
TDQS
Scored across 4 tools
measure_context (reporting) and context_budget_verify (post-edit checking) are clearly distinct, but trim_to_budget is an explicit duplicate of context_budget_plan, forcing an agent to decide between two names for the same operation. The descriptions clarify the difference, but the deliberate alias overlap keeps boundaries fuzzy.
Names mix conventions: measure_context is verb_noun, trim_to_budget is verb_to_noun, while context_budget_plan/context_budget_verify use a noun-prefix style with the action last. The context_budget_ pair is internally consistent, but the set overall is readable yet not uniform.
Four tools is small but well-scoped for a context-budget domain: one measurement, one planner, one verifier, plus a compatibility alias. The deprecated alias is the only tool that does not earn an independent slot.
The core lifecycle (measure → plan → verify) is covered, including stale-reference detection and safety/preserve-span semantics. Minor gaps exist: no way to list or inspect saved plans in .ctxcap/plans, and no standalone apply/cleanup operation beyond the plan's apply flag.