antigravity-terminal-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ANTIGRAVITY_MONITOR_MODE | No | Configures the monitor mode: 'none' for no external monitor window, 'external' for a separate PowerShell window. | none |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_commandA | Execute a command in a reusable terminal session. Reuses session_id (or default) unless create_session=true. |
| command_statusA | Check status and get incremental output from a running command. |
| send_inputA | Send text input to the stdin of an active command. |
| list_sessionsA | List existing terminal sessions and whether they are running. |
| session_visual_infoA | Get live log path and watch command for a session so users can open output visually. |
| kill_commandB | Terminate a running command by command_id. |
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 6 tools
Each tool targets a distinct aspect of terminal session management: starting a command, checking its status, sending input, killing it, listing sessions, and retrieving visual log info. No two tools serve the same purpose.
Four tools (run_command, send_input, list_sessions, kill_command) follow a verb_noun pattern, but command_status and session_visual_info are noun-based, mixing conventions. The style is readable but not consistently patterned.
Six tools is a well-scoped set for a terminal management server, covering the core lifecycle without unnecessary bloat or gaps.
The command lifecycle (run, status, input, kill) and session listing are covered, but there is no way to list active commands within a session or explicitly delete a session, causing minor discoverability and cleanup gaps.