Ipybox vs MCP Run Python
A side-by-side look at the Ipybox and MCP Run Python MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Ipybox for code execution work as a local process; choose MCP Run Python for code execution. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Ipybox when
- You need dedicated capabilities in the Code Execution domain.
- You prefer a local stdio subprocess transport.
Choose MCP Run Python when
- You need dedicated capabilities in the Code Execution domain.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Code Execution | Code Execution |
| Quality signal | 41/100 · Fair | 43/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | 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 | 76 | 20,815 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Ipybox | View MCP Run Python |
Tools & capabilities
Ipybox tools
No tool names declared yet. Check the project README from the listing page.
MCP Run Python tools
No tool names declared yet. Check the project README from the listing page.
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.
Ipybox
{
"mcpServers": {
"ipybox": {
"command": "uvx",
"args": [
"ipybox"
]
}
}
}
MCP Run Python
No confirmed install command for MCP Run Python yet — follow the setup steps linked from its listing page rather than a guessed package name.