← Back to Discover

codesight

Command-line tool that scans a codebase and writes compact context files for AI coding assistants, with a built-in MCP server, so they spend fewer tokens working out how a project is laid out.

Command-line toolsMCP servers
Visit website ↗

What it does

codesight runs with a single npx command in a project root, with no configuration, setup or API keys. It scans the code and writes markdown files into a .codesight folder that describe routes, database schema, UI components, library exports, environment variables, middleware and which files depend on which. The idea is that an AI assistant reads one prepared map instead of opening many files each session. TypeScript projects are parsed with the compiler API for structural accuracy, while other languages use pattern-based detection across more than 30 frameworks. The README lists support for languages including Python, Go, Ruby, Java, Rust, PHP, Swift and C#. Options generate agent config files such as CLAUDE.md, .cursorrules and AGENTS.md, start an MCP server with 14 tools, build a wiki-style knowledge base compiled from the code rather than by a language model, report the blast radius of changing a file, and map folders of markdown notes such as decision records and meeting notes. The README publishes benchmark tables comparing output size with estimated manual exploration.

Capabilities

  • One-command scan with no configuration or API keys
  • Detects routes, schema, components, dependencies and middleware across 30+ frameworks
  • Built-in MCP server with 14 tools
  • Generates CLAUDE.md, .cursorrules and AGENTS.md
  • Blast-radius report for a changed file
  • Optional wiki and notes-mapping modes

When to use it

  • Your AI assistant keeps rereading the same files to understand the project.
  • You use Claude Code, Cursor, Copilot, Codex, Windsurf, Cline or Aider and want shared context files.
  • You want to see which routes and models a change would touch before editing.