What are the required configuration fields?
The `allowedCommands` list, `defaultTimeout`, and `defaultCwd` are configurable; the README shows `npm`, `node`, and `git` as examples for allowed commands and a 30-second timeout.
@modelcontextprotocol/server Terminal MCP Server
@MCP-Mirror
Basic information
About @modelcontextprotocol/server Terminal MCP Server
Mirror of
@modelcontextprotocol/server Terminal MCP Server config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"terminal": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-terminal"
]
}
}
}@modelcontextprotocol/server Terminal MCP Server tools
Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
Fetch the live tool list by running this server in a temporary sandbox using the button above.
Overview
What is @modelcontextprotocol/server-terminal?
A terminal server implementation for the Model Context Protocol (MCP). It provides secure and controlled access to shell commands and npm operations, designed for MCP integrations that need to run terminal tasks programmatically.
How to use @modelcontextprotocol/server-terminal?
Install the package via npm, then add the provided JSON configuration to your MCP config file. The configuration defines allowed commands, a default timeout, a working directory, and environment variables.
Key features of @modelcontextprotocol/server-terminal
- Execute shell commands with full control
- Built-in npm operations (install, run scripts)
- Timeout handling for long-running commands
- Security through an allowed commands list
- Environment variables management
- Working directory control
- TypeScript support
Use cases of @modelcontextprotocol/server-terminal
- Run build, dev, or test scripts in a project directory
- Install npm packages automatically as part of an MCP workflow
- Execute controlled shell commands (e.g., git operations) with timeouts
- Manage development environment variables for consistent command execution
Frequently asked questions
How does the server enforce security?
It restricts which commands can be run via the `allowedCommands` configuration array—only those listed (e.g., `npm`, `node`, `git`) are permitted.
What npm operations are built-in?
The server exposes `install()`, `runScript()`, `dev()`, and `build()` methods for common npm tasks like installing packages and running scripts.
Does it support custom environment variables?
Yes, you can set environment variables like `NODE_ENV` through the `environmentVariables` configuration object.
What runtime or dependencies does it require?
It requires Node.js and npm to be installed, and it is installed via `npm install @modelcontextprotocol/server-terminal`.
More Developer Tools MCP servers
Yocoolab
YocoolabMCP server for AI Agents — exposes Yocoolab feedback threads and design selections as tools
1
MCP Server By TestMu AI
TestMu AITestMu AI MCP Server lets developers run, debug, and triage tests through natural language directly from their IDE (Cursor, Claude, GitHub Copilot, and other MCP clients). It exposes five tools — HyperExecute (test orche
Moxie Docs
Jackalope-DevAutomated codebase documentation for GitHub: searchable docs, MCP context for AI agents, doc drift detection, and Friday Cleanup PRs.
1
Windframe
Windframe MCP gives your AI the design taste needed to create consistent, production-ready UI that feels intentionally designed. Available at https://windframe.dev/mcp
ArtiBot Cloud MCP - Zhijiangyun 智匠云
bofobArtiBot Cloud MCP (Zhijiangyun 智匠云) — cloud MCP server for robot manipulation data & GPU workloads. 15 tools: robot fleet management, data collection & video recording, post-processing pipelines, and benchmark evaluation
1
Comments