A side-by-side look at the Python Exec Sandbox and ScratchRun MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Python Exec Sandbox for code execution work as a local process; choose ScratchRun for code execution as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Python Exec Sandbox when
You need dedicated capabilities in the Code Execution domain.
execute_pythonExecute a Python script with automatic dependency management.
ScratchRun 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.
Python Exec Sandbox is categorized under Code Execution and uses a local stdio subprocess. ScratchRun belongs to Code Execution and uses a local stdio subprocess. Pick Python Exec Sandbox for code execution work and ScratchRun for code execution.
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.
Python Exec Sandbox has no declared pricing — check the project's own site. ScratchRun has no declared pricing — check the project's own site. 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 python-exec-sandbox and scratchrun as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Python Exec Sandbox has a quality signal of 47/100 (Fair) with 1 views, 0 installs and 1 GitHub stars. ScratchRun has 40/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.