codebase-memory-mcp-intelligence

Index source code into a persistent knowledge graph for structural queries.

7|2|Updated May 16, 2026
One-click install
npx skills add https://github.com/Aradotso/mcp-skills --skill codebase-memory-mcp-intelligence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-memory-mcp-intelligence
Source: https://github.com/Aradotso/mcp-skills/tree/main/skills/codebase-memory-mcp-intelligence
Command: npx skills add https://github.com/Aradotso/mcp-skills --skill codebase-memory-mcp-intelligence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

codebase-memory-mcp-intelligence eliminates the time-consuming guesswork of understanding large codebases by indexing source structure into a persistent knowledge graph that can be searched, traced, and analyzed on demand.

Core Features & Use Cases

  • Graph-based code intelligence: Model functions, classes, calls, imports, and architecture boundaries as queryable nodes and edges for structural and dependency questions.
  • Fast structural and semantic search: Locate symbols by pattern, trace call chains, run Cypher-like queries, and run concept-based semantic search using bundled embeddings without requiring an external API key.
  • Architecture, routes, and risk analysis: Generate architectural summaries, list HTTP/gRPC/GraphQL routes, detect dead code, and perform change impact analysis using a call graph plus confidence/risk scoring.

Quick Start

Ask: "Index this repository and show me the architecture."

Frequently Asked Questions about codebase-memory-mcp-intelligence

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace function calls and analyze change impact in a large codebase?

Codebase change impact analysis traces function calls by indexing source structure into a persistent knowledge graph, allowing you to query call chains and calculate risk scores for modifications. It maps dependencies to show exactly what breaks when code changes.

What is the best way to find dead code and unused functions across a repository?

Dead code detection identifies unused functions by modeling your repository as a queryable graph of nodes and edges. By running graph queries against the indexed codebase, you can locate symbols with no incoming calls and safely remove them.

How does semantic search work for source code without an external API key?

Semantic code search works without external API keys by using bundled embeddings to index and retrieve code concepts. It enriches the source structure graph so you can locate symbols and logic by meaning rather than exact string matching.

Can I generate an architecture summary and list HTTP routes from a medium to large repository?

Yes, you can generate architecture summaries and list HTTP or gRPC routes for medium to large repositories. The codebase intelligence server indexes the source structure and extracts architectural boundaries and route definitions as queryable graph nodes.

Do I need to install any dependencies or API keys to run codebase graph queries?

No external API keys or dependencies are required to run codebase graph queries. The intelligence server uses bundled embeddings and local indexing, allowing you to execute Cypher-like queries and structural searches entirely offline.

Why use a knowledge graph for code intelligence instead of standard text search?

A knowledge graph provides code intelligence by mapping functions, classes, and imports as structural nodes and edges, whereas standard text search only matches strings. This graph modeling enables deep call tracing, route discovery, and dependency analysis.