MCP Terminal Tool Server
Related Servers
Alternatives to MCP Terminal Tool Server
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityNot gradedmaintenanceA simple MCP server that provides a terminal tool for executing shell commands with safety features like timeouts and error handling.-
- FlicenseAqualityDmaintenanceA lightweight MCP server that provides AI assistants with access to a system's terminal through a secure terminal tool. It enables users to execute shell commands and receive stdout, stderr, and exit codes directly within an MCP-compatible client.1-
- FlicenseAqualityCmaintenanceA simple MCP server that exposes a terminal tool, allowing AI agents to execute shell commands.1-
- FlicenseNot gradedqualityDmaintenanceA simple MCP server that allows running terminal commands with output capture, enabling command execution on the host system from MCP-compatible clients like Claude Desktop.1-
- AlicenseAqualityBmaintenanceAn MCP server that enables AI clients to execute shell, Python, and Node commands on the local machine across platforms.31MIT
- AlicenseCqualityCmaintenanceA server that enables AI assistants to execute terminal commands and retrieve outputs via the Model Context Protocol (MCP).327MIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool has a single, clear purpose: running terminal commands and returning output.
The single tool name 'terminal_tool' follows a consistent noun_noun pattern, though with only one tool, consistency is inherently perfect. There are no deviations or mixed conventions to evaluate.
A single tool for a terminal server is too few for the apparent scope, as it lacks coverage for common terminal operations like listing files, navigating directories, or managing processes. This minimal set will likely cause agent failures due to missing functionality.
The tool surface is severely incomplete for a terminal server. While 'terminal_tool' can run arbitrary commands, there are significant gaps: no dedicated tools for basic operations (e.g., ls, cd, pwd, ps) or structured outputs, forcing agents to rely on raw command parsing and increasing error risk.