SystemKernelMCP

180+ tools for full system control: terminal, Git, Docker, Kubernetes, VMs, BIOS, kernel, cybersec (50+ pentesting tools), AI, cloud. Works with Cursor, Claude Desktop, Windsurf, and any MCP client.

What is this?

SystemKernelMCP is an MCP (Model Context Protocol) server. It gives your AI assistant (Cursor, Claude, etc.) 180+ tools to control your system: run terminal commands, manage Docker, pentest (nmap, nuclei, sqlmap, etc.), read files, and more.

You do NOT run it yourself. Your AI client (Cursor, Claude) starts it automatically when you ask for a tool.

Related MCP server: allcanuse-mcp

Quick Start (3 steps)

Step 1: Install

# Create virtual environment
python -m venv venv

# Activate (pick one for your terminal)
# Windows CMD:        .\venv\Scripts\activate
# Windows Git Bash:   source venv/Scripts/activate
# Mac/Linux:          source venv/bin/activate

# Install MCP
pip install -r requirements.txt
# or: pip install mcp

Step 2: Add to your AI client

For Cursor: This project already has .cursor/mcp.json. Just open the folder in Cursor.

For Claude Desktop: Add to claude_desktop_config.json:

{
  "mcpServers": {
    "SystemKernelMCP": {
      "command": "python",
      "args": ["C:\\full\\path\\to\\MCP SERVER\\system_mcp.py"],
      "cwd": "C:\\full\\path\\to\\MCP SERVER"
    }
  }
}

For other clients: Add the same config to your client's MCP settings.

Step 3: Restart and use

1. Restart Cursor (or your AI client)

2. Enable SystemKernelMCP in Settings → MCP

3. In chat, ask: "Run get_os_info" or "Ping google.com"

4. Approve the tool when prompted

Health check: Call health_check or get_os_info. If you get a response, it's working.

Important: Do NOT run manually

python system_mcp.py   # ❌ Wrong - will show a message and exit

This is a stdio server. It talks over stdin/stdout. Your AI client starts it automatically. Running it in a terminal does nothing useful.

Supported clients

Tools (180+)

Full list: index.html

Troubleshooting

Requirements

• Python 3.10+

• Optional (for specific tools): docker, kubectl, gh, git, nmap, terraform, aws, gcloud, redis-cli, whois, VirtualBox, VMware, Hyper-V, WSL

• Optional (cybersec tools): nmap, rustscan, masscan, gobuster, feroxbuster, ffuf, dirsearch, nuclei, nikto, sqlmap, wpscan, subfinder, amass, httpx, hakrawler, katana, gau, waybackurls, arjun, paramspider, dalfox, wafw00f, fierce, dnsenum, theHarvester, hydra, john, hashcat, enum4linux, smbmap, netexec, autorecon, gdb, radare2, ghidra, binwalk, checksec, volatility, foremost, steghide, exiftool, prowler, trivy, kube-hunter, kube-bench, checkov, terrascan