Log inSubmit server
Trace MCP logo

Trace MCP

by nikolai-vysotskyi

Indexes local source code into a framework-aware dependency graph and exposes navigation, impact analysis, and refactoring tools over MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Trace MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "nikolai-vysotskyi-trace-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "trace-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

nikolai-vysotskyi/trace-mcp MCP server indexes a local codebase into a cross-language dependency graph and exposes the graph through MCP. It models framework semantics such as routes, ORM relations, component rendering, and dependency-injection trees, then provides tools for navigation, impact analysis, call graphs, refactoring, security scanning, and cross-session memory. Use it when an agent needs structured answers about a repository instead of repeatedly reading files and traversing dependencies. Installation is available through npm, with `trace init` for agent configuration and `trace add` to index the current repository.

Use cases

  • Index a repository for framework-aware agent navigation
  • Analyze the impact of changing a model or dependency
  • Trace calls and relationships across languages
  • Support refactoring and security-scanning tasks
  • Reuse repository context across agent sessions

Key features

  • Cross-language dependency graph
  • Framework-aware code indexing
  • Change-impact analysis with get_change_impact
  • Call-graph and code navigation tools
  • Refactoring and security scanning support
  • Cross-session codebase memory

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

19/20 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · trace-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars198Stargazers on the source repository.
npm downloads2.2kPackage downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Trace MCP works

What nikolai-vysotskyi/trace-mcp MCP server does

nikolai-vysotskyi/trace-mcp MCP server builds an index of a source repository and represents relationships between symbols, files, and framework-level constructs as a dependency graph. The index spans multiple programming languages and is designed to retain framework meaning rather than treating the repository as plain text.

Supported semantic structures include application routes, ORM relationships, rendered components, and dependency-injection trees. This lets an agent investigate questions such as what may be affected by changing a model, where a symbol is used, or how a call path crosses framework boundaries.

The project is listed in the 💻 Developer Tools category. It is intended for agents working on local repositories, with the README stating that code stays local. A desktop application can also explore the same indexed graph through a GPU-based graph interface, separate from the MCP server workflow.

How it works

The repository is indexed once and then queried through MCP. Rather than repeatedly loading files and reconstructing relationships during every task, an agent can request information from the precomputed graph. The index is kept incrementally fresh, so later requests can use updated repository structure without rebuilding the entire understanding from scratch.

One documented example is get_change_impact, which returns the likely blast radius of a change across areas such as source files, migrations, and dependency-injection code. The available capabilities cover code navigation, dependency and call-graph inspection, refactoring support, security scanning, and memory across sessions.

Setup and configuration

Install the server globally with npm:

Terminal
npm install -g trace-mcp

Run trace init once per machine to connect the server to an agent, then run trace add from the repository that should be indexed. The README also provides downloadable releases for macOS and Windows. No application installation is required for the MCP server itself.

Tools and capabilities

The documented capability areas include:

  • Navigate relationships in a codebase
  • Inspect call graphs and dependency connections
  • Calculate change impact with get_change_impact
  • Analyze framework-aware structures such as routes and ORM relations
  • Support refactoring and security-scanning workflows
  • Preserve usable code context across agent sessions

The graph can be used by Claude Code, Cursor, Codex, Windsurf, Zed, and other MCP clients.

Limitations and notes

nikolai-vysotskyi/trace-mcp MCP server is most relevant when the agent needs repository structure, dependencies, or framework semantics.

The published pull-request benchmark measured a specific build, version 3.23.2, on September 7, 2026. Its reported token and review results therefore describe that benchmark setup rather than guaranteeing the same results for every release or repository. The project is licensed under MIT.

The stated exception is a third-party patcher pairing available with the Max tier.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Trace MCP

nikolai-vysotskyi/trace-mcp is an MCP server that indexes local source code into a cross-language, framework-aware dependency graph and serves it to AI agents. Its capabilities include get_change_impact plus tools for navigation, call-graph analysis, refactoring, security scanning, and cross-session memory. It connects agents to the indexed codebase rather than a hosted service.

Install it with `npm install -g trace-mcp`, run `trace init` once per machine to wire it into an agent, and run `trace add` inside the repository to index it. The project also provides downloadable macOS and Windows releases.

Use the `get_change_impact` tool to request the likely blast radius of a change.

Yes, Cursor is listed among the supported clients. The README also names Claude Code, Codex, Windsurf, Zed, and any MCP client.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewTrace MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/nikolai-vysotskyi-trace-mcp?style=directory)](https://allmcps.com/mcp/nikolai-vysotskyi-trace-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/nikolai-vysotskyi-trace-mcp"><img src="https://allmcps.com/api/badge/nikolai-vysotskyi-trace-mcp?style=directory" alt="Trace MCP on AllMCPs" /></a>