A side-by-side look at the EXTRA Native Computer Use and Ibara MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose EXTRA Native Computer Use for os automation work as a local process; choose Ibara for os automation. You can also run both side by side in one mcpServers block.
Rows where the two servers differ are marked.
| Spec | I Ibara | |
|---|---|---|
| Category | OS Automation | OS Automation |
| Quality signal | 41/100 · Fair | 52/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 8 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View EXTRA Native Computer Use | View Ibara |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"extra-native-computer-use": {
"command": "npx",
"args": [
"-y",
"@yantraos/extra-desktop"
]
}
}
}
No confirmed install command for Ibara yet — follow the setup steps linked from its listing page rather than a guessed package name.