Skip to main content
Glama
aathishwar-13

antigravity-terminal-mcp

by aathishwar-13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to antigravity-terminal-mcp

No user-submitted related servers found.

    Related Servers

    • wsl-mcp

      cacaview
      A
      license
      Not graded
      quality
      D
      maintenance
      A MCP terminal management server with persistent sessions and terminal polling, optimized for Windows + WSL environments.
      6 npm
      2
      MIT

    • interminal

      QiuwenZheng
      A
      license
      A
      quality
      A
      maintenance
      MCP server for SSH and local terminal access. Supports interactive commands, long-running processes, and TUI apps like tmux/zellij
      6
      3
      MIT

    • relaybridge

      maximyz3d
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a local Windows control plane for PowerShell and AI CLIs, exposing MCP tools for safe terminal sessions, bounded provider calls, routing, committees, and run receipts.
      4 npm
      MIT

    • COP Plug

      beepoo304
      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.
      -

    • PowerShell MCP Server

      gunjanjp
      A
      license
      A
      quality
      F
      maintenance
      A comprehensive Model Context Protocol (MCP) server that enables Claude and other LLM applications to execute PowerShell commands, scripts, and perform system operations on Windows systems.
      10
      25
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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 issues

    Resources