diffctx
Related Servers
Alternatives to diffctx
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceExtracts minimal, relevant code context from multiple programming languages while analyzing diffs and optimizing imports to reduce token usage for AI assistants. Supports TypeScript/JavaScript, Python, Go, and Rust with token-aware caching.711 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to retrieve budgeted, AST-aware edit context and run refactor-safety checks over a local Tree-sitter code knowledge graph, reducing token use by avoiding full-file reads.4MIT
- AlicenseBqualityBmaintenanceIn-memory Code Property Graph context slicer for local models (Ollama,Cursor, Claude Desktop) that extracts sub-1,200 token reachability closures for autonomous repository bug repair on consumer edge hardware (4GB–8GB VRAM) without cloud APIs.4MIT
- AlicenseAqualityCmaintenanceCode graph context engine that parses codebases with tree-sitter (170+ languages), builds structural dependency graphs, and provides 24 MCP tools for code intelligence. One prepare_context call gives your AI agent the right files for any task. Includes focus, blast radius, hotspots, dead code detection, and hybrid search.2422 PyPI1AGPL 3.0
- AlicenseAqualityBmaintenanceShow an AI coding assistant only the code that matters for a change — callers, callees, and related functions packed into a token budget, with self-grading retrieval.45MIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to reduce context window bloat by filtering noisy Git diffs, summarizing structural AST changes, simulating merges, and masking high-entropy secrets before they reach the model.51MIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of selecting the wrong tool. Its purpose—finding external context a change reaches—is clearly stated and distinct.
The single tool uses a readable snake_case name with a server-specific prefix. With only one tool, there is no cross-tool pattern to violate, though the name is not a conventional verb_noun form.
A single tool is thin for a server, even a focused one. It does bundle multiple modes (impact, locate, pack), which helps, but the surface still feels minimal.
The tool covers impact analysis, fragment location, and code packing for a diff context, which is a coherent lifecycle for the stated purpose. Minor gaps may exist, such as explicit diff listing or file-level retrieval, but the core domain is addressed.