trace-mcp

# trace-mcp — Code Intelligence Routing trace-mcp is a framework-aware code intelligence MCP server. It exposes 120+ tools that return semantic, structured results over a cross-language dependency graph. When trace-mcp is available, it is almost always cheaper and more accurate than native file tools. ## When to Use Activate this skill whenever you need to: - Find a function, class, method, route, component, or any symbol - Understand a file, module, or feature before editing - Determine what breaks if you change something - Trace a request flow, call graph, or data flow - Audit architecture, dead code, tests, or security **Do not use** `Read`, `Grep`, `Glob`, or shell `ls`/`find`/`cat`/`head`/`tail` for exploring source code (`.ts`, `.js`, `.py`, `.php`, `.go`, `.rb`, `.java`, etc.). Use trace-mcp tools instead. Native tools stay allowed only for non-code files (`.md`, `.json`, `.yaml`, configs) or immediately before an `Edit` on a known file. ## Start-of-Session Checklist 1. `get_project_map` with `summary_only=true` — orient yourself to the project structure 2. `get_task_context` with `task: "<natural-language description>"` — gather all relevant code in a single call instead of chaining `search` → `get_symbol` → `Read` ## Decision Matrix | Task | trace-mcp tool | Instead of | |---|---|---| | Find a symbol by name | `search` | Grep | | Understand a file before editing | `get_outline` | Read (full file) | | Read one symbol's source | `get_symbol` | Read (full file) ...