Skip to main content
Glama
kuhyx

i3wm-mcp

by kuhyx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to i3wm-mcp

No user-submitted related servers found.

    Related Servers

    • Sway MCP

      kefimoto
      F
      license
      Not graded
      quality
      C
      maintenance
      Exposes Sway window manager commands as native tools for Claude Code, enabling window management, workspace navigation, and display configuration through natural language.
      -

    • arch-niri-mcp

      oki3505F
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to inspect, control, and automate Arch Linux/CachyOS and the Niri Desktop Environment through natural language, featuring tools for window management, system administration, package queries, and hardware control.
      35
      MIT

    • tmux-mcp

      WENLIXIAO-CS
      A
      license
      A
      quality
      D
      maintenance
      Allows AI assistants to create, manage, and interact with tmux sessions, windows, and panes programmatically.
      19
      MIT

    • FVWM3 Window Manager

      elsanchez
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables interaction with the FVWM3 window manager for configuration generation, window management, and debugging. Provides access to config files, runtime state, and control tools for managing desktops, monitors, and tiling operations.
      -

    • hypr-mcp

      tuan-cre
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to automate Hyprland desktop environments through screenshots, mouse/keyboard input, window management, workspaces, clipboard, app launching, and OCR.
      27
      1
      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

    A4.7/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a distinct purpose: inspecting state (get_tree/list_workspaces/list_outputs/get_config), navigating/focusing (focus_window), moving (move_window/kill_window), workspace management (manage_workspace), layout changes (set_layout/toggle_window_state), and execution (exec_application/run_command). Overlap is minimal and well-documented.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case, e.g., get_tree, list_workspaces, focus_window, toggle_window_state. No mixing of conventions.

    Tool Count5/5

    With 12 tools, the scope is well-balanced for an i3/Sway MCP server. It covers essential operations without being bloated or sparse.

    Completeness4/5

    The tool set covers most common i3 actions including tree queries, focus, move, workspace management, layout changes, and execution. Minor gaps exist for operations like marks and scratchpad control, but these are accessible via run_command.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources