Skip to main content
Glama
antigravity-terminal-mcp

antigravity-terminal-mcp

Antigravity Terminal MCP

Windows-focused MCP server for terminal automation with persistent sessions and live session logs. Created by AATHI.

Features

  • Persistent PowerShell sessions (session_id, default: default)

  • Incremental stdout/stderr polling

  • Send follow-up input into running sessions

  • Live log file path returned for each session

  • Configurable monitor mode via ANTIGRAVITY_MONITOR_MODE

  • VS Code integrated terminal metadata returned for each session

  • MCP standard methods (tools/list, tools/call) with legacy aliases

Related MCP server: PowerShell EX

MCP Tools

  1. run_command

  2. command_status

  3. send_input

  4. list_sessions

  5. session_visual_info

  6. kill_command

Publish-Ready One-Command Usage (From GitHub)

After pushing this project to your GitHub, users can seamlessly install and attach it to Claude using uvx (or the more robust python -m uv variant for Windows):

# Standard uvx (if in PATH)
claude mcp add antigravity-terminal-mcp uvx --from git+https://github.com/aathishwar-13/antigravity-terminal-mcp.git antigravity-terminal-mcp

# More robust Windows version (if uvx is not in PATH)
claude mcp add antigravity-terminal-mcp python -m uv tool run --from git+https://github.com/aathishwar-13/antigravity-terminal-mcp.git antigravity-terminal-mcp

(Note: If the code is nested in a subdirectory, simply append #subdirectory=folder_name to the git URL).

Local Run

uvx --from . antigravity-terminal-mcp

or

python server.py

Monitor Modes

By default, the server does not open an external monitor window (ANTIGRAVITY_MONITOR_MODE=none). This keeps monitoring in VS Code when you use the integrated terminal bridge.

If you explicitly want a separate PowerShell window for each session monitor, enable external mode:

$env:ANTIGRAVITY_MONITOR_MODE = "external"
python server.py

To force no external monitor window:

$env:ANTIGRAVITY_MONITOR_MODE = "none"
python server.py

When run_command or session_visual_info is called, the response now includes:

  • log_path

  • watch_command

  • monitor_mode

  • vscode_terminal

  • monitor_open (quick-open metadata for clickable/open actions)

monitor_open includes:

  • command_uri (VS Code command URI for antigravityTerminal.openMonitor)

  • markdown_link (prebuilt markdown clickable link for chat UIs)

  • integrated_terminal_command (copy/paste command to open live monitor in integrated terminal)

  • open_terminal_uri (opens a VS Code integrated terminal)

  • open_terminal_with_cwd_uri (opens integrated terminal in session cwd)

  • run_in_active_terminal_uri (runs monitor command in active integrated terminal)

The vscode_terminal object is designed for a VS Code extension to open the same session monitor inside an integrated terminal.

VS Code Integrated Terminal Bridge

A lightweight extension scaffold lives in vscode-integration/.

What it does

  • Opens an integrated PowerShell terminal in the current VS Code window

  • Runs the returned watch_command / vscode_terminal.command

  • Lets you paste either the full session_visual_info JSON or just the log_path

  • Shows a status-bar button: MCP Monitor (bottom-right) to pick and open any existing session monitor

  • Auto-detects session_logs/*.log create/change activity and shows an Open Monitor popup action

How to try it locally

  1. Open antigravity_mcp/vscode-integration in VS Code.

  2. Press F5 to launch the extension host.

  3. Run Antigravity: Open Monitor From Session Info JSON from the Command Palette.

  4. Paste the JSON returned by session_visual_info or run_command.

Where to click

  • Bottom-right VS Code status bar: click MCP Monitor and choose a session

  • On new session creation: click Open Monitor in the popup notification

This uses the VS Code extension API, which is the correct way to open an integrated terminal in the current editor window. A plain Python process cannot directly create a terminal tab inside VS Code by itself.

Quick Integrated Monitor Command (No Copy/Paste)

Use the helper script from a VS Code integrated terminal:

Set-Location d:\Projects\Client_projects\Velyx_Chatbot\antigravity_mcp
.\open-monitor.ps1 -SessionId live-agent

Optional short alias for the current terminal session:

Set-Alias agmwatch .\open-monitor.ps1
agmwatch -SessionId live-agent

This keeps monitoring inside VS Code and does not open an external terminal window.

Example MCP Config

{
  "mcpServers": {
    "antigravity-terminal-mcp": {
      "command": "python",
      "args": [
        "-m",
        "uv",
        "tool",
        "run",
        "--from",
        "git+https://github.com/aathishwar-13/antigravity-terminal-mcp.git",
        "antigravity-terminal-mcp"
      ]
    }
  }
}

Or


{
  "mcpServers": {
    "antigravity-terminal-mcp": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/AATHI/antigravity-terminal-mcp.git",
        "antigravity-terminal-mcp"
      ]
    }
  }
}

👨‍💻 About the Author

AATHI is a developer focused on building high-performance, developer-centric automation tools for the next generation of AI agents. With a specialization in bridging the gap between headless LLM execution and rich user-facing terminal interactions, AATHI created this tool to provide a portable, professional terminal experience beyond the standard VS Code integration limits.

Feel free to reach out for feedback or technical support via this repository!

Available Tools

6 tools
command_statusA

Check status and get incremental output from a running command.

Inputs: command_id (required).

kill_commandB

Terminate a running command by command_id.

Inputs: command_id (required).

list_sessionsA

List existing terminal sessions and whether they are running.

Inputs: no named parameters.

run_commandA

Execute a command in a reusable terminal session. Reuses session_id (or default) unless create_session=true.

Inputs: command (required), cwd, session_id, terminal_name, +1 more.

send_inputA

Send text input to the stdin of an active command.

Inputs: text (required), command_id (required).

session_visual_infoA

Get live log path and watch command for a session so users can open output visually.

Inputs: session_id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    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.

    Naming Consistency3/5

    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.

    Tool Count5/5

    Six tools is a well-scoped set for a terminal management server, covering the core lifecycle without unnecessary bloat or gaps.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      maintenance
      MCP server for SSH and local terminal access. Supports interactive commands, long-running processes, and TUI apps like tmux/zellij
      6
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A MCP terminal management server with persistent sessions and terminal polling, optimized for Windows + WSL environments.
      17 npm
      3
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to execute PowerShell commands, manage files, inspect projects, run Git operations, and monitor system information on Windows through a local MCP server.
      -