readscout
Related Servers
Alternatives to readscout
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to retrieve only the specific code sections that answer their questions, drastically reducing context usage while running fully locally.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to interrogate a local repository deterministically for symbols, dependencies, call paths, routes, tests, and Git impact, returning verified structured evidence with exact line citations instead of requiring the whole codebase to be read.56 PyPI4MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to search and ask questions about a local codebase with citations, using BM25 and optional embeddings, all offline.4 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to retrieve task-relevant repository code, pack verbatim excerpts within a configurable token budget, expand cited line ranges, and optionally use local semantic search or verified JSON/TOON compression.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI coding agents to retrieve focused, bounded repository context locally and read-only, reducing token usage while never modifying the repository or executing its code.-
- AlicenseNot gradedqualityBmaintenanceEnables agents to find code by describing its behaviour rather than guessing file names, returning ranked file:line snippets that cost far fewer tokens than grep-then-read. Also surfaces neighbouring implementations, callers and tests around a location you already know, indexing local paths or git URLs locally on CPU.428 npm1MIT
TDQS
Scored across 3 tools
local_ask and local_digest both use a local model to extract info from files, which creates mild overlap, but their descriptions clearly separate general code Q&A from log/command-output triage. local_edit is unmistakably distinct as a mutation tool with its own gating semantics.
All three tools share the same local_ prefix followed by a single verb/noun (ask, digest, edit), giving a fully predictable pattern. No mixing of conventions.
Three tools is a tight, well-scoped set for a focused helper: query files, triage logs, and apply mechanical edits. Each tool is substantial and earns its place with no redundancy.
The surface covers the core read/query, triage, and edit lifecycle for local model assistance, which matches the stated purpose. There is no explicit multi-file batch or non-mechanical edit path, but that exclusion appears deliberate and documented rather than a gap.