A side-by-side look at the Axint and Munim Computer Use MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Axint for os automation work as a local process; choose Munim Computer Use for os automation as a local process. You can also run both side by side in one mcpServers block.
wait_timeout_ms.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 59/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | 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 | 18 | 16 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 1 |
| Full listing | View Axint | View Munim Computer Use |
No tool names declared yet. Check the project README from the listing page.
wait_timeout_msdefaults to `8000`, accepts integers `0`–`10000`; `0` checksPaste 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.
{
"mcpServers": {
"agenticempire-axint": {
"command": "npx",
"args": [
"-y",
"-p",
"@axint/compiler",
"axint"
]
}
}
}
{
"mcpServers": {
"munim-computer-use": {
"command": "npx",
"args": [
"-y",
"munim-computer-use"
]
}
}
}