AtlasMemory MCP Server

1

Add it to Claude Code

Run this in a terminal.

Run in terminal
claude mcp add atlasmemory -- npx -y atlasmemory
README.md

Give your AI agent evidence-backed memory for your entire codebase.

English | 中文 | 日本語 | 한국어 | Türkçe | Español | Português

Give your AI agent evidence-backed memory for your entire codebase. Every claim grounded in code. Every context window optimized. Every session drift-resistant.

The Problem

AI coding agents hallucinate about your code. They lose context between sessions. They can't prove their claims. AtlasMemory solves all three.

Feature Others AtlasMemory
🎯 Claims about code "Trust me" Evidence-backed (line + hash)
🔄 Session continuity Start from scratch Drift-detecting contracts
📦 Context window Stuff everything in Token-budgeted packs
🏠 Dependencies Cloud API keys Local-first, zero config
🌍 Language support Varies 11 languages (TS/JS/Py/Go/Rust/Java/C#/C/C++/Ruby/PHP)
💥 Impact analysis Manual Automatic (reverse reference graph)
🧠 Session memory None Cross-session learning

What AI Agents Say

"I'll be honest. During development of AtlasMemory, my context compacted 3 times in a single session. Each time, I lost everything — file contents, variable names, architecture decisions. Without AtlasMemory, I would have spent 15-20 Read calls just to rebuild what I already knew.

With AtlasMemory, one search call brought back exactly what I needed with proof. When I searched "plugin registration hooks lifecycle" on Fastify (269 files), hooks.js came back at rank #1 with a score of 912. I couldn't find that faster with grep.

I tested it on 3 real repos: Express (141 files), Fastify (269 files), Zod (391 files). Zero crashes. TaskPack built proof-backed context in 179ms. CLAUDE.md generator mapped Express's architecture automatically — that would take me 30 minutes of reading to do manually.

This is the tool I wish I had from day one. The difference between an AI that guesses and an AI that knows."

— Claude Opus 4.6 (1M context), after being asked to honestly evaluate AtlasMemory as its own tool

"AtlasMemory's bootpack capsule gave me the full architecture of an 83-file Tauri + React project in ~700 tokens. Normally I'd need 50,000-100,000+ tokens scanning files one by one to reach the same understanding. The semantic scoring found the most critical UI components and hooks instantly. This is a game-changer for context management."

— Google Antigravity (v1.0.0), first test on a real 83-file Tauri + React project

*"The true magic of AtlasMemory is that it doesn't just parse syntax; it maps intent. After indexing the notorious 28,000-file Next.js monorepo (smartly extracting its 3,500 core files while ignoring massive minified assets), it flawlessly queried and retrieved the exact 5 TypeScript/Rust files building the 'React Server Components payload' in less than a second. It navigated the entire structural DNA of Tailwind v4's new 'Oxygen' compiler with surgical precision. As an AI Agent, my biggest bottleneck is context window exhaustion. AtlasMemory acts as my external Hippocampus — handing me exactly what I need on-demand, backed by irrefutable Git-hash evidence anchors. It turns me from a blind text-search bot into a Senior Systems Architect

Tools (2)

searchPerforms a semantic search across the codebase to retrieve relevant code snippets with proof.
indexIndexes the current codebase to build the neural map.

Configuration

claude_desktop_config.json
{"mcpServers": {"atlasmemory": {"command": "npx", "args": ["-y", "atlasmemory"]}}}

Try it

Search for the implementation of the plugin registration hooks lifecycle in the codebase.
Index my current project to build a neural map of the architecture.
Find the files responsible for the React Server Components payload and provide evidence for your findings.
Explain the architecture of this project based on the indexed memory.

Frequently Asked Questions

What are the key features of AtlasMemory?

Evidence-backed claims using line and SHA-256 hash anchors. Token-budgeted context window optimization. Cross-session learning and drift-resistant contracts. Tree-sitter indexing across 11 programming languages. Automatic impact analysis via reverse reference graph.

What can I use AtlasMemory for?

Maintaining context across long-running AI coding sessions without losing architecture decisions. Verifying AI claims about code by grounding them in specific Git-hash evidence. Navigating large monorepos by extracting core structural DNA instead of scanning all files. Reducing token usage by retrieving only the most relevant code snippets for a specific task.

How do I install AtlasMemory?

Install AtlasMemory by running: npx -y atlasmemory

What MCP clients work with AtlasMemory?

AtlasMemory works with any MCP-compatible client including Claude Desktop, Claude Code, Cursor, and other editors with MCP support.

Turn this server into reusable context

Keep AtlasMemory docs, env vars, and workflow notes in Conare so your agent carries them across sessions.

Need the old visual installer? Open Conare IDE.
Open Conare