CodeAtlas MCP Server
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
CodeAtlas MCP Server
Local-first, high-performance native Rust Model Context Protocol (MCP) server for AI-powered codebase intelligence — AST analysis, dependency graphs, and semantic code intelligence. Your source code never leaves your machine.
📌 What is CodeAtlas MCP Server?
A high-performance Model Context Protocol (MCP) server built in Rust that provides:
Tree-sitter AST Analysis: Deep parsing for TypeScript, JavaScript, Python, PHP, Rust, and more.
Dependency & Call Graphs: Fast petgraph-backed module relationships, caller/callee tracing, and cycle detection.
Semantic Code Search: Instant search and indexing across multi-repository workspaces.
Local-First & Private: Code execution stays entirely on your local machine; zero telemetry by default.
Cloud Optional: Seamless integration with codeatlas-platform for persistent dream memory and immune genome verification.
Why Use It?
Use Case | Benefit |
AI IDE Integration | Claude Desktop, Cursor, Zed, VSCode — instant context-aware code intelligence. |
Codebase Audits | Automated call graph analysis, architectural smell detection, and impact tracing. |
Semantic Code Search | Locate functions, types, and logic patterns across complex polyglot repos. |
Native Performance | Instant cold starts, minimal RAM footprint, and jemalloc-optimized concurrency. |
Related MCP server: localscope-mcp
🏗 Architecture
AI Client (Claude / Zed / Cursor)
│ (JSON-RPC over stdin/stdout)
▼
MCP Transport Adapter (crates/codeatlas-adapters)
│
Application Use Cases (crates/codeatlas-application)
│
Pure Domain Entities & Ports (crates/codeatlas-domain)
│
Infrastructure Engines (crates/codeatlas-infrastructure)
├── Tree-sitter Parser
├── Petgraph Store
└── Local Cache & Watchers🚀 Quick Start
1. Install via Cargo (crates.io)
cargo install codeatlas-cli --locked2. Or Install via One-Line Shell Script (macOS / Linux)
curl --proto '=https' --tlsv1.2 -fsSL https://raw.githubusercontent.com/giauphan/codeatlas-mcp-rust/main/install.sh | bash3. Or Build from Source
git clone https://github.com/giauphan/codeatlas-mcp-rust.git
cd codeatlas-mcp-rust
cargo build --releaseThe compiled binary will be located at target/release/codeatlas.
📡 MCP Tools
CodeAtlas provides a comprehensive suite of MCP tools across multiple categories:
Category | Tools |
Code Analysis |
|
Dependencies & Graphs |
|
Security & Quality |
|
Cloud Memory (Optional) |
|
Second Brain & Genome |
|
Workspace & Utilities |
|
💻 Client Configuration Examples
Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"codeatlas": {
"command": "codeatlas",
"args": []
}
}
}Zed Editor
Run the automatic setup command:
codeatlas setup-zedOr manually add to ~/.config/zed/settings.json:
{
"context_servers": {
"codeatlas": {
"command": "codeatlas",
"args": []
}
}
}Cursor / VSCode
Configure in your Cursor or VSCode MCP settings:
{
"mcpServers": {
"codeatlas": {
"command": "codeatlas",
"args": []
}
}
}🔒 Security & Environment Variables
CodeAtlas MCP Server operates locally by default over standard I/O with strict boundary protections:
Environment Isolation: API tokens are read directly from process environment variables and masked from diagnostic outputs.
Whitelisted Cloud Destinations: Outbound cloud requests are strictly restricted to verified endpoints (
*.codeatlas.ai,opencode.ai,127.0.0.1,localhost).Symlink Protection: Filesystem queries enforce boundary validation to prevent unauthorized directory traversal.
Variable | Description | Default |
| Optional key to connect to CodeAtlas Cloud services for shared memory. | (none) |
| Optional base URL for CodeAtlas Cloud backend. | (none) |
| Set to |
|
⚠️ Operational Considerations & Boundaries
CodeAtlas MCP Server is designed as a local-first, low-overhead native binary. Keep the following operational boundaries in mind:
Local-First & Zero Database Footprint:
The server operates entirely standalone and requires no database servers (such as Oracle, PostgreSQL, or Redis).
All AST dependency graphs, call hierarchies, and indexing structures are maintained in-memory using Petgraph and backed by local filesystem caches (
~/.codeatlas/).Optional cloud features (dream memory and immune genome synchronization) connect to upstream CodeAtlas Platform services via HTTPS only when
CODEATLAS_API_KEYandCODEATLAS_API_URLare explicitly configured.
Single-Tenant Process Isolation:
CodeAtlas executes as a dedicated child process attached to your AI client (Claude Desktop, Zed, Cursor, VS Code) via standard input/output (
stdio).Process execution boundaries, file system permissions, and workspace access align directly with the user account running the IDE. Multi-user isolation is enforced by the host operating system.
Network Boundaries & No Open Ports:
CodeAtlas does not listen on any network ports or expose an HTTP/SSE server. Reverse proxies (such as Nginx) and external firewall port forwarding are unnecessary.
Outbound cloud communication is strictly allowlisted to official CodeAtlas domains (
*.codeatlas.ai,opencode.ai) or local loopback (127.0.0.1,localhost). Non-local unencrypted HTTP traffic is rejected.
Static Analysis Scope:
Code analysis is performed statically using Tree-sitter AST parsers. It does not execute untrusted user code or evaluate runtime bytecode.
Repository graph size is bound by available host RAM. Concurrency and allocations are optimized with Tokio and jemalloc.
📚 Resources & Community
📖 Development Guide — Local development workflow and commands.
🚀 Pipeline Runbook — CI quality gates and crates.io CD automation.
🛡️ Security Policy — Vulnerability reporting and supported versions.
🤝 Contributing Guidelines — How to contribute, commit conventions, and code standards.
📜 Code of Conduct — Community standards and pledge.
📄 MIT License — Open-source license terms.
🐛 Issues & Support
Report bugs or request features: GitHub Issues
Community discussions: GitHub Discussions
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Code intelligence for coding agents: semantic, AST, graph, and full-text search. 279+ languages.
Code intelligence platform for AI agents. 20 tools for architecture, security & impact analysis.
Give your AI agent a persistent map of your project's structure, dependencies, and bugs.
Shared memory for coding agents. Stop re-explaining your codebase every session.
Related MCP Servers
- AlicenseAqualityBmaintenanceSelf-hosted semantic code search for AI coding agents. Indexes many repositories at once with tree-sitter AST chunking, local llama.cpp embeddings and Qdrant, so Claude Code, Cursor, Codex and any MCP client can find code by meaning, trace usages and callers, and read the git history behind each chunk. No API keys, and your code never leaves your machine.21834MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to analyze a local codebase and answer impact questions like 'what breaks if I change Y?' through local indexing, search, and reverse dependency analysis, with no code leaving the machine.425 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to query a local semantic code graph for surgical context, cross-file resolution, framework-aware routes, and code intelligence while keeping indexes automatically up to date.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents and developers to search code by meaning and exact text, map symbols, dependencies, blast radius and context, inspect git-change impacts, and trace live Python or JavaScript execution from a local air-gapped SQLite index.Apache 2.0