Agent Device vs Kill Process MCP
A side-by-side look at the Agent Device 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 Agent Device for os automation work; 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 Agent Device when
- You need dedicated capabilities in the OS Automation domain.
- Its auth model fits you: No auth required.
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 | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4,971 | 14 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | 2 |
| Full listing | View Agent Device | View Kill Process MCP |
Tools & capabilities
Agent Device tools
No tool names declared yet. Check the project README from 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.
Agent Device
No confirmed install command for Agent Device yet — follow the setup steps linked from its listing page rather than a guessed package name.
Kill Process MCP
{
"mcpServers": {
"misiektoja-kill-process-mcp": {
"command": "uvx",
"args": [
"kill-process-mcp@latest"
]
}
}
}
Frequently asked questions
Agent Device is categorized under OS Automation and uses an install path we have not confirmed yet. Kill Process MCP belongs to OS Automation and uses a local stdio subprocess. Pick Agent Device 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. Agent Device has no confirmed install command yet — follow its own setup instructions.
Agent Device is listed as free. Auth: no auth required. 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 callstackincubator-agent-device and misiektoja-kill-process-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent Device has a quality signal of 52/100 (Good) with 1 views, 0 installs and 4,971 GitHub stars. Kill Process MCP has 48/100 (Fair) with 3 views, 0 installs and 14 GitHub stars.