F
licenseNot graded
qualityD
maintenanceAn MCP server that allows AI assistants like Claude to execute terminal commands on the user's computer and return the output, functioning like a terminal through AI.
89
-
MCP Terminal
by sichang824
Related Servers
Alternatives to MCP Terminal
No user-submitted related servers found.
Related Servers
- 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-
- FlicenseAqualityDmaintenanceA simple MCP server that exposes a terminal tool, allowing AI agents to execute shell commands.1-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that gives AI assistants the ability to create, manage, and control terminal sessions through a safe, isolated tmux environment.1-
- AlicenseBqualityFmaintenanceA server that uses the Model Context Protocol (MCP) to allow AI agents to safely execute shell commands on a host system.1158 npm9MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that allows LLMs to execute shell commands and receive their output in a controlled manner.7MIT
TDQS
C2.8/5.0
Scored across 3 tools
Disambiguation5/5
Each tool has a clearly distinct purpose with no overlap: execute_command runs terminal commands, file_modify writes to files, and get_terminal_info retrieves terminal metadata. An agent can easily differentiate between executing commands, modifying files, and gathering system information without confusion.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern (execute_command, file_modify, get_terminal_info), using snake_case throughout. The naming is predictable and readable, with no deviations in style or convention across the set.
Tool Count3/5
With only 3 tools, the set feels thin for a terminal server, lacking operations like reading files, navigating directories, or managing processes. While the tools are well-defined, the count is borderline low for the apparent scope of terminal interactions, potentially limiting agent workflows.
Completeness2/5
There are significant gaps in the tool surface for terminal operations. Missing are essential functions like reading files, listing directories, checking command history, or handling environment variables. This incomplete coverage will likely cause agent failures when attempting common terminal tasks beyond basic command execution and file writing.
Maintenance
ActivityInactive
ResponsivenessNo issues