RepoMind-MCP
Repomind-MCP provides a local, private, and efficient suite of tools for AI coding assistants to understand codebase structure, dependencies, and impact of changes, without loading entire file contents into context.
Workspace Scanning: Use
repomind_scan_workspaceto recursively scan a workspace, producing a file tree, source file listing, and statistics (counts, sizes by type), while automatically ignoring noise likenode_modules,.git, anddist.Dependency Analysis:
repomind_get_dependenciesparses imports in JavaScript, TypeScript, and Python files to build a directed dependency graph showing direct and transitive relationships for a file or directory.Architecture Diagrams:
repomind_generate_diagramcreates a Mermaid diagram of the dependency graph, optionally scoped to specific files or directories and grouped by parent folder into subgraphs.Impact Analysis:
repomind_impact_analysisperforms reverse-dependency BFS from a target file to identify all files that depend on it (directly or indirectly), revealing the blast radius of a change with configurable traversal depth.Raw Graph Access: Exposes a resource
repomind://workspace/graphfor direct JSON inspection of the full dependency graph.Prompt Templates: Provides pre-built prompts
architecture-reviewandblast-radius-checkthat incorporate live project data for structured code reviews.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@RepoMind-MCP analyze dependencies of src/main.ts"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
RepoMind-MCP
A local Model Context Protocol server that gives AI coding assistants a map of your codebase — file structure, import graph, and "what breaks if I change this file" — without dumping the whole repo into the model's context.
It runs entirely on your machine over stdio. No network calls, no uploading code anywhere.
Quick Start
Add this to your MCP client config (e.g. Claude Desktop's claude_desktop_config.json):
{
"mcpServers": {
"repomind-mcp": {
"command": "npx",
"args": ["-y", "repomind-mcp"]
}
}
}Restart your client. The assistant can now call the tools below whenever it needs to understand your project's layout instead of guessing.
Related MCP server: mcp-server-ts-analysis
What it actually does
Ask your assistant something like "what would break if I change src/auth.ts?" or "give me an architecture diagram of this project" — it reaches for one of these tools instead of grepping blindly:
Tool | Answers the question... | Key argument |
| "What's in this project?" — file tree, counts, sizes by type |
|
| "What does this file import, directly and transitively?" |
|
| "Draw me the architecture" — Mermaid diagram grouped by folder |
|
| "What breaks if I change this file?" — reverse dependency BFS |
|
All paths are absolute and everything runs against your local filesystem — node_modules, .git, dist, and other build/binary noise is ignored automatically. Supports JavaScript, TypeScript, and Python import resolution.
Under the hood, a single in-memory dependency graph (keyed by file mtime, see src/cache.ts) backs all four tools, so repeated calls on an unchanged workspace are fast.
Also exposed
Resource
repomind://workspace/graph— the full serialized dependency graph as JSON, for clients that want to inspect it directly rather than calling a tool.Prompts
architecture-reviewandblast-radius-check— pre-built prompt templates that pull in the live file tree / impact analysis so the assistant reviews your actual code, not a hypothetical one.
Local Development
Only needed if you're modifying RepoMind-MCP itself — most users just want the Quick Start above.
npm install
npm run build # compiles src/ (TypeScript) -> dist/ (ESM)
npm start # runs the server on stdioPoint your client at the compiled entry point instead of npx:
{
"mcpServers": {
"repomind-mcp": {
"command": "node",
"args": ["/absolute/path/to/RepoMind-MCP/dist/index.js"]
}
}
}Testing
scratch/test-server.js spins up the built server and drives it through a handful of JSON-RPC tool calls end-to-end:
npm run build && node scratch/test-server.jsLicense
MIT
Available Tools
4 toolsrepomind_generate_diagramB
Generates a beautiful visual Mermaid diagram representing the dependency graph of the files. Can group files by their parent directories into subgraphs.
Inputs: scopePaths, diagramType, workspaceRoot.
repomind_get_dependenciesA
Analyzes imports in JavaScript, TypeScript, and Python files within a target path (file or directory) to build a directed dependency graph showing local module relationships.
Inputs: targetPath (required).
repomind_impact_analysisA
Calculates the downstream blast radius (reverse dependents) of modifying a target file or module, showing exactly which files depend on it directly or indirectly.
Inputs: targetPath (required), depth.
repomind_scan_workspaceA
Recursively scans a workspace directory, mapping its file structure, listing source files, and providing statistics, while ignoring binary/build folders (e.g. node_modules, .git, dist).
Inputs: basePath (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool targets a distinct phase of repository analysis: scanning structure, computing dependencies, generating diagrams, and calculating impact. No overlap or ambiguity exists between them.
All tools follow the consistent pattern 'repomind_<verb>_<object>' with snake_case throughout. The verb-noun construction is uniform and predictable across the set.
Four tools is an ideal size for a focused repository analysis server. Each tool earns its place and there is no bloat or redundancy.
The tool set forms a complete workflow: scan a workspace, extract dependencies, visualize them, and analyze impact. No obvious gaps exist for the stated purpose of repository analysis.
Maintenance
Related MCP Connectors
Repository knowledge graph MCP server for codebase understanding and debugging.
One MCP server for all your MCP servers: code mode, per-tool permissions, approvals and audit.
A MCP server built for developers enabling Git based project management with project and personal…
MCP server for static security analysis of Android source code
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceMCP server for automated architectural mapping, security vulnerability detection, ML asset tracking, and code metrics in local repositories.-
- FlicenseBqualityDmaintenanceMCP server for TypeScript type resolution and dependency graph analysis using ts-morph and madge.82-
- AlicenseAqualityDmaintenanceMCP server that analyzes TypeScript/JavaScript codebases via AST parsing and dependency graph tracing to identify affected tests, detect dead code, circular dependencies, and trace import chains, enabling AI agents to run only relevant tests.1554 npmMIT
- AlicenseAqualityCmaintenanceAn MCP server that maps any repository into architecture diagrams, providing tools for scanning code facts, building import graphs, and generating Mermaid/DOT diagrams, plus architecture rule enforcement for CI.554 npm1MIT