thinkspace-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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_to_inboxA | Send a note to the ThinkSpace app inbox on this Mac. Use when the user asks to send something to their inbox/ThinkSpace (e.g. 「受信箱に送って」, "send this to ThinkSpace"). Set |
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 confusing it with another. Its purpose (sending a note to the ThinkSpace inbox) is stated unambiguously.
The single name `send_to_inbox` follows a clear verb_destination snake_case pattern. With only one tool there are no inconsistencies to evaluate, and the name is self-descriptive.
A one-tool server is borderline thin, though it may reflect a deliberately narrow scoped integration (one-way note delivery). Whether this is appropriate depends on whether the server is intended as a minimal one-way bridge or a fuller ThinkSpace client.
The surface covers only an outbound send operation: no way to list, read, update, or delete inbox notes. If the domain is strictly one-way note delivery this is complete, but agents cannot verify delivery or manage notes afterward, leaving notable gaps.