MADRIX MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MADRIX_HOST | No | MADRIX instance IP | 127.0.0.1 |
| MADRIX_HTTP_PORT | No | MADRIX Remote HTTP port | 80 |
| MADRIX_READ_ONLY | No | Set to 1 for read-only mode | 0 |
| MADRIX_TRANSPORT | No | MCP transport (stdio, sse, streamable-http) | stdio |
| MADRIX_REMOTE_PATH | No | MADRIX Remote HTTP command path | /RemoteCommands/ |
| MADRIX_ALLOWED_HOSTS | No | Comma-separated allowlist for target hosts. Set * to allow any. | 127.0.0.1,localhost,::1 |
| MADRIX_SAFETY_PROFILE | No | Safety preset: lab, show-safe, or read-only | lab |
| MADRIX_TIMEOUT_SECONDS | No | HTTP timeout | 5.0 |
| MADRIX_CONFIRM_DESTRUCTIVE | No | Set to 1 to require confirm=true on destructive actions | 0 |
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
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 108 tools
Many tools have overlapping purposes (e.g., set_current_layer_filter vs set_layer_filter, multiple set storage tools) and lack clear distinctions, making it difficult for an agent to select the correct one.
Uses snake_case consistently, but verbs vary (get, set, toggle, trigger, add, delete) and some tools like 'select_layer' or 'health_check' break the verb_noun pattern, causing mild inconsistency.
With 108 tools, the surface is excessively large for a typical MCP server. While lighting control may require many operations, this count makes the server unwieldy and hard to navigate.
Covers many aspects like cuelists, groups, layers, audio, and storage, but lacks lifecycle operations such as creating or deleting groups, and some updates are missing, leaving notable gaps.