Skip to main content
Glama
capecoma

WinTerm MCP

by capecoma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to WinTerm MCP

No user-submitted related servers found.

    Related Servers

    • Windows Command Line MCP

      alxspiker
      A
      license
      A
      quality
      F
      maintenance
      A secure Model Context Protocol server that allows AI models to safely interact with Windows command-line functionality, enabling controlled execution of system commands, project creation, and system information retrieval.
      8
      10
      MIT

    • iTerm MCP

      lite
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that gives AI models access to your iTerm terminal session, allowing them to read output, write commands, and send control characters.
      3
      195 npm
      MIT

    • iTerm MCP Server

      rishabkoul
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server that enables AI assistants to interact with iTerm2 terminals, allowing creation and management of terminal sessions, command execution, and reading terminal output.
      5
      16 npm
      14
      ISC

    • Windows CLI MCP Server

      simon-ami
      A
      license
      B
      quality
      F
      maintenance
      A Model Context Protocol server that provides secure command-line access to Windows systems, allowing MCP clients like Claude Desktop to safely execute commands in PowerShell, CMD, and Git Bash shells with configurable security controls.
      9
      809 npm
      269
      MIT

    • wsl-bridge-mcp

      Darling209
      F
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol server that lets Windows-side AI agents operate on WSL distributions like a local environment, providing file read/write/edit, command execution, process management, log streaming, and content search via UNC paths and persistent shells.
      28
      -
    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

    B3.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: reading output, sending control characters, and writing text/commands are three separate terminal operations. An agent can easily tell them apart based on their specific functions.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (read_terminal_output, send_control_character, write_to_terminal) with snake_case throughout. The naming is predictable and readable across the set.

    Tool Count4/5

    Three tools is slightly thin but reasonable for a terminal-focused server, covering core input/output and control operations. It feels minimal but not incomplete, as each tool earns its place for basic terminal interaction.

    Completeness4/5

    The tools cover the essential terminal operations: reading, writing, and control. A minor gap might be the lack of a tool for managing terminal sessions or configuration, but for basic interaction, the surface is largely complete without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources