jan-terminal-mcp
Related Servers
Alternatives to jan-terminal-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA self-hosted MCP server that gives AI coding assistants direct shell access to your local machine, enabling execution of arbitrary bash commands for development workflows.2,507 npmISC
- AlicenseAqualityDmaintenanceAn MCP server that enables AI clients to execute shell, Python, and Node commands on the local machine across platforms.31MIT
- AlicenseBqualityCmaintenanceA comprehensive MCP server for developers providing file operations, shell execution, git integration, and smart caching to enhance AI-assisted development.116 npmMIT
- AlicenseNot gradedqualityCmaintenanceA self-hosted MCP server that gives ChatGPT full local machine access for coding tasks, including file editing, shell commands, git operations, and project exploration via 40+ MCP tools.MIT
- AlicenseBqualityCmaintenanceAn MCP server that gives AI agents terminal execution, Python scripting, file management, and code search tools so they can carry out real development tasks. It exposes bash, Python, glob, grep, and file/folder operations over MCP for coding assistants and codebase exploration.91MIT
- AlicenseNot gradedqualityDmaintenanceLocal MCP server enabling Codex and ChatGPT to read/write files, execute commands, manage processes, use Git, and inspect images on the user's machine with full privileges.Apache 2.0
TDQS
Scored across 10 tools
The run_* family is heavily overlapping: run_code, run_python, and run_cpp all execute code, with run_python and run_cpp being subsets of run_code. run_file and run_shell also blur boundaries, making it easy to select the wrong tool.
Most tools follow a clear verb_noun pattern (read_file, write_file, list_dir, edit_file, run_code, etc.). The single exception is 'git' (a plain command name) and to a lesser extent 'run_shell' which still matches the pattern, so only a minor deviation.
10 tools is within the ideal range, but the redundancy of run_python and run_cpp with run_code makes the set feel slightly over-scoped. Still, the count is reasonable for a terminal/file server.
The tool surface covers git, shell, file read/write/edit/list, and code execution, which is solid for a terminal. Minor gaps include no delete_file or rename operation, but these can be worked around with run_shell.