Dependency Tracer MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HIE_READER_BIN | No | Path to the compiled hie-reader Haskell binary. Without it, Haskell indexing falls back to source parsing. | |
| DEP_TRACER_BACKEND | No | Storage backend: native (better-sqlite3), wasm (sql.js), or unset (auto: native first, fall back to wasm). | auto |
| DEP_TRACER_DB_PATH | No | SQLite database path. Set to a project-relative path (e.g. .dep-tracer/index.db) for per-project isolation. | ~/.dep-tracer/deps.db |
| DEP_TRACER_LOG_LEVEL | No | debug, info, warn, error. All logs go to stderr (stdout is reserved for MCP stdio). | info |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| index_codebaseA | Index a codebase to build the dependency graph. Supports Haskell and ReScript. Performs incremental indexing (only changed files) unless force_full is set. For Haskell, optionally uses hie-reader binary for rich type info; falls back to source parsing. |
| index_statusA | Get indexing status for all codebases or a specific one. Shows file count, symbol count, edge count, last indexed time. |
| trace_calleesA | Trace what a function/component depends on (outgoing edges). Shows all functions called, types used, and components rendered. Use this to answer: "What do I need to mock to test function X?" or "What is the full flow from this endpoint to the database?" |
| trace_callersA | Trace what depends on a function/component (incoming edges). Shows all callers, importers, and parent components. Use this to answer: "I changed function X, what tests need updating?" or "What entry points reach this code?" |
| trace_module_depsA | Trace module-level dependencies (coarser but always available). Shows which files/modules depend on which. |
| impact_analysisA | Given changed files or symbols, determine the full impact: what tests might break, what entry points are affected, what downstream consumers exist. |
| get_symbolA | Get detailed information about a specific symbol: definition location, type signature, direct callees, and direct callers. |
| get_module_symbolsB | List all symbols defined in a module/file: functions, types, components, exports. |
| search_symbolsA | Search for symbols by name pattern. Supports partial matching and * wildcards. Use when you know a function name but not its full module path. |
| get_test_contextA | Get everything needed to write tests for a function or module: the function itself, all its direct dependencies (what to mock), all its callers (usage examples), type definitions it uses, and file paths for all involved code. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/pdogra1299/dep-tracer-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server