wingbox
Related Servers
Alternatives to wingbox
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents to explore a repository by querying a pre-built structural knowledge graph of symbols and their relationships — definitions, callers, callees, blast radius, and file-level impact — instead of grepping and reading files. This cuts the tokens spent on code exploration by roughly 96–99% while running entirely on local SQLite with tree-sitter parsing.1MIT
- FlicenseAqualityCmaintenanceDeterministic code intelligence engine — indexes 27 languages into a queryable symbol graph for real-time blast-radius analysis, no embeddings or LLM calls.527-
- AlicenseAqualityBmaintenanceLocal code-graph engine for AI coding workflows: static analysis of Rust, Cangjie, ArkTS, TypeScript/JavaScript, C/C++, Python, and Shell projects into symbols, imports, call graphs, and quality gates, with pre-commit change review and impact analysis. Read-only by design — never executes build scripts or uploads code.61MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to query a local structural code graph, inspect relationships and impact, and retrieve focused project context before reading full files.24 npmMIT
- FlicenseNot gradedqualityBmaintenanceProvides efficient code navigation and graph-based analysis for AI agents, enabling symbol resolution, callers, implementations, and type schemas with minimal token usage.-
- FlicenseNot gradedqualityBmaintenanceProvides graph-native code intelligence for coding agents, enabling them to navigate repositories through compact SQLite-backed symbol graphs and retrieve full source only for relevant symbols.-
TDQS
Scored across 18 tools
Several tools overlap: entity, usages, find_function and find_type all locate definitions or references, while boundary vs boundaries and analyze vs quick are easy to confuse. Detailed descriptions help resolve most cases, but selecting the right tool still requires careful reading.
Most names are lowercase snake_case, but the conventions are mixed: find_* verb_noun tools sit alongside bare nouns (deps, impact, boundary, layers), verb-only names (query, build, analyze), and the near-identical boundary/boundaries. Readable, but not a predictable pattern.
18 tools is reasonable for a code-graph analysis server, and most cover distinct operations. A few, such as quick and entity, feel like convenience wrappers over other tools, so the set is slightly above the ideal 3-15 range.
The surface covers graph building/refresh, querying, dependency and reverse-dependency traversal, impact analysis, architecture layers and boundaries, call graph navigation, symbol lookup, usages, and diff inspection. There are no obvious lifecycle gaps for this domain.