mcp-server-text-editor
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 |
|---|---|
| text_editorB | View, create, and edit files with persistent state across command calls. This tool is identical with Claude's built in text editor tool called text_editor_20241022 |
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 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool has a single, clear purpose for file editing with persistent state, making disambiguation trivial.
A single tool named 'text_editor' follows a clear and consistent naming pattern. There are no other tools to compare against, so no inconsistency can exist.
A single tool for a text editor server feels thin and under-scoped. While it covers basic file operations, typical text editors would benefit from additional tools for tasks like search/replace, formatting, or managing multiple files, making this count borderline inadequate.
The tool surface is severely incomplete for a text editor domain. It lacks essential operations such as search within files, undo/redo functionality, file management (e.g., rename, delete), or formatting options, which are core to text editing workflows.