terminal-x-mcp
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., "@terminal-x-mcp execute npm install with high security level"
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.
![Terminal[X]MCP Banner](/mcp/servers/rnd-pro/terminal-x-mcp/user-images?source=https%3A%2F%2Fgithub.com%2Frnd-pro%2Fterminal-x-mcp%2Fraw%2Fmain%2Fassets%2Flogo%2Fterminal-x-mcp-banner.png)
Multi-Agent Terminal Automation System with Command Planning and Security Validation
Terminal[X]MCP is a Model Context Provider (MCP) server that enables intelligent terminal automation through a multi-agent system with distributed specialized roles for command execution, security validation, and real-time monitoring.
Automate your terminal workflows intelligently - Works seamlessly with Cursor, Claude Desktop, VS Code, and other MCP-compatible applications while providing secure command execution and comprehensive monitoring.
โจ Features
๐ค Multi-Agent Architecture
Terminal Coordinator: Intelligent command planning and workflow orchestration
Command Executor: Safe command execution with environment management
Security Monitor: Command security analysis and risk prevention
Terminal Monitor: Real-time process monitoring and performance tracking
๐ง Auto-Intelligence
Command Planning: Automatic command sequence optimization
Security Validation: Real-time command risk assessment
Workflow Orchestration: Multi-step terminal automation
Error Recovery: Intelligent failure handling and retry strategies
๐ Agent Coordination
Distributed Processing: Specialized agents with focused responsibilities
Task Distribution: Intelligent workload balancing across terminal sessions
Result Aggregation: Comprehensive output collection and analysis
Resource Management: Efficient terminal resource allocation
๐ก๏ธ Security First
Command Validation: Real-time security analysis before execution
Privilege Management: Safe execution with appropriate permissions
Sandbox Execution: Isolated command execution environments
Risk Assessment: Intelligent command risk scoring
๐ Terminal Management
Multi-Session Support: Concurrent terminal session management
Process Monitoring: Real-time process tracking and analysis
Performance Metrics: Terminal performance optimization
Logging System: Comprehensive command and output logging
๐ก Intelligent Automation
Workflow Automation: Complex multi-step terminal workflows
Environment Detection: Automatic environment configuration
Dependency Resolution: Smart command dependency management
Error Handling: Robust error detection and recovery
Related MCP server: MCP Terminal
๐ Quick Start
Installation
# Clone the repository
git clone https://github.com/rnd-pro/terminal-x-mcp.git
cd terminal-x-mcp
# Install dependencies
npm install
# Copy environment configuration
cp .env.example .env
# Start the server
npm startMCP Client Configuration
Add to your MCP client configuration:
{
"mcpServers": {
"terminal-x-mcp": {
"command": "node",
"args": ["/path/to/terminal-x-mcp/src/server/index.js"],
"env": {
"NODE_ENV": "production"
}
}
}
}Basic Usage
// Example: Execute secure command workflow
await mcp.request("execute_command", {
command: "npm install && npm test",
security_level: "high",
timeout: 60000
});
// Example: Monitor terminal processes
await mcp.request("monitor_processes", {
filter: "node",
metrics: ["cpu", "memory", "duration"]
});๐๏ธ Architecture
Agent Communication Flow
โโโโโโโโโโโโโโโโโโโ โโโโโโโโโโโโโโโโโโโโ โโโโโโโโโโโโโโโโโโโ
โ MCP Client โโโโโถโ Terminal[X]MCP โโโโโถโ Command Executorโ
โ (Cursor/CLI) โ โ Coordinator โ โ Agent โ
โโโโโโโโโโโโโโโโโโโ โโโโโโโโโโโโโโโโโโโโ โโโโโโโโโโโโโโโโโโโ
โ
โโโโโโโโโดโโโโโโโโ
โผ โผ
โโโโโโโโโโโโโโโโ โโโโโโโโโโโโโโโ
โSecurity โ โTerminal โ
โMonitor Agent โ โMonitor Agentโ
โโโโโโโโโโโโโโโโ โโโโโโโโโโโโโโโ
โ โ
โผ โผ
โโโโโโโโโโโโโโโโ โโโโโโโโโโโโโโโ
โCommand โ โProcess โ
โValidation โ โMonitoring โ
โโโโโโโโโโโโโโโโ โโโโโโโโโโโโโโโMulti-Agent Roles
Terminal Coordinator Agent - Main command planning and orchestration
Command Executor Agent - Safe command execution and output handling
Security Monitor Agent - Command security analysis and validation
Terminal Monitor Agent - Process monitoring and performance tracking
๐ ๏ธ Available Tools
Core Terminal Tools
execute_command- Secure command execution with validationplan_workflow- Multi-step command workflow planningmonitor_processes- Real-time process monitoringvalidate_security- Command security assessment
Agent Coordination Tools
coordinate_execution- Multi-agent command coordinationaggregate_outputs- Command output collection and analysismanage_sessions- Terminal session management
Monitoring Tools
track_performance- Terminal performance metricsanalyze_logs- Command execution log analysismonitor_resources- System resource monitoring
โ๏ธ Configuration
Environment Variables
# MCP Server Configuration
MCP_PORT=3003
NODE_ENV=development
# Agent Configuration
AGENT_MAX_CONCURRENCY=3
AGENT_TIMEOUT=30000
# Terminal Settings
TERMINAL_MAX_SESSIONS=10
TERMINAL_COMMAND_TIMEOUT=60000
# Security Configuration
SECURITY_VALIDATION_ENABLED=true
SECURITY_RISK_THRESHOLD=0.7
# Monitoring Settings
MONITORING_ENABLED=true
MONITORING_INTERVAL=5000
# Logging Configuration
LOG_LEVEL=info
LOG_TERMINAL_OUTPUT=true๐งช Testing
# Run all tests
npm test
# Test multi-agent coordination
npm run test:agents
# Test terminal automation
npm run test:terminal
# Run security validation tests
npm run test:security๐ Project Structure
terminal-x-mcp/
โโโ src/
โ โโโ server/ # MCP server implementation
โ โโโ agents/ # Multi-agent system
โ โโโ core/ # Core functionality
โ โโโ utils/ # Utilities and helpers
โโโ test/ # Test suites
โโโ docs/ # Documentation
โโโ examples/ # Usage examples
โโโ assets/ # Assets and resources๐ค Integration Examples
Command Workflow Automation
// Automated build and deploy workflow
const result = await terminalXMCP.executeWorkflow({
commands: [
"git pull origin main",
"npm install",
"npm run build",
"npm run test",
"npm run deploy"
],
securityLevel: "high",
failFast: true
});Process Monitoring
// Monitor development server
const monitoring = await terminalXMCP.monitorProcess({
command: "npm run dev",
metrics: ["cpu", "memory", "network"],
alertThresholds: {
cpu: 80,
memory: 1024
}
});๐ฎ Roadmap
Phase 1: Foundation โ
Project structure setup
Basic MCP server implementation
Agent framework foundation
Phase 2: Core Agents (In Progress)
Terminal Coordinator implementation
Command Executor with security validation
Basic monitoring capabilities
Phase 3: Advanced Features
Multi-session terminal management
Advanced security monitoring
Workflow automation engine
Phase 4: Optimization
Performance optimization
Advanced command planning
Production deployment
๐ค Contributing
We welcome contributions! Please see our Contributing Guide for details.
Development Setup
# Clone the repository
git clone https://github.com/rnd-pro/terminal-x-mcp.git
cd terminal-x-mcp
# Install dependencies
npm install
# Start development server
npm run devSubmitting Changes
Fork the repository
Create a feature branch:
git checkout -b feature/amazing-terminal-featureCommit changes:
git commit -m 'Add amazing terminal feature'Push to branch:
git push origin feature/amazing-terminal-featureOpen a Pull Request
๐ License
MIT License - see LICENSE file for details.
๐ฅ Development Team
Developed by RND-PRO Team
๐ Website: rnd-pro.com
๐ผ Professional development team specializing in innovative AI solutions
๐ค Experts in multi-agent systems and terminal automation
๐ Leaders in MCP protocol implementations and secure command execution
๐ Acknowledgments
Built on Model Context Protocol (MCP)
Inspired by multi-agent AI architectures and secure terminal automation
Command execution powered by Node.js process management
Security validation using advanced risk assessment algorithms
๐ Support
๐ง Issues: GitHub Issues
๐ฌ Discussions: GitHub Discussions
๐ Documentation: Wiki
Made with โค๏ธ by RND-PRO Team for the terminal automation community
Available Tools
4 toolsexecute_commandC
Execute a command in the terminal with security validation
Inputs: command (required), timeout, security_level, working_directory.
monitor_processesC
Monitor running processes and collect metrics
Inputs: filter, metrics, duration.
plan_workflowB
Plan a multi-step terminal workflow
Inputs: goal (required), commands, dependencies.
validate_securityB
Validate command security and assess risk level
Inputs: command (required), context.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogโฆ
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: execute_command runs commands, monitor_processes observes processes, validate_security assesses command risk without executing, and plan_workflow designs multi-step sequences. The slight overlap between execute_command's built-in validation and validate_security is separated by execution vs assessment, so no real ambiguity exists.
All tool names follow a consistent verb_noun pattern: execute_command, monitor_processes, validate_security, plan_workflow. The verbs and nouns are clear and uniformly formatted, making the tool names predictable and easy to understand.
With 4 tools, the server is well-scoped for its stated purpose of secure terminal interaction. Each tool covers a distinct phase (planning, validation, execution, monitoring) without redundancy or bloat, falling comfortably within the ideal 3-15 range.
The set covers core terminal operations but has notable gaps: no tool for process control (e.g., kill, stop), and plan_workflow only creates a plan without an execution mechanism to run the whole workflow at once. While execute_command can handle many actions, these missing operations limit the server's end-to-end workflow support.
Maintenance
Related MCP Connectors
MCP Server for an Agent Task Marketplace
Termalin's hosted MCP server. Claude, ChatGPT or any MCP client runs commands, moves files over SFTP, queries databases and reads server metrics and monitoring alerts on your servers, keylessly through Termalin Connectors: no SSH key is handed over and no inbound port is opened. Per-host command policy and an audit log. Needs a termal.in Pro or Team account (new accounts start with a 14-day Pro trial).
Remote MCP server exposing your Node Command fleet (files, shell, processes, browser) to AI hosts.
Related MCP Servers
- AlicenseBqualityDmaintenanceA secure terminal execution server that enables controlled command execution with security features and resource limits via the Model Context Protocol (MCP).130 npm11MIT
- AlicenseCqualityDmaintenanceA server that enables AI assistants to execute terminal commands and retrieve outputs via the Model Context Protocol (MCP).326MIT
- AlicenseNot gradedqualityDmaintenanceMCP server enabling AI agents to interact with terminal applications through structured Terminal State Tree representation. Works with any AI assistant that supports the Model Context Protocol.95 npm21MIT
- AlicenseNot gradedqualityCmaintenanceA command-line interface and MCP server for managing and monitoring multiple development services through a unified terminal UI. It enables users to interact with service logs, filter messages, and control development environments directly via Model Context Protocol integration.-