Supports containerized deployment with security isolation, resource limits, and non-root execution for safe SSH orchestration operations.
Enables log inspection and monitoring of nginx servers, including error log analysis and service management across web server fleets.
Allows safe management and monitoring of Proxmox virtualization hosts, including disk usage checks and routine maintenance tasks with policy-controlled access.
Enables secure management and monitoring of TrueNAS storage systems through SSH with policy-based access controls.
MCP SSH Orchestrator
What Problem Does This Solve?
Imagine this: Your AI assistant (Claude, ChatGPT, etc.) can access your servers, but you're terrified of what it might do. rm -rf /? Delete your databases? Change firewall rules?
Now imagine this: Your AI has governed, auditable access to your infrastructure. It can check logs, restart services, and manage your fleet—but only if your security policies allow it.
That's exactly what MCP SSH Orchestrator provides: the power of AI-driven server management with deny-by-default access control, IP allowlists, host key verification, and comprehensive audit logging.
Why This Matters
Zero-Trust Security Model
Deny-by-default: Nothing runs unless explicitly allowed
Network controls: IP allowlists prevent lateral movement
Command whitelisting: Only approved commands can execute
Comprehensive audit trails: Every action is logged in JSON
Prevents Common Attack Vectors
Dangerous commands blocked:
rm -rf,dd, file deletionsNetwork isolation: Servers can't access external internet
No privilege escalation: Runs as non-root in containers
Resource limits: CPU and memory caps prevent DOS
Production-Ready Audit & Security
OWASP LLM Top 10 protected: Mitigates LLM07 (Insecure Plugin Design), LLM08 (Excessive Agency), LLM01 (Prompt Injection)
MITRE ATT&CK aligned: Prevents T1071 (Application Layer Protocol), T1659 (Content Injection)
Structured JSON audit logs: Complete audit trail with timestamps, hashes, and IPs
Forensics ready: Command hashing, IP tracking, detailed metadata
Real-time monitoring: Progress logs for long-running tasks
Who Is This For?
Homelab Enthusiasts
Automate routine server maintenance with AI
Safely manage Proxmox, TrueNAS, Docker hosts
Get help troubleshooting without losing SSH security
Security Engineers
Audit and control AI access to infrastructure
Implement zero-trust principles with policy-as-code
Meet compliance requirements with structured logging
DevOps Teams
Let AI handle routine tasks: log checks, service restarts, updates
Manage fleets of servers through conversational interface
Reduce manual toil while maintaining security standards
Platform Engineers
Enable AI-powered infrastructure management
Provide secure self-service access to developers
Bridge the gap between AI and infrastructure securely
Real-World Use Cases
Scenario 1: Homelab Automation
You say: "Claude, my home server is running slow. Can you check the disk usage on my Proxmox host?"
What happens:
Policy checks: Only
df -hallowed on that hostNetwork check: Proxmox IP is in allowlist
Command executes safely
Audit log records the operation
Scenario 2: Incident Response
You say: "Check nginx logs for errors across all web servers"
What happens:
Tag-based execution runs
tail -f /var/log/nginx/error.logon all web serversNetwork-isolated execution (no external access)
Real-time progress logs show you what's happening
Complete audit trail for post-incident review
Scenario 3: Compliance & Auditing
Your security team needs to know: "Who accessed what and when?"
What happens:
JSON audit logs capture every action with timestamps
Command hashing preserves privacy while enabling forensics
IP addresses logged for network compliance
Easy to parse with
jqfor reporting
Quick Start
Using Docker (Recommended)
Want to see it in action? Check out our Usage Cookbook with real examples!
How Security Works (The Technical Details)
Defense-in-Depth Architecture
What Gets Blocked
What Gets Allowed (Examples)
Protection Against Real Threats
MCP SSH Orchestrator directly addresses documented vulnerabilities in the MCP ecosystem:
CVE-2025-49596: Localhost-exposed MCP services → Mitigated with stdio-only transport
CVE-2025-6514: Command injection in MCP servers → Mitigated with policy-based validation
43% of MCP servers have command injection flaws → Zero-trust security model
Full Security Model Documentation | Security Risks Analysis
Documentation
Section  | What You'll Learn  | 
Practical examples and common workflows  | |
How it works under the hood  | |
Zero-trust design and controls  | |
Setting up hosts, credentials, policies  | |
Logging, monitoring, compliance  | |
Production setup guide  | 
What Can AI Do With This? (MCP Tools)
Your AI assistant gets 13 powerful tools with built-in security:
Discovery & Planning
ssh_list_hosts- See all available serversssh_describe_host- Get host details and tagsssh_plan- Test commands before running (dry-run mode)
Execution
ssh_run- Execute single command on one serverssh_run_on_tag- Run command on multiple servers (e.g., all "web" servers)ssh_run_async- Start long-running tasks in background
Monitoring & Control
ssh_get_task_status- Check progress of async tasksssh_get_task_output- Stream output in real-timessh_get_task_result- Get final result when donessh_cancel- Stop a running task safely
Management
ssh_reload_config- Update hosts/credentials without restartssh_ping- Verify connectivity to a host
Complete Tools Reference with Examples
Learn More
Key Differentiators
Production-Ready Security: OpenSSF Scorecard 7.5+ score
Zero-Trust Architecture: Deny-by-default, allow-by-exception
OWASP LLM Top 10 Protected: Mitigates insecure plugin design, excessive agency, prompt injection
MITRE ATT&CK Aligned: Prevents content injection and unauthorized protocol usage
Security-Focused: Built on security-first principles against real CVEs (CVE-2025-49596, CVE-2025-6514)
Easy Integration: Works with Claude, ChatGPT, and any MCP client
Open Source: Apache 2.0 licensed, community-driven
What Users Are Saying
"Finally, I can let Claude manage my Proxmox cluster without fear!" - Homelab Admin
"This is what infrastructure-as-code should have been. Declarative security for AI access." - Platform Engineer
"The structured audit logs make incident response so much easier." - Security Engineer
Contributing
We welcome contributions! See our Contributing Guide for:
Development setup
Code of conduct
How to submit PRs
Architecture decisions
License
Apache 2.0 - See LICENSE for details.
Links
GitHub Repository - Star us on GitHub!
Issue Tracker - Report bugs or request features
MCP Specification - Learn about MCP
Docker MCP Security Guide - Security best practices
remote-capable server
The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.
Provides policy-driven, auditable SSH access to server fleets for AI assistants with zero-trust security controls, command whitelisting, and comprehensive audit logging to safely manage infrastructure.