Esta página se muestra en inglés. Una traducción al español está en curso.
MCP ConfigsMay 11, 2026·2 min de lectura
trace-mcp — Project Tracing MCP for Agents
Index a project once, then reuse maps and task context via an MCP server. Includes a CLI to init and register projects for Claude Code, Cursor, and more.
Primero deja archivos en staging; la activación requiere revisar el README y el plan staged.
Introducción
Index a project once, then reuse maps and task context via an MCP server. Includes a CLI to init and register projects for Claude Code, Cursor, and more.
Best for: Teams who want fewer repeated “scan the repo again” passes and more deterministic context reuse across tasks
Works with: Node.js CLI + MCP clients; codebases and markdown vaults (per repo docs)
Setup time: 12 minutes
How to Use It Well
Setup time ~12 minutes (npm install + init + add a project)
GitHub stars + forks (verified): see Source & Thanks
CLI flow is 2 core commands (init, add) for first-time wiring
Treat it like a cache for agent reasoning: run the CLI once to index and register a project, then pull project maps, change impact, and task context through MCP tools instead of repeatedly loading the same files into the prompt.
FAQ
Q: What’s the big win?
A: You stop re-deriving the same repo map for every task. The agent can pull structured project context when needed.
Q: Do I have to keep files in my repo?
A: The project describes keeping state under a home directory and keeping the repo clean unless you opt in.
Q: Is it only for code?
A: No. The docs describe indexing markdown vaults (notes, headings, links) as well.