Skip to main content
Glama
Antigravity Desktop MCP

Antigravity Desktop MCP

by silas-ouyang

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
AGY_DESKTOP_UI_ENGINENoUI engine for desktop automation (e.g., 'com').

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
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
desktop_screenshotA

Capture the Windows screen, a specific display, a specific window (even overlapped via PrintWindow), a screen/window region, or a foreground-plus-related-windows bundle. Returns the image directly plus physical-pixel coordinate metadata and a frame_id for accurate click/drag/scroll projection.

desktop_actionsB

Execute a sequence of up to 50 desktop actions (click, move, drag, scroll, type, paste, key, clipboard, focus, launch, wait, wait_for, screenshot, state, or UI Automation actions like invoke/set_value/get_text) in a single round trip. Aborts immediately at <1ms latency if user E-Stop triggers.

desktop_clickB

Move to (x, y) and click. Prefer passing from_frame from desktop_screenshot so occlusion/window movement is guarded automatically.

desktop_moveB

Move the mouse cursor to absolute/frame-projected (x, y) or by relative delta (dx, dy) for hover tooltips or pointer-locked canvases.

desktop_dragB

Press left button and drag smoothly from (from_x, from_y) to (to_x, to_y), along a multi-point path, or continuing from previous drag (from_last / continue_from).

desktop_scrollC

Scroll vertically or horizontally at (x, y) or current cursor position.

desktop_typeB

Type Unicode text cleanly using SendInput KEYEVENTF_UNICODE into the active foreground window (use into_hwnd to guard against focus stealing).

desktop_keyB

Press or hold a key or key chord (e.g. "enter", "ctrl+s", "alt+f4", "ctrl+shift+p"). Blocked OS-escape chords are rejected under whitelist mode.

desktop_windowsB

Enumerate visible Windows application windows (and optionally minimized ones with include_minimized), or bring a window to foreground via focus_hwnd.

desktop_uiB

Inspect a window's UI Automation accessibility tree (with compact [s#.#] control refs for desktop_ui_action, snapshot delta diffing, pattern filtering, and optional focused/selected/document text observation).

desktop_ui_actionC

Perform a UI Automation action on a control identified by ref (from desktop_ui) or by selector (hwnd, automation_id, name, control_type, class_name, index).

desktop_clipboardA

Read (get), write (set), or clear the Windows text clipboard.

desktop_pasteB

Paste long or multi-line Unicode text reliably via clipboard + Ctrl+V, automatically saving & restoring previous clipboard contents (use require_restore: true to refuse if clipboard contains non-text data).

desktop_launchC

Launch a Windows application, executable path, Start Menu display name, URL, or Store app with Electron/Node-injection env vars stripped cleanly, and wait for its window.

desktop_stopA

URGENT: Immediately abort all running and queued desktop actions, kill hung workers if needed, confirm held keys/mouse buttons are released, and optionally latch the E-Stop.

desktop_safetyA

Inspect physical E-Stop overlay state, hotkey config (Esc mode + combo), window whitelist rules, and backend health, OR lock/tighten the window whitelist (lock_whitelist / tighten_whitelist). AI cannot clear an E-Stop or disable/widen an active whitelist.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 16 tools

Disambiguation4/5

Most tools have clearly distinct purposes: pointer movement, clicking, dragging, typing, window inspection, UI Automation, clipboard, launch, and safety are separable. The main overlap is desktop_actions, which can batch many of the same operations, and desktop_type versus desktop_paste, though their descriptions clarify the intended distinction.

Naming Consistency5/5

All tool names use a consistent snake_case convention with the shared desktop_ prefix. The verb/noun structure is predictable throughout, e.g. desktop_move, desktop_click, desktop_screenshot, desktop_ui_action.

Tool Count4/5

The 16 tools are justified by a broad desktop-automation domain covering input, screenshots, windows, UI Automation, clipboard, launch, and safety. The surface is slightly heavy relative to the ideal 3-15 range, but each tool maps to a meaningful capability rather than redundant variants.

Completeness4/5

Coverage is strong for the core desktop automation lifecycle: inspect, move, click, drag, scroll, type, key, clipboard, UI Automation, launch, stop, and safety. Minor gaps remain around direct right-click/double-click gestures and explicit window management operations like resize, move, minimize, or close, though some may be achievable through UI Automation or batch actions.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues