deep-directory-tree-mcp
This server provides functionality for visualizing and analyzing directory structures with customizable options:
Get deep directory tree: Retrieve the directory tree structure for a specified path.
Configurable depth: Customize the maximum depth of the directory tree (default: 3).
Pattern-based exclusion: Exclude specific directories or files using patterns (default exclusions: node_modules, .git, .turbo, dist, .next).
Absolute path support: Works best with absolute paths for accurate tree generation.
Required runtime for development of the MCP server
Required runtime environment for the MCP server, used to analyze and visualize directory structures
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., "@deep-directory-tree-mcp show me the project structure up to depth 3"
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.
Deep Directory Tree MCP 🌳
A powerful Model Context Protocol (MCP) implementation for visualizing and analyzing directory structures. Why? Now you can let AI assistants understand and navigate your project structure efficiently, enabling smarter code navigation and project organization insights.
Built with:
Features
Deep directory tree visualization
Configurable depth-based tree generation
Smart pattern-based file/directory exclusion
Clean and readable tree output format
Real-time directory structure updates
Targeted directory analysis
DEMO:
Related MCP server: MCP Filesystem Server
Quick Start
Prerequisites
Node.js (v18 or higher)
Smithery Installation
The easiest way to get started is using Smithery:
npx -y @smithery/cli install @andredezzy/deep-directory-tree-mcp --client cursorManual Installation
Cursor IDE Setup
Open Cursor Settings → MCP → Add new MCP server
Configure with these settings:
{ "deep-directory-tree": { "command": "npx", "args": ["-y", "@andredezzy/deep-directory-tree-mcp"] } }
Claude Desktop Setup
Add the following to your MCP configuration:
{
"mcpServers": {
"deep-directory-tree": {
"command": "npx",
"args": ["-y", "@andredezzy/deep-directory-tree-mcp"]
}
}
}Usage
Common commands for AI assistants:
"Show me the directory structure"
"Visualize project tree up to depth 4"
"Show files excluding test directories"
Development
Prerequisites
Bun Runtime (required)
# Clone the repository
git clone https://github.com/andredezzy/deep-directory-tree-mcp.git
cd deep-directory-tree-mcp
# Install dependencies
bun install
# Build the project
bun run buildDevelopment Manual Installation
Cursor IDE Setup
Open Cursor Settings → MCP → Add new MCP server
Configure with these settings:
{ "deep-directory-tree": { "command": "node", "args": ["ABSOLUTE_PATH_TO_MCP_SERVER/bin/deep-directory-tree.js"] } }
Claude Desktop Setup
Add the following to your MCP configuration:
{
"mcpServers": {
"deep-directory-tree": {
"command": "node",
"args": ["ABSOLUTE_PATH_TO_MCP_SERVER/bin/deep-directory-tree.js"]
}
}
}Contributing
Fork the repository
Create feature branch (
git checkout -b feature/amazing-feature)Commit changes (
git commit -m 'Add feature')Push to branch (
git push origin feature/amazing-feature)Open a Pull Request
Support
Need help? Try these resources:
License
MIT License - see LICENSE file for details.
Available Tools
1 toolget_deep_directory_treeC
Get deep directory tree
Inputs: path (required), options.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool's purpose is clearly distinct by default.
A single tool inherently follows a consistent naming pattern, as there are no other tools to compare against. The name 'get_deep_directory_tree' uses a clear verb_noun structure.
One tool is too few for a server named 'deep-directory-tree-mcp', which suggests a scope that might include operations like listing, filtering, or modifying directory trees. A single get operation feels thin and incomplete for this domain.
The tool surface is severely incomplete for a directory tree domain. It only provides a get operation, with obvious gaps such as creating, updating, deleting, or searching directory trees, which are essential for basic CRUD coverage.
Maintenance
Related MCP Connectors
AI-powered codebase analysis — call graphs, security, dead code, complexity. 150+ tools.
Code intelligence platform for AI agents. 20 tools for architecture, security & impact analysis.
Code-map tools for AI agents: see a repo's structure first, then edit only what matters.
AI Agent with Architectural Memory. Impact analysis (free), tests and code from the graph (pro).
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables comprehensive directory analysis and file management operations including project structure exploration, intelligent file search, full CRUD operations on files and directories, batch operations with rollback capabilities, and Git integration.134MIT
- AlicenseNot gradedqualityDmaintenanceProvides LLM-optimized tools for advanced code analysis, repository complexity evaluation, and call graph generation. It enables users to visualize directory structures, detect code patterns, and build semantic context with significant token savings.11 npmMIT
- AlicenseBqualityDmaintenanceEnables token-efficient semantic search and analysis over any directory of files through hybrid search, directory overview, structural analysis, and dependency graphs.1418 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceProvides a dependency graph of any local repository with tools for change impact, transitive dependents, health audits, and more, enabling AI coding agents to see structure and refactor safely.4,912 npm4MIT