jan-terminal-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_shellC | Run a PowerShell command on the user's machine. |
| gitA | Run a git command. args = e.g. 'status', 'log --oneline -10', 'commit -m "fix bug"' |
| read_fileC | Read the contents of a file on the user's machine. |
| write_fileB | Write or overwrite a file on the user's machine. After writing code, use run_file to execute it — do NOT also call run_code with the same code. |
| list_dirB | List files and folders in a directory. |
| edit_fileA | Edit a file by replacing old_text with new_text. Use this to fix errors instead of rewriting the whole file. |
| run_fileA | Run an already-existing file. Use this after write_file — avoids writing the code twice. Language is auto-detected from extension if not provided. |
| run_codeA | Execute a code snippet directly without saving to disk. Use for quick one-off runs. If you already wrote the code with write_file, use run_file instead to avoid writing twice. Supported: python, javascript, typescript, java, cpp, csharp, go, rust, ruby, php, r, kotlin, swift, matlab |
| run_pythonB | Execute Python code directly and return the output. |
| run_cppA | Compile and run C++ code. Returns compiler errors or program output. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.