CodeAtlas MCP Server
🗺️ Servidor MCP CodeAtlas
Dale a tu asistente de IA una comprensión profunda de cualquier base de código
Un servidor MCP independiente que expone datos de análisis de código a Gemini, Claude, Cursor, Windsurf, VS Code Copilot — con memoria de IA persistente entre conversaciones.
✨ ¿Qué hace?
Your Code → CodeAtlas Analyze → MCP Server → AI Understands Everything
│
10 powerful tools:
• Search functions & classes
• Trace feature flows
• Generate architecture diagrams
• Persistent memory across conversationsAntes de CodeAtlas: La IA busca a ciegas, olvida tu proyecto en cada conversación. Después de CodeAtlas: La IA conoce al instante tu arquitectura, dependencias y recuerda el contexto.
Related MCP server: code-intel MCP Server
🚀 Configuración (1 minuto)
1. Analiza tu proyecto
Instala la extensión CodeAtlas, luego:
Ctrl+Shift+P → CodeAtlas: Analyze Project2. Añade la configuración MCP a tu IA
{
"mcpServers": {
"codeatlas": {
"command": "npx",
"args": ["-y", "@giauphan/codeatlas-mcp"]
}
}
}{
"mcpServers": {
"codeatlas": {
"command": "npx",
"args": ["-y", "@giauphan/codeatlas-mcp"]
}
}
}{
"mcp": {
"servers": {
"codeatlas": {
"command": "npx",
"args": ["-y", "@giauphan/codeatlas-mcp"]
}
}
}
}{
"mcpServers": {
"codeatlas": {
"command": "npx",
"args": ["-y", "@giauphan/codeatlas-mcp"]
}
}
}claude mcp add codeatlas -- npx -y @giauphan/codeatlas-mcp{
"mcpServers": {
"codeatlas": {
"command": "npx",
"args": ["-y", "@giauphan/codeatlas-mcp"]
}
}
}¡Listo! Tu IA ahora puede usar las 10 herramientas de CodeAtlas.
🛠️ 10 Herramientas MCP
Análisis de código (6 herramientas)
Herramienta | Descripción | Ejemplo de uso |
| Lista todos los proyectos analizados | "¿Qué proyectos tengo?" |
| Obtiene módulos, clases, funciones | "Muéstrame todas las clases" |
| Relaciones de importación/llamada/contención | "¿De qué depende UserService?" |
| Análisis de calidad y seguridad del código | "¿Hay problemas de seguridad?" |
| Búsqueda difusa de entidades por nombre | "Encuentra la función de inicio de sesión" |
| Todas las entidades en un archivo específico | "¿Qué hay en auth.ts?" |
Visualización de arquitectura (2 herramientas)
Herramienta | Descripción | Ejemplo de uso |
| Diagrama de arquitectura Mermaid (importaciones de módulos) | "Muéstrame la arquitectura del sistema" |
| Diagrama de flujo de ejecución Mermaid (cadenas de llamadas) | "¿Cómo funciona la función de pago?" |
Memoria de IA (2 herramientas)
Herramienta | Descripción | Ejemplo de uso |
| Guarda el contexto en | "Recuerda lo que cambiamos" |
| Rastrea la funcionalidad a través de la base de código | "¿Qué archivos están involucrados en la autenticación?" |
🧠 Memoria de IA — Contexto persistente
Los asistentes de IA olvidan todo entre conversaciones. CodeAtlas soluciona esto:
Conversation 1 → AI analyzes code → sync_system_memory
│
.agents/memory/
├── system-map.md ← Architecture diagram
├── modules.json ← All entities
├── conventions.md ← Code patterns
├── business-rules.json ← Domain logic
├── feature-flows.json ← Feature traces
└── change-log.json ← Change history
│
Conversation 2 → AI reads memory → full context restored instantly ✨Reglas de IDE autogeneradas
Cuando ejecutas Analyze Project, CodeAtlas crea automáticamente archivos de reglas para tu IDE de IA:
Archivo generado | Para |
| Todos los asistentes de IA |
| Cursor |
| Claude Code |
| Windsurf |
Estos le dicen a tu IA que:
Lea
.agents/memory/al inicio de cada conversaciónUse herramientas MCP antes de realizar cambios
Llame a
sync_system_memorydespués de completar los cambios
🌍 Lenguajes soportados
Lenguaje | Características |
TypeScript / JavaScript | AST completo: importaciones, clases, funciones, variables, llamadas, implementaciones |
Python | Clases, funciones, variables, importaciones, llamadas |
PHP | Clases, interfaces, traits, enums, funciones, propiedades |
Blade Templates |
|
📦 Alternativa: Instalación global
npm install -g @giauphan/codeatlas-mcpLuego usa "command": "codeatlas-mcp" en tu configuración MCP (no se necesitan args).
🔧 Variables de entorno
Variable | Descripción |
| Fuerza un directorio de proyecto específico |
Por defecto, el servidor descubre automáticamente todos los proyectos con
.codeatlas/analysis.jsonbajo~/.
🧑💻 Desarrollo
git clone https://github.com/giauphan/codeatlas-mcp.git
cd codeatlas-mcp
npm install
npm run build
npm test # 6 tests
npm start # Start MCP server🔗 Relacionado
Extensión CodeAtlas — Extensión de VS Code con gráfico de código interactivo
Protocolo MCP — Estándar del Protocolo de Contexto de Modelo
Licencia
MIT — Gratuito para uso personal y comercial.
Available Tools
10 toolsgenerate_feature_flow_diagramA
Generate a Mermaid diagram showing the EXECUTION FLOW of a feature. Unlike generate_system_flow (which shows module imports), this traces the actual call chain: entry point → controller → service → model → database. Given a keyword, it finds all related functions and classes, then builds a flowchart or sequence diagram showing how they call each other at runtime. This is the best tool for understanding HOW a feature works step-by-step.
Inputs: keyword (required), project, diagramType, depth, +1 more.
generate_system_flowB
Auto-generate a Mermaid flowchart diagram showing how modules, classes, and functions connect in the system. Returns a Mermaid diagram string that AI can read to understand the full system flow without reading every file.
Inputs: project, scope, feature, maxNodes.
get_dependenciesB
Get import/call/containment/implements relationships between entities. Shows how modules, classes, and functions are connected.
Inputs: project, source, target, relationship, +1 more.
get_file_entitiesC
Get all entities (classes, functions, variables) defined in a specific file.
Inputs: filePath (required), project.
get_insightsA
Get AI-generated code insights including refactoring suggestions, security issues, and maintainability analysis.
Inputs: no named parameters.
get_project_structureA
Get all modules, classes, functions, and variables in the analyzed project. Returns entity type, name, file path, and line number.
Inputs: project, type, limit.
list_projectsA
List all projects that have been analyzed by CodeAtlas. Returns project names, paths, and last analysis time.
Inputs: no named parameters.
search_entitiesB
Search for functions, classes, modules, or variables by name. Supports fuzzy matching.
Inputs: query (required), project, type.
sync_system_memoryA
Create or update the .agents/memory/ folder with auto-generated system documentation. This folder serves as AI's 'long-term memory' — it persists between conversations. After calling this, AI in any future conversation can read these files to understand the full system flow without re-analyzing. Call this after completing any code changes.
Inputs: project, businessRule, changeDescription.
trace_feature_flowA
Trace the complete flow of a feature through the codebase. Given a keyword (e.g. 'login', 'payment', 'crawl'), finds all related files, classes, and functions, then orders them by dependency chain to show the execution flow. This helps AI understand which files to read when working on a feature.
Inputs: keyword (required), project, depth.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 10 tools
Most tools have distinct purposes. However, `generate_feature_flow_diagram` and `trace_feature_flow` both trace feature flow by keyword, differing only in output format (diagram vs. ordered list). Descriptions help differentiate, but an agent might still select the wrong one for a given need.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., `generate_feature_flow_diagram`, `get_dependencies`, `list_projects`). No mixed conventions or vague verbs.
With 10 tools, the set covers the domain of code analysis and documentation well. Each tool serves a distinct, necessary function without redundancy or bloat.
The tool surface covers core CRUD-like operations for projects and entities, plus advanced analysis (flows, insights, memory sync). Minor gaps exist, such as no tool for editing entities or comparing versions, but core workflows are supported.
Maintenance
Related MCP Connectors
Search indexed code, trace dependencies, assess change impact, and recall repository memory.
The Cortex MCP server provides read-only access to real-time engineering context from the Cortex developer portal, allowing AI coding assistants to answer natural language questions about your organization's catalog (microservices, libraries, domains, teams, infrastructure), scorecards (engineering standards and best practices), initiatives (goals and deadlines), and Engineering Intelligence metrics. It includes tools for querying documentation, tracking personal entities, and accessing AI-assisted insights across the entire Cortex ecosystem.
Give your AI agent a persistent map of your project's structure, dependencies, and bugs.
Code intelligence for LLMs. Analyze, search, and retrieve code from any public git repository.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that analyzes application codebases with real-time file watching, providing AI assistants like Claude with deep insights into project structure, code patterns, and architecture.MIT
- AlicenseNot gradedqualityBmaintenanceProvides LLMs with code intelligence tools like relationship explanation, PR impact analysis, and health reports via the Model Context Protocol.3MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to securely browse, search, inspect, and understand local project files through Model Context Protocol tools.1MIT
- AlicenseNot gradedqualityBmaintenanceTurns a codebase into a queryable graph with semantic search, call graphs, and control/data flow analysis, served to AI coding agents via the Model Context Protocol.182 npmMIT