Edit MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port to listen on for HTTP transport | 3000 |
| DEBUG | No | Enable debug logging | |
| API_KEY | No | API key for authentication when authEnabled is true | |
| TIMEOUT | No | Timeout for Edit instances in milliseconds | 300000 |
| EDIT_PATH | No | Path to the Edit executable | |
| CONFIG_PATH | No | Path to configuration file | |
| MAX_INSTANCES | No | Maximum number of Edit instances | 5 |
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 |
|---|---|
| read_fileB | Read the contents of a file |
| write_fileB | Write content to a file |
| list_filesB | List files in a directory |
| find_in_fileB | Find occurrences of a pattern in a file |
| format_codeB | Format code in a file |
| complex_find_replaceB | Perform advanced find and replace operations with context awareness |
| interactive_edit_sessionB | Start an interactive editing session for complex edits |
| smart_refactorA | Intelligently refactor code by renaming symbols across multiple files |
| backup_and_editB | Create backups of files before editing them |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Most tools have distinct purposes, such as backup_and_edit for safe modifications and smart_refactor for code restructuring. However, find_in_file and complex_find_replace could be confused, as both involve searching, though the latter adds advanced features like context awareness.
All tool names follow a consistent snake_case pattern with clear verb_noun structures, such as read_file and format_code. There are no deviations or mixed conventions, making the naming predictable and easy to understand.
With 9 tools, the count is well-scoped for a file editing server, covering essential operations like reading, writing, and advanced edits. Each tool serves a clear purpose without feeling excessive or insufficient for the domain.
The toolset provides comprehensive coverage for file editing tasks, including basic CRUD operations (list_files, read_file, write_file), advanced features (smart_refactor, format_code), and safety measures (backup_and_edit). No obvious gaps exist for the stated purpose.