mcp-computer-use
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_COMPUTER_USE_HOST | No | Host interface for HTTP transport. Defaults to 0.0.0.0:8723. | 0.0.0.0 |
| MCP_COMPUTER_USE_PORT | No | Port for HTTP transport. Defaults to 8723. | 8723 |
| MCP_COMPUTER_USE_STATELESS | No | If set to 1, server runs in stateless HTTP mode. Each request is self-contained. | 1 |
| MCP_COMPUTER_USE_TOOL_NAME | No | Override the tool name. Must match [a-z][a-z0-9_]*. | computer_use |
| MCP_COMPUTER_USE_SESSION_KEY | No | Session key for identifying the client session. | |
| MCP_COMPUTER_USE_AUTO_APPROVE | No | Legacy shortcut for auto approval mode. Set to 1 to enable. | |
| MCP_COMPUTER_USE_ALLOWED_HOSTS | No | Comma-separated list of allowed Host headers for DNS-rebinding protection. Empty disables. | |
| MCP_COMPUTER_USE_APPROVAL_MODE | No | Approval mode: deny, auto, or callback. Controls destructive action approvals. | deny |
| MCP_COMPUTER_USE_ALLOWED_ORIGINS | No | Comma-separated list of allowed origins for CORS. Empty disables. |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| computer_useA | Drive the desktop via cua-driver — screenshots, mouse, keyboard, scroll, drag — on macOS, Windows, and Linux. Input is background-FIRST, not background-only: the default delivery routes to the target window without stealing the user's cursor or focus (works even on hidden/minimized windows), and when a result's |
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 1 tool
With only one tool there is no possibility of mistaking it for another tool. The tool internally distinguishes capture, click, type, scroll, and drag through its action parameter, so the surface is unambiguous.
The single tool name 'computer_use' is clear and descriptive, though it does not follow a verb_noun pattern. There is no inconsistent naming across the set because only one name exists.
One tool is borderline for such a broad domain, but it deliberately consolidates all computer-use actions behind a single action parameter. This keeps the count minimal, though splitting actions into separate tools could improve discoverability.
The tool covers the core GUI automation lifecycle: capture, click, type, scroll, drag, and verification via re-capture. Minor operations like explicit right-click or file upload are not named, but the overall workflow is practical and mostly complete.