LiveBrain 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 |
|---|---|
| healthA | Check LiveBrain MCP health. |
| live_set_snapshotA | Read the current Ableton Live Set. |
| generate_basslineC | Generate a deterministic style-aware bassline. |
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 3 tools
Each tool serves a clearly distinct function: health checks server status, live_set_snapshot reads the current Ableton Live set, and generate_bassline creates a bassline. There is no overlap or ambiguity between them.
Tool names follow mixed conventions: 'health' is a bare noun, 'live_set_snapshot' is a noun phrase, and 'generate_bassline' uses a verb_noun pattern. This inconsistency makes the naming pattern unpredictable.
With only 3 tools, the server feels slightly under-scoped but remains reasonable for a focused integration. Each tool contributes a distinct capability without redundancy.
The server covers the core workflow of reading the Live set and generating a bassline, with health as a utility. Minor gaps exist (e.g., no update/apply function), but the primary purpose is adequately served.