lean-computer-use-mcp
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
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 |
|---|---|
| cu_find_appA | List running apps with visible windows; optional name filter. |
| cu_observeA | Compact state read for one app; returns top-K controls and a state_id. |
| cu_actB | Execute one bounded action against a state_id; stale states are rejected. |
| cu_batchA | Run a bounded, fail-fast action sequence against one app. |
| cu_metricsA | Return aggregate cost and error metrics for this process. |
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 5 tools
Each tool has a distinct role: finding apps, observing state, executing single actions, batch actions, and metrics. No functional overlap between tools, and the descriptions clearly differentiate them.
All tools share the 'cu_' prefix and are short, but the second part mixes verbs (find, observe, act, batch) with a noun (metrics). This is a minor deviation from a consistent verb-focused pattern.
With only 5 tools, the server is lean and well-scoped. Each tool handles a core capability (discover, observe, act, batch, monitor), and the count feels right for the stated purpose.
The tools cover the essential lifecycle for computer use: finding an app, observing its state, performing actions (single or batched), and tracking metrics. There are no obvious dead ends or missing core operations.