misiektoja/kill-process-mcp

Cross-platform **MCP** (Model Context Protocol) server exposing LLM-accessible tools to **list and kill OS processes** via natural language queries.
Perfect for shy ninjas who just want rogue processes gone: **"Find and nuke the damn CPU glutton choking my system!"**
Demo
Tools
The following tools are exposed to MCP clients:
- process_list: Lists running processes sorted by CPU or memory with optional name, user, status, CPU/memory thresholds, system-process filtering, sort order and limit
- process_kill: Terminates the selected process (with extreme prejudice!)
Requirements
* MCP-compatible LLM client (like Claude Desktop or Cursor)
* OS: macOS/Windows/Linux
* Python 3.13 or higher
* uv
* Libraries: mcp psutil
Installation
You can install kill-process-mcp in two ways:
1. **Preferred:** use uvx - no cloning or setup needed.
2. **Alternative:** clone the repo and set up manually.
---
1. Install uv (required for both methods)
Install uv if missing:
In case of the preferred uvx method you can now configure your MCP client (skip the cloning step below).
2. Clone the repo and install (only required for alternative mode, skip for uvx)
Install dependencies:
3. Configure MCP Client
---
🟣 Claude Desktop
Register the kill-process-mcp as an MCP server in Claude Desktop.
Add the following to claude_desktop_config.json file if you want to use uvx method (recommended):
In case of an alternative manual method using a cloned repo:
Default claude_desktop_config.json location (if the file is missing - create it):
- macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
- Windows: %APPDATA%\Claude\claude_desktop_config.json
Replace /path/to/kill-process-mcp with the actual path of your project folder (remember to escape backslash characters if you're on Windows, e.g.: C:\\path\\to\\kill-process-mcp)
Restart Claude Desktop and it should be able to talk to the kill-process-mcp server.
You can check if the server is loaded by going to **Profile → Settings → Connectors**.
---
🟢 Cursor
Register the kill-process-mcp as an MCP server in Cursor.
Open Cursor settings and click **Tools & MCP → Add Custom MCP**.
Once the mcp.json file opens, add the following if you want to use uvx method (recommended):
In case of an alternative manual method using a cloned repo:
Default mcp.json location:
- macOS/Linux: ~/.cursor/mcp.json
- Windows: %USERPROFILE%\.cursor\mcp.json
Replace /path/to/kill-process-mcp with the actual path of your project folder (remember to escape backslash characters if you're on Windows, e.g.: C:\\path\\to\\kill-process-mcp)
You should be able to talk to the kill-process-mcp server now.
You can check if the server is loaded by going to Cursor settings and clicking **Tools & MCP**.
---
Optional: Install a Persistent Shim
If you prefer faster startup or offline use while using the uvx method, you can install a local shim once:
Then change your LLM client config to:
Example Hit Contracts
Here are some example prompts you can use with your MCP-compatible AI assistant when interacting with this MCP server: