mcp-terminal-share
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TERMINAL_SHARE_DIR | No | Override the storage root directory (default: ~/.claude/terminal-messages) | |
| MCP_TERMINAL_SHARE_LABEL_PREFIX | No | Override the emoji/prefix for the statusline label (default: 📟) |
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 |
|---|---|
| registerA | Register this terminal with a name (e.g. A1, A2). Other terminals can then send messages to this name. |
| list_terminalsB | List all registered terminals. |
| send_messageB | Send a message to another terminal. The target terminal can read it with get_messages. |
| get_messagesA | Read messages sent to this terminal. Returns all messages and optionally deletes them after reading. |
| watch_messagesA | Block and wait for a message to arrive for this terminal. Returns as soon as a message is received or timeout is reached. |
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 5 tools
Each tool has a clear, non-overlapping purpose: registration, sending, listing, and two distinct reading methods (polling and blocking). No ambiguity.
All tool names follow a consistent verb_noun pattern (get_messages, list_terminals, register, send_message, watch_messages), making them predictable.
With 5 tools covering the core operations of a terminal messaging service, the count is well-scoped and each tool earns its place.
The tool surface covers registration, sending, and two receive modes. A minor gap is the lack of an explicit unregister or delete functionality, but the core workflow is complete.