Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/DeusData/codebase-memory-mcp/llms.txt

Use this file to discover all available pages before exploring further.

Codebase Memory MCP ships an optional built-in graph visualization UI that renders your entire knowledge graph as an interactive 3D scene directly in your browser. Functions, call chains, modules, HTTP routes, and cross-service links all appear as navigable nodes and edges — no external tool, no Gephi export, no separate graph database required. The UI is bundled as an embedded HTTP server inside the binary and runs as a background thread alongside the MCP server, so it is available whenever your agent is connected.
The 3D visualization renders functions, call chains, modules, and HTTP routes as navigable nodes and edges directly in your browser — no external tool or separate graph database required.

Getting the UI Variant

The standard binary does not include the UI. You need to specifically download or install the ui variant.
Pass the --ui flag to the install script:
curl -fsSL https://raw.githubusercontent.com/DeusData/codebase-memory-mcp/main/install.sh | bash -s -- --ui

Starting the UI Server

Once you have the UI variant installed, start it with:
codebase-memory-mcp --ui=true --port=9749
Then open http://localhost:9749 in your browser.
The --port flag defaults to 9749. You can change it to any available port. The MCP server (stdio) continues to run normally alongside the UI — your agent connection is not affected.

What You Can Explore

The 3D graph scene renders every node and relationship in your knowledge graph. Pan, zoom, and rotate to navigate large codebases:

Functions & Call Chains

Follow CALLS edges visually to trace execution paths through your codebase — the same traversal that trace_path performs, rendered as an interactive graph.

Modules & Packages

See how packages cluster around each other. Louvain community detection groups tightly coupled nodes, so functional boundaries appear as natural visual clusters.

HTTP Routes

Route nodes appear as first-class entities. HTTP_CALLS edges show cross-service dependencies as visible links between clusters.

Cross-Service Links

gRPC, GraphQL, tRPC, and pub-sub channel connections (EMITS / LISTENS_ON) are all rendered as labeled edges, making multi-service architectures immediately visible.

Multi-Galaxy Layout

When you have indexed multiple repositories under the same store, the UI switches to a multi-galaxy layout: each repository forms its own spatial cluster (galaxy), and CROSS_* edges connecting nodes across repositories appear as long arcs bridging the galaxies. This makes cross-repo architecture immediately visible — you can see which services call each other, which packages are shared, and where your system’s real boundaries lie.
Index all your microservices or related monorepos with cli index_repository one by one. They share the same SQLite store and the cross-repo links are resolved automatically during indexing.

Troubleshooting

ProblemFix
UI not loading at localhost:9749Confirm you downloaded the ui variant (not the standard binary) and passed --ui=true at startup.
Port already in useChoose a different port: --port=9750
Graph is emptyIndex at least one repository first: codebase-memory-mcp cli index_repository '{"repo_path": "/abs/path"}'

Build docs developers (and LLMs) love