OpenTrace plugin
Plugin that builds a codebase knowledge graph of classes, calls and services, which an agent queries through MCP.
- 111 ★ on the repository
- Last commit
- Apache-2.0
Extended access
Why this level
- Indexing reads the whole repository, and wiki mode sends code fragments to the chosen LLM provider.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/opentraceDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Indexing reads the whole repository, and wiki mode sends code fragments to the chosen LLM provider.
This is third-party code. Review the repository files before installing.
What it does
OpenTrace parses source code through tree-sitter grammars (WASM, 12 languages), extracts classes, functions, imports and calls, and stores the graph in the embedded LadybugDB database. Each node gets a short description from its identifiers, and the graph is opened to the agent through MCP tools. The Claude Code plugin adds five agents (`@opentrace`, `@code-explorer`, `@dependency-analyzer`, `@find-usages`, `@explain-service`) and four commands: `/index`, `/graph-status`, `/explore`, `/interrogate`. The OpenCode plugin gives nine tools, including symbol search, blast-radius analysis and graph traversal. A browser version needs no install.
Who it is for. Developers entering a large codebase who ask an agent to find callers and assess the impact of a change through the graph.
Good fit when
- Before editing a function, all callers and dependent modules must be seen.
- A newcomer is walked through a service top-down using the graph.
- A repository is indexed with one command so the agent does not read files blindly.
- The graph is explored in the browser without installing anything.
Not a fit when
- Code cannot go to third-party LLM providers in wiki mode.
- The repository uses a language outside the list and enters the graph only as files.
- Precise type semantics are needed instead of structural parsing.
Example request
Index the current project and show everything that calls the payment function, with a blast-radius estimate.Limitations
Full extraction (symbols, calls, imports) covers Python, TypeScript, JavaScript and Go. For Rust, Java, Kotlin, C#, C/C++, Ruby and Swift only symbols are extracted. Wiki mode calls an LLM provider (Anthropic, Gemini, OpenAI or local), and code fragments go to the chosen provider. The CLI and plugins need `uv`, and a source build needs Node 22+ and Python 3.12+. Node descriptions are built from identifiers by template rather than from the meaning of code, so for complex logic compare the agent conclusions with the source.
How to disable. In Claude Code remove the `opentrace-oss` plugin through the `/plugin` menu. Clean local indexes and graph databases separately.
FAQ
Which languages are fully parsed?
Python, TypeScript, JavaScript and Go: symbols, calls and imports. For other supported languages only symbols are extracted.
Can the graph be connected to Gemini CLI?
Yes, with `gemini mcp add opentraceai uvx opentraceai mcp`.
Where does code go during indexing?
Parsing runs locally, in the browser or in your process. Only wiki mode calls the selected LLM provider.
What does `/graph-status` show?
An overview of indexed nodes by type. `/index` creates or refreshes the index of the current project.
Can I try it without installing?
Yes, in the browser at `app.opentrace.ai`: indexing and graph viewing run on the browser side.
Discussion
No questions or reviews yet.
Related
PluginsDeep Graph MCP: a code graph of a repository for agents
Deep Graph MCP
An MCP server that gives an agent a repository code graph: search by meaning, symbol links and the places an edit would touch
A local semantic code index: the agent searches by meaning, then follows hits into definitions, callers and dependency paths
A local MCP server with call graphs and symbol search: the agent sees code structure and what an edit affects in advance.
A Claude Code and Codex plugin with skills for code research, tests, refactoring and independent review of finished changes
Local code graph for agents: an MCP server returns entry points, symbol links and change impact in one call
A local code graph with version history: an MCP server that tells the agent who calls a function and what an edit breaks
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| OpenTrace (this card) | no | 111 | ||
| CodeGraph | no | not required | 77,481 | indexes code into a graph for agent navigation; OpenTrace adds a browser viewer, wiki mode and an OpenCode plugin |
| code-graph-rag | no | not required | 5,349 | builds a code graph for natural-language questions; OpenTrace serves the graph through MCP tools and plugin commands |
README in short
The agent queries a graph instead of reading files: callers, dependencies and blast radius are found through relations.