System Manager

MCP运维云端

提供方 mdlmarkham

运维云端 stdio · 本地进程 OAuth 授权 社区 / 第三方 Claude
查看接入方式

TailOpsMCP是一个安全控制平面网关,通过集中式管理SSH、Docker和HTTP目标,实现分布式基础设施的统一控制和安全策略执行。

一句话选型结论

按资料字段整理

System Manager 属于运维云端类 MCP 服务器,stdio · 本地进程,OAuth 授权,可直接接入 Claude,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类运维云端 传输方式stdio · 本地进程 鉴权OAuth 授权 部署方式本地部署
GitHub 星标 11 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

运维云端
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

控制平面Python本地部署基础设施管理安全网关DevOps工具SSH管理

安装与配置

stdio · 本地进程 OAuth 授权
客户端在本机拉起子进程,数据不出本机
pip install -r requirements.txt

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
云资源查询

查实例、存储、账单等云上资源状态。

部署与发布

把部署、重启、回滚这类操作接进对话。

监控与告警

拉取监控指标,异常时让模型帮你判断。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在运维云端场景里让模型直接调用外部能力的人。
  • 已经在用 Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
System Manager当前 未标注 stdio · 本地进程 本地部署 有 2026-05-17
lobehub 未标注 stdio · 本地进程 本地部署 有 2026-04-11
TrendRadar 未标注 stdio · 本地进程 本地部署 有 2026-04-13
Ui Tars Desktop 8a825770 未标注 stdio · 本地进程 本地部署 有 2026-05-17
ruflo 未标注 stdio · 本地进程 本地部署 有 2026-04-13
FastGPT 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

运维云端
字段来自项目仓库与公开索引,中文说明由本站标注
提供方mdlmarkham上游标注的维护方 mdlmarkham
分类运维云端本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

14.9 KB
来自项目仓库与上游目录的原文,未做删改

TailOpsMCP Gateway

🛰️ TailOpsMCP — A secure control plane gateway for managing distributed infrastructure

> Centralized management of multiple targets through a single control plane gateway — powered by MCP
> Model Context Protocol (MCP) server that operates as a control plane gateway, managing SSH, Docker, and HTTP targets through capability-based authorization and policy enforcement.


🎯 What is TailOpsMCP?

TailOpsMCP is a control plane gateway that centralizes management of distributed infrastructure through AI assistants like Claude, ChatGPT, or any MCP-compatible client. Instead of deploying agents on every node, you deploy a single gateway that manages multiple targets through SSH, Docker, and HTTP connections.

Key Operational Model:
- Control Plane Gateway: Single trusted node manages multiple targets
- Target Registry: Central configuration of managed systems
- Policy Gate: Capability-based authorization prevents "LLM imagination" risk
- Execution Layer: Orchestrates commands across different target types

Instead of remembering complex commands, just ask:

  • "Deploy my monitoring stack to all web servers"
  • "Analyze security logs across the production cluster"
  • "What's using all the CPU across all database nodes?"
  • "Update packages on all staging servers"

Perfect for infrastructure teams, SREs, and DevOps engineers managing distributed systems across multiple environments.


🚀 Quick Start

Proxmox One-Liner Deployment (Recommended)

Deploy TailOpsMCP Gateway with a single command:```bash
bash -c "$(curl -fsSL https://raw.githubusercontent.com/mdlmarkham/TailOpsMCP/master/ct/tailops-gateway.sh)"


**What this does:**
- ✅ Creates isolated LXC container with sensible defaults
- ✅ Installs TailOpsMCP with all dependencies
- ✅ Configures for Tailscale and Docker integration
- ✅ Starts the gateway service automatically
- ✅ Provides clear access instructions

**Customize deployment:**```bash
# High-performance deployment
RAM_SIZE=4096 CPU_CORES=4 DISK_SIZE=16 \
bash -c "$(curl -fsSL https://raw.githubusercontent.com/mdlmarkham/TailOpsMCP/master/ct/tailops-gateway.sh)"

# Minimal deployment
RAM_SIZE=1024 CPU_CORES=1 DISK_SIZE=4 \
bash -c "$(curl -fsSL https://raw.githubusercontent.com/mdlmarkham/TailOpsMCP/master/ct/tailops-gateway.sh)"

Alternative: Legacy Proxmox Installer

For existing workflows, the legacy installer is still available:```bash

Legacy Proxmox installer

bash -c "$(wget -qLO - https://raw.githubusercontent.com/mdlmarkham/TailOpsMCP/master/ct/build.func)"


This creates an isolated gateway container with:
- Debian 12 LXC (2GB RAM, 2 CPU cores, 8GB disk)
- Python 3.12 and all dependencies
- Tailscale OAuth authentication
- Systemd service configuration

---

## 👨‍💻 Development

### **Quick Development Setup**```bash
# Clone the repository
git clone https://github.com/mdlmarkham/TailOpsMCP.git
cd TailOpsMCP

# Set up complete development environment
make setup

# Run all quality checks
make quality

# Run tests
make test

# Fix code issues automatically
make fix

Development Environment

TailOpsMCP includes a comprehensive development environment with:

  • 🔧 Code Quality Tools: ruff, mypy, bandit, safety, isort, black
  • 🧪 Testing Framework: pytest with coverage reporting
  • 🛡️ Security Scanning: Automated security vulnerability detection
  • 📝 Pre-commit Hooks: Automatic quality checks before commits
  • 📊 Complexity Analysis: radon for code maintainability metrics
  • 🔄 CI/CD Pipeline: Automated quality checks and testing

For detailed development setup and workflow, see DEVELOPER_SETUP.md

Quality Standards

Our code quality system ensures:
- ✅ Automated Quality Checks: Every commit runs comprehensive quality checks
- 🛡️ Security First: Continuous security scanning for vulnerabilities
- 📈 Code Coverage: Minimum 80% test coverage requirement
- 🔧 Auto-Fix Tools: Automated fixing of common issues
- 📚 Comprehensive Documentation: Full documentation for all tools

Available Commands

Command Description
make setup Set up complete development environment
make quality Run all quality checks (lint, typecheck, security, complexity)
make lint Run ruff linting
make format Format code with ruff and isort
make typecheck Run mypy type checking
make security Run security scans (bandit, safety)
make complexity Run complexity analysis
make test Run tests with coverage
make fix Auto-fix code issues
make ci Run CI pipeline (quality + tests)
make clean Clean up generated files and caches

For complete command reference, see QUALITY_TOOLS_REFERENCE.md

Automation Scripts

Script Purpose
scripts/run_quality_checks.py Comprehensive quality checks runner
scripts/fix_code_quality.py Auto-fix code quality issues
scripts/setup_dev_environment.sh Complete development environment setup

For detailed automation documentation, see CODE_QUALITY.md


✨ Key Features

🚀 Current Capabilities

Control Plane Architecture

  • ✅ Target Registry - Central configuration of SSH, Docker, and HTTP targets
  • ✅ Policy Gate - Capability-based authorization with parameter validation
  • ✅ Execution Layer - Orchestrates commands across multiple target types
  • ✅ Multi-Target Operations - Execute commands across groups of targets

Target Management

  • ✅ SSH Target Support - Manage remote systems via SSH connections
  • ✅ Docker Socket Access - Control Docker hosts through socket connections
  • ✅ HTTP API Integration - Interact with web services and APIs
  • ✅ Local System Management - Manage the gateway host itself

Security & Operations

  • ✅ Capability-Based Authorization - Prevent "LLM imagination" risk through explicit allowlisting
  • ✅ Parameter Validation - Enforce constraints on operation parameters
  • ✅ Audit Logging - Comprehensive tracking of all gateway operations
  • ✅ Multi-Gateway Support - Redundant gateways for high availability

🔒 Security First

⚠️ Read the Security Advisory before production deployment

  • ✅ Tailscale Required - Encrypted transport mandatory (no built-in TLS)
  • ✅ OAuth 2.1 with TSIDP - Tailscale Identity Provider authentication
  • ✅ Non-Root Service - Runs as dedicated tailopsmcp user
  • ✅ Systemd Hardening - Full sandboxing with ProtectSystem, ProtectHome
  • ✅ Audit Logging - Complete tracking of all operations
  • ✅ Scope-Based Access - Fine-grained permission control
  • ⚠️ Approval Gates - Requires external webhook (not built-in)

🔮 Roadmap (See HOMELAB_FEATURES.md)

  • 🔄 LXC Network Auditing - Review and audit container network configs
  • 🔄 Backup & Snapshots - Automated backups with verification
  • 🔄 Certificate Management - Let's Encrypt automation
  • 🔄 Reverse Proxy Management - Traefik/Nginx/Caddy configuration
  • 🔄 Proxmox API Integration - Full VM/container management
  • 🔄 Security Scanning - Container vulnerability detection

🏗️ Control Plane Gateway Architecture```mermaid

graph TD
A[AI Assistant] -- MCP Protocol --> B[Control Plane Gateway]
B -- Policy Gate --> C[Target Registry]
C -- Execution Layer --> D[SSH Targets]
C -- Execution Layer --> E[Docker Targets]
C -- Execution Layer --> F[HTTP Targets]
C -- Execution Layer --> G[Local System]

B -- Audit Logging --> H[Audit Trail]
B -- Capability Auth --> I[Security Policy]

subgraph "Network Segments"
    J[Segment A Gateway] -- Manages --> K[Segment A Targets]
    L[Segment B Gateway] -- Manages --> M[Segment B Targets]
end

### **Architecture Overview**

**Control Plane Gateway Model:**
- **Single Gateway**: One trusted node manages multiple targets
- **Target Registry**: Central configuration of managed systems
- **Policy Enforcement**: Capability-based authorization prevents unauthorized operations
- **Execution Orchestration**: Commands routed to appropriate targets

**Security Benefits:**
- **Reduced Blast Radius**: Compromise affects only gateway, not all targets
- **Capability Allowlisting**: Explicit authorization prevents "LLM imagination" risk
- **Segment Isolation**: Gateways can be deployed per network segment
- **Audit Trail**: Comprehensive logging of all gateway operations

**Operational Model:**
- **Gateway Deployment**: Typically runs in Proxmox LXC containers for isolation
- **Target Connectivity**: SSH keys, Docker sockets, HTTP APIs for target access
- **Redundancy**: Multiple gateways can manage overlapping target sets
- **Maintenance**: Single point of control for updates and configuration

---

## 🐳 Gateway Deployment & Management

### **Proxmox LXC Gateway Deployment**

TailOpsMCP gateways are typically deployed in Proxmox LXC containers for isolation and security.

#### **Recommended LXC Configuration**```bash
# /etc/pve/lxc/103.conf
arch: amd64
cores: 2
memory: 2048
net0: name=eth0,bridge=vmbr0,firewall=1,ip=dhcp
rootfs: local-lvm:vm-103-disk-0,size=8G

# Enable Docker for target management
features: nesting=1,keyctl=1
lxc.apparmor.profile: unconfined
lxc.cgroup2.devices.allow: c 10:200 rwm  # /dev/net/tun for Tailscale

Gateway Container Features

  • Isolation: LXC containers provide process and network isolation
  • Resource Control: CPU and memory limits prevent gateway resource exhaustion
  • Security: AppArmor profiles and cgroup device controls
  • Network Access: Tailscale integration for secure remote access

Multi-Gateway Deployment Strategy

Segment-Based Deployment

Deploy gateways per network segment to limit blast radius:```yaml

Production Segment A

production-a-gateway:
segment: "production-a"
targets: ["web-a-01", "db-a-01", "cache-a-01"]

Production Segment B

production-b-gateway:
segment: "production-b"
targets: ["web-b-01", "db-b-01", "cache-b-01"]

Staging Segment

staging-gateway:
segment: "staging"
targets: ["staging-web-01", "staging-db-01"]


#### **Redundancy Configuration**

Multiple gateways can manage overlapping target sets:```yaml
# Primary gateway for production
primary-gateway:
  targets: ["web-01", "db-01", "cache-01", "monitoring-01"]

# Secondary gateway for redundancy
secondary-gateway:
  targets: ["web-01", "db-01", "cache-01", "logging-01"]

Gateway Maintenance Procedures

Updates & Upgrades```bash

Update gateway software

sudo systemctl stop tailopsmcp-mcp
cd /opt/tailopsmcp
git pull
pip install -r requirements.txt
sudo systemctl start tailopsmcp-mcp

Verify gateway health

sudo systemctl status tailopsmcp-mcp
sudo journalctl -u tailopsmcp-mcp --since "5 minutes ago"


#### **Target Registry Management**```bash
# Backup target registry
cp targets.yaml targets.yaml.backup.$(date +%Y%m%d_%H%M%S)

# Validate configuration
tailopsmcp-mcp --validate-config targets.yaml

# Reload gateway configuration
sudo systemctl reload tailopsmcp-mcp

🔐 Security & Connectivity

Tailscale Integration for Gateway Security

TailOpsMCP uses Tailscale Identity Provider (TSIDP) for OAuth 2.1 authentication, providing secure gateway access control.

Gateway Network Security

Configure Tailscale ACLs to control gateway access:```json
{
"acls": [
{
"action": "accept",
"src": ["group:tailopsmcp-admins"],
"dst": ["tag:tailopsmcp-gateway:8080"]
}
],
"tagOwners": {
"tag:tailopsmcp-gateway": ["group:tailopsmcp-admins"]
}
}


#### **Target Network Connectivity**

Ensure gateways can reach targets through Tailscale:

- **Subnet Routes**: Configure Tailscale subnet routes for cross-network access
- **ACL Rules**: Allow gateway-to-target communication
- **Service Tags**: Use tags for gateway service discovery

### **Gateway-to-Target Connectivity**

#### **SSH Target Requirements**
- Network connectivity between gateway and target
- SSH key authentication configured
- Firewall rules allowing SSH access
- Tailscale subnet routes if crossing networks

#### **Docker Target Requirements**
- Docker socket access or API endpoint reachable
- Network connectivity to Docker host
- API token authentication if using remote API

#### **HTTP Target Requirements**
- Network connectivity to API endpoint
- Authentication credentials (API keys, tokens)
- TLS/SSL certificate validation

### **Multi-Gateway Network Design**

For segment isolation and redundancy:```yaml
# Segment A Gateway
segment-a-gateway:
  network_segment: "production-a"
  targets: ["web-a-01", "db-a-01", "cache-a-01"]

# Segment B Gateway
segment-b-gateway:
  network_segment: "production-b"
  targets: ["web-b-01", "db-b-01", "cache-b-01"]

# Overlapping targets for redundancy
shared-targets: ["monitoring-01", "logging-01"]

📚 Documentation

Development Documentation

  • DEVELOPER_SETUP.md - Complete development environment setup
  • CODE_QUALITY.md - Comprehensive code quality guide
  • QUALITY_TOOLS_REFERENCE.md - Technical reference for all tools

Project Documentation

  • CONTRIBUTING.md - Contributing guidelines
  • SECURITY_REVIEW_REPORT.md - Security review results
  • HOMELAB_FEATURES.md - Feature roadmap and specifications

Technical Specifications

  • Specs Directory - Detailed technical specifications
  • Examples Directory - Usage examples and demonstrations
  • Plans Directory - Implementation plans and architecture

🤝 Contributing

We welcome contributions! Please see our Contributing Guidelines for details.

Development Workflow

  1. Fork and Clone: Fork the repository and clone locally
  2. Setup Environment: Run make setup to set up development environment
  3. Create Feature Branch: Create a feature branch for your changes
  4. Develop: Make your changes with tests
  5. Quality Checks: Run make quality to ensure code quality
  6. Submit PR: Submit a pull request with clear description

Code Quality Requirements

All contributions must:
- ✅ Pass all quality checks (make quality)
- ✅ Include comprehensive tests
- ✅ Follow security best practices
- ✅ Include documentation for new features
- ✅ Maintain backward compatibility


📄 License

This project is licensed under the MIT License - see the LICENSE file for details.


🔗 Links

  • Repository: https://github.com/mdlmarkham/TailOpsMCP
  • Documentation: https://mdlmarkham.github.io/TailOpsMCP
  • Issues: https://github.com/mdlmarkham/TailOpsMCP/issues
  • Discussions: https://github.com/mdlmarkham/TailOpsMCP/discussions

🙏 Acknowledgments

  • Model Context Protocol (MCP) - The protocol that makes this possible
  • Tailscale - Secure network connectivity
  • Proxmox - Virtualization platform
  • Python Community - Amazing ecosystem of tools and libraries

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
System Manager 怎么安装?

在客户端按下面的安装命令接入:pip install -r requirements.txt。装完在客户端配置里引用同一个包或端点。

System Manager 怎么在 Claude 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

System Manager 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

System Manager 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

System Manager 支持哪些客户端?

资料标注支持 Claude;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

System Manager 能提供哪些能力?

资料显示能力标签包括 基础设施管理、Python、Claude。具体工具清单以官方文档为准。

System Manager 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

System Manager 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。