beat-twin
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITWIG_HOST | No | The host of the Bitwig controller JSON-RPC bridge. | 127.0.0.1 |
| BITWIG_PORT | No | The port of the Bitwig controller JSON-RPC bridge. | 8888 |
| BITWIG_MCP_WRITE_POLICY | No | Comma-separated list of write classes to enable (e.g., 'transport,mixer_write'). | |
| BITWIG_MCP_ENABLE_WRITES | No | Set to '1' to enable every write class. |
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 |
|---|---|
| bitwig_session_inspectA | [policy:read] Read-only inspection of Bitwig transport, tracks, scenes, selected device, and remote controls |
| bitwig_arrangement_planB | [policy:read] Plan-only arrangement suggestion from the read-only Bitwig session snapshot |
| transport_get_tempoA | [policy:read] Get the current tempo (BPM) |
| transport_get_positionA | [policy:read] Get current playhead position in beats |
| transport_playing_statusA | [policy:read] Check if transport is currently playing |
| track_bank_get_statusA | [policy:read] Get status (vol/pan/mute/solo) of all 8 tracks in the current bank window |
| scene_listB | [policy:read] List available scenes in the current bank |
| clip_get_infoA | [policy:read] Get loop and playing-step info for the focused cursor clip |
| track_selected_get_statusA | [policy:read] Get status of the currently selected track |
| device_get_statusA | [policy:read] Get status of the currently selected device |
| device_get_remote_controlsA | [policy:read] Get the 8 remote control parameters for the current page |
| device_listB | [policy:read] List devices on a visible track |
| browser_get_statusB | [policy:read] Get the Bitwig popup browser status |
| browser_list_resultsA | [policy:read] List visible results in Bitwig's popup browser |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/LaurentHuzard/beat-twin'
If you have feedback or need assistance with the MCP directory API, please join our Discord server