draft-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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| review_draftA | Let the user review and edit a draft before it goes anywhere. When creating PR descriptions, Linear tickets, Slack messages, or emails: call this tool first, then use the approved content with the target tool. Opens a browser window with an editor and live preview. Blocks until the user approves or rejects. On approve: proceed with the next step (create PR, post ticket, etc.) or copy to clipboard. On reject: ask the user what they'd like to change. Examples:
|
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
Only one tool exists, so no risk of confusion between tools.
The single tool name 'review_draft' follows a clear verb_noun pattern, which is consistent within the set.
The server has exactly one tool, which is minimal but appropriate for a focused drafting/review utility. While the count is low, the purpose is narrow enough that it doesn't feel insufficient.
The server fully delivers on its stated purpose: providing a review step for drafts before sending to other tools. No additional tools are needed for this specific function.