NexusWindows for Antigravity
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEXUS_AGY_CONFIRM | No | Set to "off" in the MCP server environment to turn confirmation off entirely (default: on). When on, an action labelled pay, buy, order, transfer money, send, publish, delete permanently, uninstall, format, reset, cancel a subscription, erase data or make a repository public needs `confirm: true` on the step. | on |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| windowsC | List open windows: hwnd, title, process (the real application for UWP), position, foreground. by_app=true: grouped by application. Example: {"by_app": false} |
| lookA | GOLDEN RULE: look → act in one batch, targets by label; never resend a batch without looking. See a NAMED window (hwnd: number, title or process) WITHOUT bringing it to the front (covered ones too): one line per element "[N] role "name" = "value" states @x,y"; image (WebP ≤ 2000 px) only if the tree is too thin, or with capture_screenshot=true, annotate (numbers drawn) or zoom=box_2d (area enlarged); query filters; format="json": compact JSON (box_2d 0-1000 per element). Same screen as the last image sent: not attached again. Unlocks a batch. Example: {"hwnd": "Notepad", "query": "save"} |
| actA | Act in ONE batch, in the background, on a NAMED window (hwnd), without reading the code: shared token, emergency stop and the user's pause are handled here.
Actions: click, double_click, right_click, type, set, clear, check, uncheck, select (option), expand, collapse, menu (path), key, scroll, drag, hover, wait (seconds, text), focus.
Target: target="Exact label", "#N", box_2d or x/y; ambiguous label refused. Steps ✓ = ~ ✗, status = the worst; follow |
| launchA | Open an application (name such as "notepad.exe", or path), a folder or a document, like a double-click; the
opening is read back. Settings page: app="ms-settings:display" (opened behind the user's window, read back).
Refused: web addresses http, https, ftp (web pages: nexus-browser). args: arguments of a .exe program (a file to
open…), never for a document, a folder or an address; also accepted after the program in |
| windowA | Manage a NAMED window (hwnd: number, title or process). action="close": close it cleanly (UI Automation, then WM_CLOSE), the closing is read back; a "Save?" prompt, if any, is reported, never answered. Example: {"action": "close", "hwnd": 123456} |
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
The core split is clean: launch opens things, windows enumerates, look observes, act manipulates, window closes. The single real hazard is 'window' (close one window) versus 'windows' (list all windows) — near-identical names with different scopes that an agent could easily pick wrong, though the descriptions do state their roles explicitly.
All names are single lowercase tokens, so the surface style is uniform, but the convention is mixed: launch/look/act are verbs while window/windows are nouns, and 'window' vs 'windows' differ only by a plural. Readable, but not the predictable verb_noun or verb_resource pattern that scales well.
Five tools is lean but well-matched to a multiplexed design where look and act absorb most verbs via action/step parameters. The only slight waste is 'window', which carries a single close action and could arguably live inside act, leaving one tool under-loaded relative to the rest.
The lifecycle is covered end to end: launch an app, enumerate windows, observe a named window, act within it, and close it, with foreground fallback and confirmation guards for destructive actions. Gaps are minor — no minimize/maximize/resize/reposition, no process-level kill, and web URLs are explicitly deferred to a companion server.