Moku 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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| discover_mokusB | Discover Moku devices on network via zeroconf |
| attach_mokuB | Connect to Moku device and assume ownership |
| release_mokuB | Disconnect from Moku and release ownership |
| push_configC | Deploy MokuConfig to connected device |
| get_configB | Retrieve current device configuration |
| set_routingD | Configure MCC signal routing |
| get_device_infoB | Query device metadata (name, serial, IP, etc.) |
| list_slotsB | List configured instrument slots |
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 8 tools
Each tool has a clearly distinct purpose with no overlap: discovery, connection, device info, configuration retrieval, slot listing, configuration deployment, disconnection, and routing setup. The descriptions make it easy to distinguish between tools like get_config (retrieve config) and push_config (deploy config), avoiding any ambiguity.
All tool names follow a consistent verb_noun pattern with snake_case, such as attach_moku, discover_mokus, get_config, and release_moku. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions.
With 8 tools, the server is well-scoped for managing Moku devices, covering essential operations like discovery, connection, configuration, and release. Each tool earns its place without feeling excessive or insufficient, aligning perfectly with the domain's needs.
The tool set provides complete lifecycle coverage for Moku device management, from discovery and attachment to configuration, monitoring, and release. There are no obvious gaps; all core operations are included, ensuring agents can handle typical workflows without dead ends.