openmausbot-cua-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENMAUSBOT_DATA_DIR | No | Override the OpenMausBot data directory | |
| OPENMAUSBOT_BUNDLE_ID | No | Override the OpenMausBot bundle identifier | |
| OPENMAUSBOT_CUA_DRIVER | No | Override the cua-driver executable | |
| OPENMAUSBOT_CUA_SOCKET | No | Override the live Unix socket | |
| OPENMAUSBOT_CUA_CONNECTION_FILE | No | Override cua-connection.json | |
| OPENMAUSBOT_CUA_MAX_OUTPUT_CHARS | No | Bound stdout and stderr returned to the client | |
| OPENMAUSBOT_COMPANION_SETTINGS_FILE | No | Override companion settings JSON |
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 |
|---|---|
| openmausbot_statusA | Check discovery and the live cua-driver daemon without changing state. |
| openmausbot_list_cua_toolsA | List every tool exposed by the cua-driver bundled with OpenMausBot. |
| openmausbot_describe_cua_toolA | Return the description and JSON input schema for one cua-driver tool. |
| openmausbot_call_cua_toolA | Invoke one cua-driver tool; some tools can control apps or modify local state. The connected OpenMausBot daemon applies its own permission mode. Call openmausbot_describe_cua_tool first when the input schema is not known. |
| openmausbot_get_companion_settingsA | Read OpenMausBot's companion settings JSON file. |
| openmausbot_set_companion_settingA | Atomically update one existing key in OpenMausBot's companion settings. |
| openmausbot_cua_skills_statusA | Report cua-driver skill pack installation status for supported agents. |
| openmausbot_cua_permissions_statusA | Report Accessibility and Screen Recording permission status. |
| openmausbot_cua_check_updateA | Check the configured cua-driver release channel without installing anything. |
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 9 tools
Most tools are clearly distinct, especially the list/describe/call cua-driver trio and the get/set companion settings pair. However, the three status-style tools (openmausbot_status, openmausbot_cua_skills_status, openmausbot_cua_permissions_status) are similar enough that an agent could initially struggle to pick the right one without reading descriptions carefully.
The openmausbot_ prefix and generally verb_noun structure make the set predictable. Minor inconsistencies exist: some tools use bare noun-style names like openmausbot_status, and set_companion_setting uses singular while get_companion_settings uses plural.
Nine tools is well-scoped for this server's purpose: environment/status checks, companion settings access, and discovery/invocation of cua-driver tools. Each tool has a distinct role and none feel redundant.
Core workflows are covered: checking daemon health, permissions, skills, release channel, reading/updating settings, and listing/describing/calling cua tools. The surface is slightly check-only around updates and skills—there is no install/update/enable action—but that appears intentional and is not a fatal gap.