mindreset-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MINDRESET_DEVICE_ID | Yes | Device serial number from MindReset App | |
| MINDRESET_DEVICE_SECRET | Yes | Device secret from MindReset App |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mindreset_simple_textC | Send simple text content to MindReset device screen |
| mindreset_complex_textB | Send complex text content with signature to MindReset device screen |
| mindreset_text_with_iconC | Send text content with icon and optional link to MindReset device screen |
| mindreset_imageC | Display PNG image on a MindReset device screen |
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 4 tools
Three of the four tools send text to the device screen, with overlapping purposes (simple text, complex text with signature, text with icon/link). The descriptions hint at differences, but an agent could easily struggle to choose the right one without more explicit guidance.
All names use the mindreset_ prefix and snake_case, which is consistent. However, the suffix patterns vary (simple_text, complex_text, text_with_icon, image) rather than following a strict verb_noun convention.
Four tools is a well-scoped set for a device display integration, covering both text and image output. Each tool appears to serve a distinct display variant, so none feels redundant at the count level.
The surface covers the core operations of sending text and images to the device, which is likely the main use case. Minor gaps exist, such as clearing the screen or querying device status, but these are workaroundable by sending new content.