depct: MCP Server Provides Claude with Live Runtime Analysis and Documentation

What depct Does

depct is an MCP server that gives Claude Code access to always-updated documentation, runtime analysis, dependency maps, and architecture diagrams. It instruments your Node.js runtime to capture application behavior and generates structured documentation that Claude reads before starting to code.

Setup and Runtime Instrumentation

To start using depct, run:

npx depct.dev start

The tool instruments your Node.js runtime and captures:

• HTTP routes
• DB queries
• Middleware chains
• External calls
• Response codes

Documentation Structure and Confidence Levels

depct generates structured runtime documentation tagged with three confidence levels:

• Observed: Saw it happen during runtime
• Inferred: Strong evidence from runtime patterns
• Hypothesis: Possible risk based on analysis

What Claude Gets Access To

• Full documentation that's always up to date with Claude's changes
• Runtime errors with file location, endpoint, status code, and occurrence count
• Architecture overview showing how services connect and where dependencies break
• Breaking change detection - if a route rename or dependency update causes failures, it surfaces immediately

Testing Results

During testing, the runtime error data immediately told Claude that errors were 404s from probe traffic hitting undefined routes. This would have required reading code and server logs to piece together manually. The call graph surfaced a self-loop in middleware without any manual instrumentation. After a route rename, updating documentation required only one tool call instead of hunting down every documentation reference.

How It Works with Claude

Claude reads the generated documentation before it starts coding. When Claude finishes making changes, depct incrementally updates the documentation automatically with no manual step required.