TextEdit-MCP
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_rtf_documentC | Create a formatted RTF document with TextEdit compatibility |
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
There is only one tool, so there is no possibility of confusion with another tool. Its purpose is clear from the name and description.
The single tool follows a clear verb_noun naming pattern: create_rtf_document. With only one tool, there are no inconsistencies to assess.
A single tool is very thin for a server named TextEdit-MCP, which implies broader document interaction. The tool earns its place, but the overall surface feels under-scoped.
The server only supports creating an RTF document, with no read, open, edit, append, or convert operations. This leaves significant gaps for typical TextEdit-related workflows.