CHRONOS-AGENT
Related Servers
Alternatives to CHRONOS-AGENT
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI coding agents to index a workspace into AST symbol graphs and retrieve exact function or class slices, trace callers and blast radius, and apply syntax-safe symbol patches without dumping whole files into context.71MIT
- FlicenseNot gradedqualityBmaintenanceProvides efficient code navigation and graph-based analysis for AI agents, enabling symbol resolution, callers, implementations, and type schemas with minimal token usage.-
- AlicenseNot gradedqualityBmaintenanceGives LLM coding agents a live code graph alongside their own tools, enabling ranked repo maps, fused lexical and graph search, symbol callers/callees and impact analysis, architecture summaries, and previewed graph-addressed edits. Adapters can extend it with custom nodes, queries, and tools.MIT
- FlicenseNot gradedqualityBmaintenanceEnables developer agents to perform semantic codebase search, dependency and impact analysis, cross-file refactoring, and full-stack API tracing through a unified query DSL over a high-performance graph engine.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and terminal users to query codebases for callers, impact, tests, dependencies, and refactor previews using static AST analysis, with every match accounted for and uncertain relationships clearly marked.1,067 npm2MIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to query a deterministic AST knowledge graph of a codebase over MCP—finding symbols, callers/callees, dependencies, impact, and relevant tests via compact path:line JSON—so they can navigate code without grepping, embeddings, or an LLM.MIT
TDQS
Scored across 14 tools
Most tools have distinct roles (analyze, edit, refactor, telemetry hydration, mutation gate), but chronos_explore is explicitly a one-call superset bundling BM25/regex matching, signature views, blast-radius, and caller chains, which overlaps heavily with chronos_search_graph, chronos_get_snippet, and chronos_blast_radius. chronos_query_hotspots vs chronos_get_architecture (which also reports O(N^2) hotspots) and chronos_query_graph vs chronos_search_graph are also easy to confuse despite helpful descriptions.
All names share the chronos_ prefix and snake_case, which is strong, but verb styles mix: verb_noun (analyze_file, query_graph, get_snippet, edit_symbol) alongside bare noun phrases (blast_radius, mutation_gate, contract_status) and one bare verb (explore). Still predictable enough to read correctly at a glance.
14 tools for a code-graph analysis engine covering ingest, query, impact, refactor, testing, and doc generation is well-scoped and each tool clearly earns its place. Slightly on the heavy side but no obvious filler.
CRUD-like lifecycle on symbols is covered (analyze, read, edit, refactor/delete) and the graph query surface is rich, but there is no batch/directory ingest (analyze_file is one file per call) and no way to invalidate or re-index stale graph nodes after external file deletion, which are real gaps for this domain.