FileScopeMCP
The FileScopeMCP server helps understand codebase structure and dependencies through these capabilities:
File Tree Management: Create, select, list, and delete file tree configurations for different projects
Dependency Analysis: Track bidirectional dependencies across multiple languages (Python, JS/TS, C/C++, Rust, Lua, Zig)
Importance Handling: Calculate, recalculate, and manually set file importance scores (0-10) based on dependencies
File Operations: List files with importance rankings, find important files, and read file content
File Summaries: Add, retrieve, and persist human or AI-generated summaries for specific files
Visualization: Generate Mermaid diagrams in various styles (dependency, directory, hybrid) with filtering and layout options
Auto-updates: Toggle file watching to automatically update when files change
Persistence: Store all file tree data including dependencies, importance, and summaries in JSON files
Analyzes C/C++ source files by detecting #include directives to map dependencies and calculate importance scores for files in C/C++ projects.
Analyzes JavaScript files by detecting import statements and require() calls to track dependencies and assign importance scores to files in JavaScript projects.
Analyzes Lua source files by detecting require statements to map dependencies and calculate importance scores for files in Lua projects.
Generates Mermaid diagrams to visualize file relationships with color-coded visualization based on importance scores for dependency graphs or directory trees.
Analyzes Python source files by detecting import and from...import statements to map dependencies and calculate importance scores for files in Python projects.
Analyzes Rust source files by detecting use and mod statements to map dependencies and calculate importance scores for files in Rust projects.
Provides enhanced support for TypeScript projects by analyzing import statements, tracking dependencies, and assigning higher base importance scores to TypeScript files.
Analyzes Zig source files by detecting @import directives to map dependencies and calculate importance scores for files in Zig projects.
Click on "Install 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., "@FileScopeMCPshow me the most important files in my project"
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.
FileScopeMCP
Your AI already knows how to code. Now it knows your codebase.
FileScopeMCP watches your code, ranks every file by importance, maps all dependencies, and keeps AI-generated summaries fresh in the background. When your LLM asks "what does this file do?" — it gets a real answer without reading the source.
Works with Claude Code, Cursor AI, or as a standalone daemon. Supports 12 languages out of the box.
Key Features
Importance ranking — every file scored 0-10 based on how many things depend on it, what it exports, and where it lives. Your LLM sees the critical files first.
Dependency mapping — bidirectional import tracking across Python, JS/TS, C/C++, Rust, Go, Ruby, Lua, Zig, PHP, C#, Java. Finds circular dependencies too.
Always fresh — file watcher + semantic change detection means metadata updates automatically. AST-level diffing for TS/JS, LLM-powered analysis for everything else. Only re-processes what actually changed.
LLM broker — a background process coordinates all AI work through llama.cpp's llama-server (or any OpenAI-compatible HTTP API). Priority queue ensures interactive queries beat background processing. Runs on a single GPU.
Nexus dashboard — a web UI at localhost:1234 that lets you visually explore your codebase across all your repos. Interactive dependency graphs, file detail panels, live broker activity, and per-repo health monitoring.
Related MCP server: SourceSage MCP
Quick Start
git clone https://github.com/admica/FileScopeMCP.git
cd FileScopeMCP
./build.sh # installs deps, compiles, registers with Claude CodeThat's it. Open a Claude Code session in any project and FileScopeMCP auto-initializes. Try:
find_important_files(limit: 5)
status()Want AI summaries? Run ./setup-llm.sh for a platform-specific guide to setting up llama.cpp's llama-server — see docs/llm-setup.md for details. Without it, everything else still works.
Add to your project's .gitignore:
.filescope/
.filescope-daemon.logMCP Tools
Tool | What it does |
| Top files by importance score |
| Everything about a file: summary, concepts, change impact, deps, staleness |
| Full file tree with importance |
| Find circular dependency chains |
| Broker connection, queue depth, LLM progress, watcher state |
| Queue entire codebase for LLM processing |
| Point at a different project |
| Manual overrides |
| Drop files/patterns from tracking |
| Cycles involving a specific file |
Nexus Dashboard
npm run nexus # opens at http://localhost:1234A read-only web dashboard that connects to every FileScopeMCP repo on your machine:
Project view — file tree with importance heat colors and staleness indicators, click any file for full metadata
Dependency graph — interactive Cytoscape.js visualization, filter by directory, click nodes to inspect
System view — live broker status, per-repo token usage, streaming activity log
Settings — manage which repos appear, remove or restore from blacklist
Auto-discovers repos by scanning for .filescope/data.db directories. No configuration needed.
How It Works
Your code changes
→ file watcher picks it up
→ AST diff classifies the change (exports? types? body only?)
→ importance scores recalculated
→ staleness cascades to dependents (only if exports/types changed)
→ LLM broker regenerates summaries, concepts, change impact
→ your AI's next query gets fresh answersEverything lives in .filescope/data.db (SQLite, WAL mode) per project. The broker coordinates LLM work across all your repos via a Unix socket at ~/.filescope/broker.sock.
Documentation
Doc | What's in it |
llama.cpp / llama-server installation — local, WSL2+Windows, or remote | |
Per-project config, broker config, ignore patterns | |
Setup for Claude Code, Cursor AI, daemon mode | |
Common issues and fixes | |
Dependency detection, importance formula, cascade engine, storage |
License
Copyright (c) 2026 admica. All rights reserved. See LICENSE.
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/admica/FileScopeMCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server