opendeck-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENDECK_EXE | No | Override the path to the OpenDeck executable. Default (Windows): %LOCALAPPDATA%\OpenDeck\opendeck.exe | |
| OPENDECK_LOG_DIR | No | Override the OpenDeck log folder. Default (Windows): %LOCALAPPDATA%\opendeck\logs | |
| OPENDECK_CONFIG_DIR | No | Override the OpenDeck config folder. Default (Windows): %APPDATA%\opendeck | |
| OPENDECK_MCP_DATA_DIR | No | Directory for the server's own plan, backups and cache. Default (Windows): %LOCALAPPDATA%\opendeck-mcp |
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 |
|---|---|
| get_overviewA | Start here. Lists devices (grid size, dials, touchpoints, connected), each device's profiles and which is selected, installed plugins, whether OpenDeck is running, and how many changes are staged. |
| show_profileA | Render a profile: a grid sketch plus every occupied slot with its action, title and state. Includes staged (not yet applied) changes, marked with *. Slot labels shown are the ones the editing tools accept. |
| list_actionsA | List actions that can be placed on keys or dials: name, plugin, uuid, controllers, states. Includes OpenDeck's Multi Action and Toggle Action, and plugins staged for install. |
| describe_actionA | Explain one action's settings before placing it: a curated schema for OpenDeck and Starter Pack actions, otherwise hints read from the plugin's settings page, plus real settings from the user's existing keys (secrets redacted). |
| get_plugin_settingsA | Show a plugin's global (plugin-wide) settings with secret values redacted. |
| read_logsA | Tail OpenDeck's log or a plugin's log (tokens redacted). Useful after apply_changes. |
| get_app_rulesA | Show automatic profile switching: which profile each device switches to when an app is focused. |
| set_keyA | Place an action on a key or dial, replacing whatever is there. For dials use dial with an action that supports Encoder. For a Multi/Toggle Action, set it here, then add_child. Staged only. |
| update_keyA | Change an existing key without replacing its action: title, title style, image, settings, or which state it shows. Title text, image and settings changes on the profile a connected device is showing apply instantly, with no restart (undo with undo_live). Anything else (title style, current state, another profile, a device with staged changes) is staged for apply_changes; the result says which happened. A live settings change reaches the plugin as if edited in OpenDeck's own panel; if that key's settings panel is open in OpenDeck, reopen it to see the change. |
| undo_liveA | Undo the latest instant (live) edits made by update_key, newest first: titles, images and settings go back to what they were. Staged changes and applied plans are undone with discard_changes and restore_backup instead. |
| make_folderA | Make a folder: a new profile opened by a key on this one, with a Back key inside. OpenDeck allows one folder level, so it's created as '<this profile's folder>/'. Staged only. |
| clear_keyB | Remove the action from a key or dial. Staged only. |
| move_keyA | Move, swap or copy a key (with its settings, title, image and children), within a profile or to another profile/device. Staged only. |
| add_childA | Add an action inside a Multi Action (runs all children in order) or Toggle Action (cycles through them, one per press). Put the Multi/Toggle Action on the key with set_key first. Staged only. |
| remove_childA | Remove one action from inside a Multi/Toggle Action. Staged only. |
| set_multi_delaysA | Set the pauses between the children of a Multi Action. Staged only. |
| manage_profileA | Create, duplicate, rename or delete a profile, or make one the device's selected profile. Renaming also updates app rules and Switch Profile keys that point at it. Staged only. |
| set_app_ruleB | Switch a device to a profile automatically when an app is focused. Staged only. |
| set_plugin_settingsA | Change a plugin's global (plugin-wide) settings, e.g. a server URL. Staged only. |
| set_device_layoutA | Tell opendeck-mcp a device's key grid size when it can't detect it (stored locally; doesn't touch OpenDeck). Usually unnecessary: the bridge plugin records it automatically. |
| preview_changesA | Show everything staged: per device/profile/slot changes, warnings (commands that will run, plugins that will be installed), and conflicts with edits made in OpenDeck since staging. |
| discard_changesA | Drop staged changes without applying them. |
| render_profileA | A picture of the deck as OpenDeck draws it: icons, titles, colours, dials, with staged changes outlined. Use it to check a layout before applying, or to show the user. |
| make_iconA | Make a key image: text, an emoji, a brand logo or a generic symbol on a coloured square.
Returns a preview and a file path to pass as |
| find_iconsB | Find icon names for make_icon. |
| ha_searchA | Find Home Assistant entities (id, name, state, area) to put on keys, using the Home Assistant plugin's saved login. With no filters, lists the areas and domains. |
| ha_describe_entityB | One Home Assistant entity: state, attributes, area, the services its domain offers, and ready-made settings for a Home Assistant key that controls it. |
| ha_call_serviceA | Call a Home Assistant service right now, e.g. to test what a key will do. Acts on the real home: call with confirm=false first and get the user's OK. |
| find_pluginsB | Search for plugins to install, with author, repository and installed/available versions. |
| stage_pluginA | Install, update or remove a plugin. Installing runs third-party code on the user's computer: call first with confirm=false, show the user what was found (author, version, checksum, AI-assisted flag), and only stage it with confirm=true after they agree. Removal clears the plugin's keys everywhere. |
| apply_changesA | The only tool that changes OpenDeck. Stops OpenDeck, backs up, writes all staged changes, verifies them and restarts OpenDeck. Call with confirm=false first and show the user the result. |
| list_backupsB | Backups taken by apply_changes and restore_backup, newest first. |
| restore_backupA | Undo an apply: put the files it changed back as they were (restarts OpenDeck). Call with confirm=false first to see what would be restored. |
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 33 tools
The staging lifecycle is exceptionally well delineated: set_key/clear_key/move_key/add_child/remove_child are staged-only, update_key is live, preview_changes/discard_changes/apply_changes/restore_backup/undo_live each cover a distinct stage, and descriptions explicitly tell the agent when to use which. The only mild overlap is among the three inspection tools (get_overview summary, show_profile text grid, render_profile image), but granularity differences keep them distinguishable.
Every tool follows a clean verb_noun snake_case pattern (get_overview, set_key, make_icon, apply_changes, list_actions), with a consistent ha_ prefix namespacing the Home Assistant tools. No camelCase, vague verbs, or divergent styles.
At 33 tools this is heavy and exceeds the comfortable band; the staging/key/plugin/icon/HA subgroups each add surface area. The domain (devices, profiles, key grids, plugins, staging, backups, HA) is genuinely complex so most tools earn their place, but the set is at the borderline of being unwieldy.
Coverage is strong: full key/dial placement and mutation, Multi/Toggle children, folders, profile CRUD and selection, app rules, plugin install/update/remove and settings, device layout, icons, HA entities/services, plus the whole stage-preview-apply-backup-restore-undo lifecycle and logging. Only minor gaps remain (e.g. no dedicated backup retention/pruning or finer key-state editing beyond what update_key exposes).