Data · MODEL CONTEXT PROTOCOL

admica FileScopeMCP

Analyzes your codebase identifying important files based on dependency relationships. Generates diagrams and importance scores per file, helping AI assistants understand the codebase. Automatically parses popular programming languages such as Python, C, C++, Rust, Zig, Lua.

WHAT IT CONNECTS

What admica FileScopeMCP gives an AI Agent

  • **🎯 File Importance Analysis**
  • Rank files on a 0-10 scale based on their role in the codebase.
  • Calculate importance using incoming/outgoing dependencies.
  • Instantly pinpoint the most critical files in your project.
  • Smart calculation considers file type, location, and name significance.
  • **🔗 Dependency Tracking**
  • Map bidirectional dependency relationships between files.
  • Identify which files import a given file (dependents).
  • See which files are imported by a given file (dependencies).
  • Distinguish between local and package dependencies.
  • Multi-language support: Python, JavaScript, TypeScript, C/C++, Rust, Lua, Zig.
  • **📊 Visualization**
  • Generate Mermaid diagrams to visualize file relationships.
  • Color-coded visualization based on importance scores.
  • Support for dependency graphs, directory trees, or hybrid views.
  • HTML output with embedded rendering including theme toggle and responsive design.
  • Customize diagram depth, filter by importance, and adjust layout options.
  • **📝 File Summaries**
  • Add human or AI-generated summaries to any file.
  • Retrieve stored summaries to quickly grasp file purpose.
  • Summaries persist across server restarts.
  • **📚 Multiple Project Support**
  • Create and manage multiple file trees for different project areas.
  • Configure separate trees with distinct base directories.
  • Switch between different file trees effortlessly.
  • Cached trees for faster subsequent operations.
  • **💾 Persistent Storage**
  • All data automatically saved to disk in JSON format.
  • Load existing file trees without rescanning the filesystem.
  • Track when file trees were last updated.
  • Clone this repository
  • Build the project:
  • Update the arg path --base-dir to your project's base path.
  • Python: `import` and `from ... import` statements
  • JavaScript/TypeScript: `import` statements and `require()` calls
  • C/C++: `#include` directives
  • Rust: `use` and `mod` statements
  • Lua: `require` statements
  • Zig: `@import` directives
  • Number of files that import this file (dependents)
  • Number of files this file imports (dependencies)
  • File type and extension (with TypeScript/JavaScript files getting higher base scores)
  • Location in the project structure (files in `src/` are weighted higher)
  • File naming (files like 'index', 'main', 'server', etc. get additional points)
  • Collection Phase: Register all nodes and relationships
  • Node Definition Phase: Generate definitions for all nodes before any references
  • Edge Generation Phase: Create edges between defined nodes
  • Responsive design that works on any device
  • Light/dark theme toggle with system preference detection
  • Client-side Mermaid rendering for optimal performance
  • Timestamp of generation
  • Windows and Unix path formats
  • Absolute and relative paths
  • URL-encoded paths
  • Cross-platform compatibility
  • Configuration metadata (filename, base directory, last updated timestamp)
  • Complete file tree with dependencies, dependents, importance scores, and summaries
  • **TypeScript/Node.js**: Built with TypeScript for type safety and modern JavaScript features
  • **Model Context Protocol**: Implements the MCP specification for integration with Cursor
  • **Mermaid.js**: Uses Mermaid syntax for diagram generation
  • **JSON Storage**: Uses simple JSON files for persistence
  • **Path Normalization**: Cross-platform path handling to support Windows and Unix
  • **Caching**: Implements caching for faster repeated operations
  • **list_saved_trees**: List all saved file trees
  • **create_file_tree**: Create a new file tree configuration for a specific directory
  • **select_file_tree**: Select an existing file tree to work with
  • **delete_file_tree**: Delete a file tree configuration
  • **list_files**: List all files in the project with their importance rankings
  • **get_file_importance**: Get detailed information about a specific file, including dependencies and dependents
  • **find_important_files**: Find the most important files in the project based on configurable criteria
  • **read_file_content**: Read the content of a specific file
  • **recalculate_importance**: Recalculate importance values for all files based on dependencies
  • **get_file_summary**: Get the stored summary of a specific file
  • **set_file_summary**: Set or update the summary of a specific file
  • **toggle_file_watching**: Toggle file watching on/off
  • **get_file_watching_status**: Get the current status of file watching
  • **update_file_watching_config**: Update file watching configuration
  • **generate_diagram**: Create Mermaid diagrams with customizable options
  • Output formats: Mermaid text (`.mmd`) or HTML with embedded rendering
  • Diagram styles: default, dependency, directory, or hybrid views
  • Filter options: max depth, minimum importance threshold
  • Layout options: direction (TB, BT, LR, RL), node spacing, rank spacing
  • Create a file tree for your project:
  • Find the most important files:
  • Get detailed information about a specific file:
  • Read a file's content to understand it:
  • Add a summary to the file:
  • Retrieve the summary later:
  • Create a basic project structure diagram:
  • Generate an HTML diagram with dependency relationships:
  • Customize the diagram layout:
  • Enable file watching for your project:
  • Check the current file watching status:
  • Update file watching configuration:
  • Add support for more programming languages
  • Add more sophisticated importance calculation algorithms
  • Enhance diagram customization options
  • Support for exporting diagrams to additional formats

SECURITY

An MCP listing is not a security review

An MCP server may receive model context, credentials, local files, or permission to call external systems. Review its code, requested environment variables, network behavior, package provenance, and maintenance status before connecting it to an agent.