MCP Terminal Server
The MCP Terminal Server is a secure command-line interface that enables AI models to interact with your terminal while maintaining security and control. With this server, you can:
Execute Commands: Run terminal commands securely with configurable permissions, including remote execution via SSH
File System Operations: Perform operations within strictly allowed paths
Environment Variable Management: Securely manage environment variables for command execution
Cross-Platform Support: Operate on Windows, macOS, and Linux systems
Security: Benefit from command validation, restricted paths, and proper error handling
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Terminal Server list files in my current directory"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Terminal Server
A secure command-line interface server for the Model Context Protocol (MCP) that enables AI models to interact with your terminal while maintaining security and control.
Features
π Secure command execution with configurable permissions
π File system operations within allowed paths
π Environment variable management
π» Cross-platform support (Windows, macOS, Linux)
π Remote system connections support via command execution
Related MCP server: Shell MCP Server
Usage with Claude Desktop
Add the server configuration to your Claude Desktop config file:
{
"mcpServers": {
"terminal": {
"command": "npx",
"args": [
"@dillip285/mcp-terminal",
"--allowed-paths",
"/path/to/allowed/directory"
]
}
}
}Restart Claude Desktop to apply the changes. You can now use the terminal capabilities through Claude with secure file access and command execution.
Available Tools
execute_command: Run terminal commands securely (including SSH and remote commands)
Security
All operations are restricted to specified allowed paths
Commands are validated and sanitized before execution
Environment variables are carefully managed
Proper error handling for security-related issues
Development
# Clone the repository
git clone https://github.com/dillip285/mcp-terminal.git
# Install dependencies
npm install
# Configure npm authentication
cp .npmrc.example .npmrc
# Edit .npmrc and add your NPM_TOKEN
# Run tests
npm test
# Build the project
npm run buildPublishing
To publish the package:
Copy
.npmrc.exampleto.npmrcAdd your npm authentication token to
.npmrcRun
npm publish --access public
Note: Never commit your .npmrc file with the authentication token. It is already added to .gitignore.
Contributing
Fork the repository
Create your feature branch (
git checkout -b feature/amazing-feature)Commit your changes (
git commit -m 'feat: Add amazing feature')Push to the branch (
git push origin feature/amazing-feature)Open a Pull Request
License
MIT License - see the LICENSE file for details.
Related Projects
Support
For bug reports and feature requests, please open an issue.
Available Tools
1 toolexecute_commandC
Execute a command in the local system
Inputs: command (required), args, cwd.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'execute_command' has a clear and distinct purpose that cannot be confused with any other tool in this set.
The single tool name 'execute_command' follows a verb_noun pattern, and with only one tool, the naming is inherently consistent. There are no other tools to compare against, so no inconsistencies can arise.
A single tool for a terminal server feels too minimal for the apparent scope. While it covers basic command execution, typical terminal operations might include listing files, navigating directories, or managing processes, suggesting a gap in functionality.
The tool surface is severely incomplete for a terminal server domain. It only allows command execution, missing essential operations like file browsing, process management, or environment inspection, which are core to terminal workflows and will likely cause agent failures.
Maintenance
Related MCP Connectors
Operate Linux, macOS and Windows from your LLM. Every action runs through an auditable allowlist.
Remote MCP server exposing your Node Command fleet (files, shell, processes, browser) to AI hosts.
Use your own Windows, Mac or Linux computer from ChatGPT, Claude, Cursor or Gemini CLI: run commands, read, write and search files, run long processes. Your computer only makes an outgoing connection (no open ports or VPN). Read-only mode, allowed folders, blocked commands and an action log keep you in control. Free plan available.
Secure Linux sandboxes for AI agents, as MCP tools.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA secure server that allows LLM applications like Claude to execute whitelisted system commands with user confirmation and comprehensive security features.-
- AlicenseBqualityDmaintenanceA secure server that enables AI applications to execute shell commands in specified directories, supporting multiple shell types (bash, sh, cmd, powershell) with built-in security features like directory isolation and timeout control.123Apache 2.0
- AlicenseAqualityFmaintenanceAn MCP server that enables secure terminal command execution, directory navigation, and file system operations through a standardized interface for LLMs.1080 PyPI94MIT
- AlicenseBqualityDmaintenanceA secure terminal execution server that enables controlled command execution with security features and resource limits via the Model Context Protocol (MCP).14 npm11MIT