Skip to main content
Glama
Hor1zonZzz

Terminal MCP

by Hor1zonZzz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Terminal MCP

No user-submitted related servers found.

    Related Servers

    • BashTerm

      sirlordt
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables executing commands in visible VSCode terminal tabs with full output capture, supporting long-running processes, interactive input, and isolated sessions for parallel agents.
      45 npm
      2
      MIT

    • Node Terminal MCP

      hazzel-cn
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with terminal environments through multiple concurrent PTY sessions. Supports cross-platform terminal operations including command execution, session management, and real-time communication.
      4 npm
      3
      MIT

    • MCP Terminal Server

      alejoair
      A
      license
      Not graded
      quality
      F
      maintenance
      Provides cross-platform terminal access through MCP, enabling AI assistants to create and manage interactive terminal sessions, execute commands, and capture visual snapshots on Windows, Linux, and macOS.
      1
      MIT

    • Terminal MCP Server

      jonrad
      F
      license
      Not graded
      quality
      F
      maintenance
      Enables interactive terminal sessions within Claude Code and Desktop, allowing users and AI to execute commands and manage multiple tabs.
      2
      -

    • vscode-mcp

      prog76
      F
      license
      Not graded
      quality
      B
      maintenance
      Exposes VS Code terminals as MCP tools, allowing AI agents to create, execute commands, read output, list, and kill terminals across multiple workspaces.
      -
    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

    A4.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no ambiguity. terminal_create_or_get creates/retrieves sessions, terminal_send_input sends commands, terminal_get_output retrieves output, terminal_list shows active sessions, and terminal_close terminates sessions. The boundaries between these operations are well-defined and non-overlapping.

    Naming Consistency5/5

    All tools follow a perfect verb_noun pattern with 'terminal_' prefix and snake_case throughout. The naming is highly predictable: terminal_create_or_get, terminal_send_input, terminal_get_output, terminal_list, terminal_close. This consistency makes the tool set immediately understandable.

    Tool Count5/5

    Five tools is ideal for this terminal management domain. The set covers the complete lifecycle: create/retrieve, send input, get output, list sessions, and close sessions. Each tool earns its place with no redundancy, and the count is neither too sparse nor overwhelming for the scope.

    Completeness5/5

    The tool surface provides complete CRUD/lifecycle coverage for terminal management. It supports creating/retrieving terminals, sending commands, getting output, listing active sessions, and closing sessions. There are no obvious gaps or dead ends for agents working with terminal operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources