MCP Git Terminal Server MCP Server

MCP server for git and terminal access. The mcp git terminal server mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 7 defined tools rather than through you.

What it actually does

1. Clone the repository (if you haven't already): bash git clone https://github.com/AbdurRaahimm/mcp-git-terminal-server.git mcp-terminal cd mcp-terminal 2. Install dependencies: bash npm install

• execute_command — Execute a terminal command in a specified directory
• git_clone — Clone a git repository to a specified location
• install_react_project — Create a new React project using Vite
• install_vue_project — Create a new Vue project using Vite
• install_next_project — Create a new Next.js project
• open_in_vscode — Open a directory or file in VSCode

Its toolset

Everything the assistant can do here goes through one of these:

• execute_command — The execute_command tool exposed by this server
• git_clone — The git_clone tool exposed by this server
• install_react_project — Create a new React project using Vite and open it in VSCode
• install_vue_project — The install_vue_project tool exposed by this server
• install_next_project — The install_next_project tool exposed by this server
• open_in_vscode — The open_in_vscode tool exposed by this server
• check_directory — The check_directory tool exposed by this server

Configuration

• Node.js (which includes npm) * Visual Studio Code (for features that open projects in VSCode)

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Git Terminal Server's toolset — execute_command, git_clone, install_react_project and 4 more — is a fair guide to whether it matches your workflow. It is maintained by AbdurRaahimm; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against MCP Git Terminal Server's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp git terminal server mcp server does with a few real requests.