MCP Terminal & Git Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_commandC | Execute a terminal command in a specified directory |
| git_cloneC | Clone a git repository to a specified location |
| install_react_projectB | Create a new React project using Vite and open it in VSCode |
| install_vue_projectA | Create a new Vue project using Vite and open it in VSCode |
| install_next_projectB | Create a new Next.js project and open it in VSCode |
| open_in_vscodeC | Open a directory or file in VSCode |
| check_directoryC | Check if a directory exists and list its contents |
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 7 tools
Most tools have distinct purposes: check_directory for inspection, execute_command for general terminal operations, git_clone for repository cloning, and three project installation tools for different frameworks. However, the three install_*_project tools could potentially be confused as they follow similar patterns but target different frameworks, creating minor ambiguity in selection.
The naming shows mixed conventions: check_directory, execute_command, and git_clone follow a verb_noun pattern, while install_next_project, install_react_project, and install_vue_project use a verb_framework_project structure. open_in_vscode uses a prepositional phrase. This inconsistency makes the set less predictable, though still readable.
With 7 tools, the count is reasonable for a combined terminal and Git server. It covers core operations like directory checking, command execution, Git cloning, project setup, and IDE opening. The scope is slightly broad but manageable, with no obvious bloat or thinness.
The server covers basic terminal and Git operations, but there are notable gaps. For terminal operations, it lacks file manipulation (create, delete, edit) and navigation tools. For Git, it only includes cloning, missing commit, push, pull, and status operations. The project installation tools are framework-specific but don't cover other common setups.