Moom MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| activate_layoutC | Activate a specific Moom layout by name |
| save_current_layoutB | Save the current window arrangement as a new Moom layout |
| trigger_moom_actionC | Trigger common Moom actions via keyboard shortcuts |
| show_moom_menuC | Show the Moom popup menu |
| create_quad_layoutB | Create a quad (2x2) window layout on a specific display |
| create_custom_grid_layoutC | Create a custom grid layout (e.g., 3x2, 4x3) for high-res displays |
| list_layoutsB | List all saved Moom layouts |
| launch_applicationC | Launch a specified application for workflow setup |
| get_monitorsB | Get monitor configuration data for layout adaptation |
| set_window_positionC | Move a window to a specific position for precise control |
| set_window_sizeC | Resize a window to specific dimensions |
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 11 tools
Most tools have distinct purposes, but there is some potential overlap between 'activate_layout' and 'trigger_moom_action' (which could include layout activation), and 'create_custom_grid_layout' and 'create_quad_layout' are both layout creation tools with different grid types. Descriptions help clarify, but an agent might occasionally misselect between these similar functions.
Tool names follow a consistent verb_noun pattern throughout, such as 'activate_layout', 'create_custom_grid_layout', 'get_monitors', and 'list_layouts'. All tools use snake_case with clear, descriptive verbs, making the set predictable and easy to navigate.
With 11 tools, the count is well-scoped for a Moom window management server, covering layout activation, creation, monitoring, window control, and application launching. Each tool appears to serve a specific, useful function without unnecessary redundancy or bloat.
The toolset provides comprehensive coverage for window layout management, including CRUD-like operations (list, create, save, activate layouts), window positioning, and monitor configuration. A minor gap is the lack of a tool to delete or modify existing layouts, which could limit full lifecycle management, but core workflows are well-supported.