Enhanced Directory Context MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| set_working_directoryC | Set the working directory for context extraction |
| get_directory_structureC | Get the complete directory structure with file metadata |
| get_file_contentsC | Read contents of specific files |
| search_filesC | Search for content within files using regex or text matching |
| analyze_project_contextC | Analyze the project structure and provide intelligent context summary |
| get_git_contextC | Extract Git repository context (branch, recent commits, status) |
| create_fileC | Create a new file with specified content |
| update_fileB | Update specific parts of a file using search and replace |
| append_to_fileC | Append content to the end of a file |
| delete_fileC | Delete a file |
| rename_fileC | Rename or move a file |
| create_directoryC | Create a new directory |
| batch_file_operationsB | Perform multiple file operations in a single transaction |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Directory Overview | Overview of /app |
| package.json | Contents of package.json |
| readme.md | Contents of readme.md |
| server.js | Contents of server.js |
TDQS
Scored across 13 tools
Most tools have distinct purposes targeting specific file/directory operations, but some overlap exists: 'update_file' and 'append_to_file' both modify file content, and 'get_directory_structure' and 'analyze_project_context' both provide structural insights, though descriptions help differentiate them.
All tools follow a consistent verb_noun pattern with clear, descriptive names (e.g., 'create_file', 'delete_file', 'get_file_contents'). There are no deviations in naming conventions, making the set predictable and readable.
With 13 tools, this server is well-scoped for directory and file management, covering essential operations like create, read, update, delete, search, and context extraction. Each tool serves a clear purpose without bloat.
The toolset provides comprehensive coverage for file system operations, including CRUD for files/directories, content manipulation, searching, and context extraction (e.g., Git, project analysis). There are no obvious gaps that would hinder agent workflows in this domain.