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. |
| openmausbot_api_healthA | Return local API health, app version, and compatibility findings. |
| openmausbot_list_botsA | List bots without long soul text unless explicitly requested. |
| openmausbot_list_routinesA | List routines and runs, optionally within a millisecond range. |
| openmausbot_list_webhooksA | List webhooks and attempts with secret material redacted. |
| openmausbot_usageA | Read usage for a date range of no more than one year. |
| openmausbot_list_modelsA | List provider instances and models without account details. |
| openmausbot_list_decisionsB | List recent decisions. |
| openmausbot_export_teamB | Export team data using a paired-device session token. |
| openmausbot_planA | Plan desired-state changes without sending any mutation. |
| openmausbot_update_botC | Plan or apply a guarded bot update. |
| openmausbot_set_bot_modelC | Plan or apply a validated model selection. |
| openmausbot_upsert_routineC | Plan or apply a name-idempotent routine upsert. |
| openmausbot_set_routine_enabledB | Plan or apply one routine's enabled state. |
| openmausbot_run_routine_nowC | Plan or start one routine immediately. |
| openmausbot_delete_routineC | Plan or delete one exactly confirmed routine. |
| openmausbot_cancel_runC | Plan or cancel one routine run. |
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 25 tools
Most tools target distinct resources and actions, with clear separation between listing, mutating, and CUA-driver operations. Minor confusion is possible between openmausbot_api_health and openmausbot_status, and between the generic openmausbot_plan and the per-resource 'plan or apply' mutation tools, but descriptions mostly mitigate this.
All tools share the openmausbot_ prefix, which helps, but verb patterns are mixed: list_bots vs get_companion_settings vs usage vs status, and cua_skills_status/cua_permissions_status/cua_check_update deviate from the list_/set_ convention. The naming is readable but not uniformly predictable.
At 25 tools, this sits at the heavy end of the acceptable range. The count is somewhat justified by covering bot management, routines, webhooks, usage, companion settings, and the CUA-driver surface, but it feels like several smaller logical servers have been merged into one.
Routine lifecycle is well covered with upsert, enable/disable, run, and delete, and companion settings have get/set. However, webhooks are list-only with no create/update/delete, bots lack create/delete, and the CUA-driver tools only inspect and invoke rather than manage the driver itself, leaving notable gaps.