codesight_get_blast_radius
Blast radius analysis. Given a file (or list of files), returns all transitively affected files, routes, models, and middleware. Use before making changes to understand impact.
LABSCO SUMMARY
The assistant asks for the part it needs instead of loading the project.
Each tool is scoped — routes by prefix, schema by model, env vars filtered to required — so orientation costs a small answer rather than a directory walk. Blast radius is the one to reach for before an edit: it names what depends on the file you are about to change.
What it is
A project scanner that hands an assistant the map instead of the files. It detects the stack across 30+ frameworks, parses ORMs for the data model, and exposes the results as 14 tools so a question about routes or a data model costs one small call rather than a directory crawl. TypeScript projects are read with AST precision; the other languages fall back to regex detection over the same frameworks.
What you get
- A full project scan, and a compact overview when the full one is more than the question needs
- Routes filtered by prefix, tag or method, and the schema filtered to one model
- Blast radius for a file — what breaks if you change it — read before the edit rather than after
- Environment variables collected, narrowed to the ones that are actually required
- The most-imported files, which is the fastest read on where a codebase's weight sits
- Background work found and named: BullMQ queues, Celery tasks, Kafka topics, Redis pub/sub and EventEmitter
- A test coverage map of which routes and models have test files at all
- A generated wiki over the project — a small index to read at session start, then one article at a time — with a lint pass over it
- A knowledge map of decisions, open questions and themes, when the project has been scanned in that mode
- Results cached per session, so the first call scans and the rest answer immediately, with a forced re-scan when the code has moved on
Requirements
Node.js 18 or newer and nothing else — no configuration, no API keys, and zero dependencies. Started with npx codesight --mcp over stdio, or from a global install, which starts noticeably faster. On Codex the first npx run can exceed the default startup timeout, so raise it or install globally. It reads the project it is run in; languages covered include TypeScript, JavaScript, Python, Go, Ruby, Elixir, Java, Kotlin, Rust, PHP, Dart, Swift, C# and BrighterScript.
Setup effort
One command — npx codesight --mcp
USE CASES
01
Getting oriented in an unfamiliar repository
Read the wiki index first, then the compact summary, and open only the articles that cover what you are about to touch.
02
Checking what a change will break
Ask for the file's blast radius before editing it, and look at whether the routes and models it touches have tests.
03
Finding the endpoint you half remember
Filter the routes by prefix or method rather than grepping, then pull the schema for the model behind it.
04
Setting the project up somewhere new
List the environment variables narrowed to the required ones, so a first run does not fail on a missing key.
05
Working out what runs in the background
Read the queues, tasks, topics and pub/sub channels the code registers — the part that never shows up in the route table.
06
Keeping the map honest after a refactor
Force a re-scan so the cached answers match the code, and check the wiki still lints clean.
14 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
codesight_get_coverage
Get test coverage summary: which routes and models have corresponding tests. Shows coverage percentage and lists uncovered endpoints.
codesight_get_env
Get environment variables across the codebase with required/default status and source file.
codesight_get_events
Get event queues, Kafka topics, Redis pub/sub channels, and EventEmitter events detected in the project. Useful for understanding async data flows.
codesight_get_hot_files
Get the most-imported files in the project. These have the highest blast radius — changes here affect the most other files.
codesight_get_knowledge
Get the knowledge map for a second-brain or docs folder: decisions made, open questions, recurring themes, people mentioned, and an index of all notes by type (ADR, meeting, retro, spec, etc.). Run npx codesight --mode knowledge first to generate it.
codesight_get_routes
Get API routes with methods, paths, params, tags, and handler files. Supports filtering by prefix, tag, or HTTP method.
codesight_get_schema
Get database models with fields, types, constraints, and relations. Optionally filter by model name.
codesight_get_summary
Compact project summary (~500 tokens). Stack, key stats, high-impact files, required env vars. Use this first before diving deeper.
codesight_get_wiki_article
Read a specific wiki article by name. Each article covers one subsystem in narrative form (~300-500 tokens). Use for targeted questions: 'how does auth work?' → article='auth', 'what models exist?' → article='database', 'what routes are there?' → article='api'. Much cheaper than loading the full context map.
codesight_get_wiki_index
Get the wiki index (~200 tokens). Lists all available wiki articles with one-line summaries. Read this at session start for instant project orientation. If wiki not generated, run npx codesight --wiki first.
codesight_lint_wiki
Health check the wiki. Finds orphan articles, missing cross-links, and articles that may be stale. Run after making significant changes to verify wiki integrity.
codesight_refresh
Force re-scan the project. Use after making significant changes to get updated context.
codesight_scan
Full codebase scan. Returns complete AI context map with routes, schema, components, libraries, config, middleware, and dependency graph. Use this for initial project understanding.
BEFORE YOU INSTALL
What to know first
Tools you get
14 tools when we connected. codesight_get_wiki_index, codesight_get_wiki_article and codesight_lint_wiki read the wiki built by npx codesight --wiki, and codesight_get_knowledge reads the map built with --mode knowledge.
Requires
npx on PATH
Where it runs
All 3 documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 14 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx codesight --mcpMCP Clients
Claude Code, Cursor
JSON
{
"mcpServers": {
"codesight": {
"command": "npx",
"args": [
"codesight",
"--mcp"
]
}
}
}Codex
CODEX · TOML
[mcp_servers.codesight]
command = "npx"
args = ["codesight", "--mcp"]
startup_timeout_sec = 60
