AI Summarytrace-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. Activate this skill whenever you need
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "trace-mcp" skill in my project. Please run this command in my terminal: # Install skill into your project mkdir -p .claude/skills/trace-mcp && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/trace-mcp/SKILL.md "https://raw.githubusercontent.com/nikolai-vysotskyi/trace-mcp/master/skills/trace-mcp/SKILL.md" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
Use trace-mcp tools for code navigation, impact analysis, and framework-aware queries instead of Read/Grep/Glob/Bash. Activate whenever the agent needs to explore, understand, or modify a codebase that has trace-mcp indexed.
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
• get_project_map with summary_only=true — orient yourself to the project structure • 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) | | Multiple symbols + shared imports | get_context_bundle | chained get_symbol | | What breaks if I change X | get_change_impact | guessing | | Who calls this / what does it call | get_call_graph | Grep | | All usages of a symbol | find_usages | Grep | | Implementations of an interface | get_type_hierarchy | Grep / ls | | Classes implementing X | search with implements filter | Grep | | Tests for a symbol or file | get_tests_for | Glob + Grep | | Project overview | get_project_map (summary_only) | Bash ls/find | | Context for a task | get_task_context / get_feature_context | reading many files | | HTTP request flow | get_request_flow | reading route + controller files | | DB model relationships | get_model_context | reading model + migrations | | Component tree | get_component_tree | reading component files | | Circular dependencies | get_circular_imports | manual tracing | | Dead code / dead exports | get_dead_code / get_dead_exports | Grep for unused | | Project health / coverage gaps | self_audit | manual inspection | | Complexity / hotspots | get_complexity_report / get_risk_hotspots | guessing |
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster