Skip to main content
Glama
kastro5

opendeck-mcp

by kastro5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to opendeck-mcp

No user-submitted related servers found.

    Related Servers

    • Deckhand MCP Server

      ProfetGit
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-capable AI agents such as Claude, Codex, Gemini CLI, Cursor and Zed to design and manage a Stream Deck by reading layouts, building pages and keys, setting icons and wallpapers, managing profiles and taking screenshots to verify their own work. Access is governed by read-only, edit-layout and full-control levels, with approval prompts before any tool runs something on the user's computer.
      MIT

    • n8n-mcp-guard

      FarazHayder
      A
      license
      A
      quality
      B
      maintenance
      Lets AI agents read, create, and update n8n workflows with a guarded two-phase plan-and-apply flow that backs up every change, refuses writes when the live workflow has moved, and verifies results by readback. Also supports rehearsing changes on trigger- and outbound-disabled test clones, so mutations to a live instance stay reviewable and reversible.
      5
      14 npm
      6
      MIT

    • n3 MCP server

      MelvinTo
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to directly control a Mirabox Stream Dock N3 via tools for key/screen updates, brightness, power, event listening, and layout management.
      MIT

    • mijia-fast

      X1039538408
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to inspect devices and automation rules, preview and apply changes, create backups, compare snapshots, and restore rules on a local MiJia gateway, with writes requiring confirmation.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 33 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count3/5

    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.

    Completeness4/5

    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).

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources