@modelcontextprotocol/server-terminal

What is @modelcontextprotocol/server-terminal?

@modelcontextprotocol/server-terminal is an MCP server that provides secure, controlled access to terminal commands and npm operations over the Model Context Protocol. It lets AI agents execute shell commands, install packages, and run scripts in a sandboxed environment with configurable security constraints.

How to use @modelcontextprotocol/server-terminal?

Install the package via npm, then add the server to your MCP configuration file. In the config, you define an allowedCommands whitelist, a default timeout, a working directory, and optional environment variables. Once configured, you invoke operations like executeCommand, install, or runScript through the MCP client.

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 and working directory control
• TypeScript support

Use cases of @modelcontextprotocol/server-terminal

• Automate build and test workflows by running npm scripts
• Execute safe, predefined shell commands from an AI assistant
• Install npm packages and manage dependencies programmatically
• Run development servers (npm run dev) or builds (npm run build) via MCP

FAQ from @modelcontextprotocol/server-terminal

What commands can the server run?

Only commands listed in the allowedCommands configuration array (e.g., npm, node, git) may be executed. This provides a security boundary.

How are long-running commands handled?

The server enforces a configurable defaultTimeout (default: 30000 ms). Commands that exceed the timeout are terminated.

What runtime dependencies are required?

Node.js and npm are required. The server itself is installed via npm and runs as a Node.js process.

Where does the server execute commands?

Commands run in the directory specified by defaultCwd in the configuration. This can be overridden per invocation via the cwd option.

How are environment variables managed?

You can set a base set of environment variables in the configuration under environmentVariables. These are passed to every command.