Computer Use vs Kill Process MCP
A side-by-side look at the Computer Use and Kill Process MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Computer Use for os automation work as a local process; choose Kill Process MCP for os automation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Computer Use when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- You want tools like
mouse_move, mouse_move_smooth, mouse_move_relative.
Choose Kill Process MCP when
- You need dedicated capabilities in the OS Automation domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
process_list, process_kill.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 52/100 · Good | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 14 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 44 | 2 |
| Full listing | View Computer Use | View Kill Process MCP |
Tools & capabilities
Computer Use tools 44
mouse_moveMove cursor to absolute coordinatesmouse_move_smoothSmooth cursor movement (human-like)mouse_move_relativeRelative cursor movementmouse_get_positionGet current cursor positionmouse_clickMouse clickmouse_click_atMove and clickmouse_togglePress/release mouse buttonmouse_dragDrag operationmouse_drag_smoothSmooth drag operationmouse_scrollScrollmouse_scroll_directionScroll in directionmouse_scroll_smoothSmooth scroll- +32 more on the listing page
Kill Process MCP tools 2
process_listLists running processes sorted by CPU or memory with optional name, user, status, CPU/memory thresholds, system-process filtering, sort order and limitprocess_killTerminates the selected process (with extreme prejudice!)
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Computer Use
{
"mcpServers": {
"computer-use-2": {
"command": "npx",
"args": [
"-y",
"go-computer-use-mcp-server"
]
}
}
}
Kill Process MCP
{
"mcpServers": {
"misiektoja-kill-process-mcp": {
"command": "uvx",
"args": [
"kill-process-mcp@latest"
]
}
}
}
Frequently asked questions
Computer Use is categorized under OS Automation and uses a local stdio subprocess. Kill Process MCP belongs to OS Automation and uses a local stdio subprocess. Pick Computer Use for os automation work and Kill Process MCP for os automation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Computer Use has no declared pricing — check the project's own site. Kill Process MCP is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add computer-use-2 and misiektoja-kill-process-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Computer Use has a quality signal of 52/100 (Good) with 1 views, 0 installs and 3 GitHub stars. Kill Process MCP has 48/100 (Fair) with 3 views, 0 installs and 14 GitHub stars.