Skip to main content
Glama
nexon33

Electron Terminal MCP Server

by nexon33
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Electron Terminal MCP Server

  • MCP Terminal

    sichang824
    A
    license
    C
    quality
    C
    maintenance
    A server that enables AI assistants to execute terminal commands and retrieve outputs via the Model Context Protocol (MCP).
    3
    27
    MIT

Related Servers

  • PTY MCP Server

    almahdi
    A
    license
    A
    quality
    D
    maintenance
    A TypeScript-based server that enables programmatic management of pseudo-terminal sessions. It allows users to spawn, control, and interact with terminal processes in real-time through the Model Context Protocol.
    5
    4 npm
    AGPL 3.0

  • WinTerm MCP

    capecoma
    A
    license
    B
    quality
    D
    maintenance
    A Model Context Protocol server that provides programmatic access to the Windows terminal, enabling AI models to interact with the Windows command line through standardized tools for writing commands, reading output, and sending control signals.
    3
    5 npm
    MIT

  • stela-mcp

    Sachin-Bhat
    A
    license
    A
    quality
    D
    maintenance
    A Model Context Protocol server for secure local system operations, enabling shell command execution and file management via a standardized interface.
    14
    1
    Apache 2.0

  • Shell Server

    sergio-deras
    F
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server that enables users to execute arbitrary shell commands through a terminal tool. It supports custom working directories, configurable execution timeouts, and safe command parsing using shlex.
    -
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

C2.2/5.0

Scored across 5 tools

Disambiguation5/5

Each tool name maps to a distinct lifecycle action: start, execute, get output, stop, and list sessions. Even without descriptions, the boundaries are clear and unlikely to cause misselection.

Naming Consistency5/5

All tool names follow the same terminal_verb pattern using snake_case. The convention is uniform and predictable across the entire set.

Tool Count5/5

Five tools is a well-scoped size for a terminal management server. Each tool covers a necessary operation without redundancy or bloat.

Completeness5/5

The set covers the full terminal session lifecycle: create, interact, read output, stop, and enumerate sessions. There are no obvious dead ends or missing core operations.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources