Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
LCU_HOMENoWhere the installer puts the server. Defaults to ~/.linux-computer-use.~/.linux-computer-use
LCU_DATA_DIRNoWhere the lease file and the audit log are written. Defaults to ~/.linux-computer-use.~/.linux-computer-use
LCU_IRREVERSIBLENoReplaces the list of verbs treated as irreversible, comma separated.
LCU_PLAYWRIGHT_CLINoPath to an alternative playwright-cli, used instead of the bundled one.

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
openA

Open a browser session, or attach to a browser already running with a CDP endpoint. Call this first.

gotoC

Navigate the current tab to a URL.

snapshotA

Accessibility tree of the page with a ref for each element. Use these refs with click and fill. Prefer this over screenshot for acting: it is exact and cheap.

screenshotA

Image of the page. Use it to read visual content, verify a result, or work out coordinates for the mouse tool.

clickA

Click an element by its ref from snapshot. Blocked when the element looks irreversible unless confirm is true.

typeA

Type text into the focused element. Refused when a password field has focus.

fillB

Fill a field identified by its ref. Refused on credential fields.

pressB

Press a key, for example Enter, Tab or ArrowDown.

mouseA

Coordinate based mouse control for canvas, maps and custom widgets that have no accessible element. Take a screenshot first to read the coordinates.

tabsB

List, open, select or close tabs.

historyC

Go back, go forward or reload.

statusA

Report the session, the mode and who holds the control lease. Pass takeover: true to hand control to the human before they act in the dashboard. Control comes back only when the human releases it on their machine, never through this tool.

set_modeA

normal asks before sensitive actions. auto runs a complete objective end to end, stopping only for an empty login, an account choice, or an irreversible action.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 13 tools

Disambiguation4/5

Most tools have clearly distinct purposes: goto for navigation, snapshot for accessibility tree, screenshot for visual capture, click/type/fill/press for input. The overlaps between click and mouse (ref vs coordinates) and type vs fill (focused vs by ref) are clarified by descriptions, making misselection unlikely.

Naming Consistency3/5

Tool names are all lowercase and mostly single words, but they mix verb forms (goto, click, type, fill, press, open) with noun forms (snapshot, screenshot, mouse, tabs, history, status). The only underscore in set_mode breaks the otherwise uniform style, creating a minor inconsistency.

Tool Count5/5

13 tools is well within the ideal range for a browser automation server. Each tool covers a distinct aspect of interaction, from session management and navigation to reading state and performing actions, without feeling bloated or sparse.

Completeness4/5

The toolset covers the core lifecycle: open, navigate, inspect (snapshot/screenshot), interact (click/type/fill/press/mouse), manage tabs/history, and control session mode. Minor gaps like an explicit wait or scroll tool are workable because snapshot can serve as a synchronization point and mouse can handle scrolling.

Maintenance

ActivityStale
ResponsivenessNo issues