stackchan-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAC_IP | Yes | IP address of the host machine running the MCP server | |
| STACKCHAN_IP | Yes | IP address of the Stack-chan robot on the local network | |
| FISH_AUDIO_KEY | No | Fish Audio API key for TTS (optional; falls back to edge-tts if not set) |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| stackchan_sayD | – |
| stackchan_listenD | – |
| stackchan_moveD | – |
| stackchan_nodD | – |
| stackchan_shakeD | – |
| stackchan_faceD | – |
| stackchan_seeD | – |
| stackchan_homeD | – |
| stackchan_statusD | – |
| stackchan_healthA | Non-destructive health check for config, dependencies, and device status. |
| stackchan_config_summaryA | Return Stack-chan runtime config without secrets. |
| stackchan_playback_statusD | – |
| stackchan_voice_inboxD | – |
| stackchan_voice_inbox_clearD | – |
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 14 tools
Most tools have no descriptions, making it impossible for an agent to distinguish between them. Tools like 'stackchan_listen', 'stackchan_say', 'stackchan_see', and 'stackchan_move' likely have distinct functions, but without descriptions they are ambiguous.
All tool names follow a consistent 'stackchan_' prefix followed by a clear noun or verb, such as 'stackchan_config_summary', 'stackchan_move', 'stackchan_say'. This pattern is predictable and easy to parse.
14 tools is reasonable for a robotics/personal assistant server covering configuration, movement, voice, and status. It is slightly above the ideal range (3-15) but still well-scoped.
Based on tool names, the server appears to cover core robot interactions (speech, movement, health, voice inbox). However, missing descriptions and evident gaps like 'stackchan_home' (unclear purpose) hinder full assessment. Coverage seems acceptable but not exhaustive.