Sandboxed Python execution for AI agents. PEP 723 inline deps, multi-version Python, zero pollution.
Most cloud and infrastructure work still happens through a UI a human drives. Python Exec Sandbox MCP server moves it into the conversation instead. Sandboxed Python execution for AI agents. PEP 723 inline deps, multi-version Python, zero pollution.
Sandboxed Python execution for AI agents. Scripts run in ephemeral, isolated environments with inline dependencies (PEP 723) -- zero host pollution, zero leftover venvs, zero package conflicts.
The server publishes 6 tools. What each one is for:
Cursor — The Cursor tool exposed by this serverexecute_python — Execute a Python script with automatic dependency managementcheck_environment — Returns information about the execution environment: Python version, uv version, platform, sandbox status, and configurationvalidate_script — Validates a script's PEP 723 metadata and dependencies without executing itSetup — The Setup tool exposed by this serverContributing — The Contributing tool exposed by this serverAll setups require: - Python 3.13+ -- to run the MCP server process - uv -- manages script execution, dependency resolution, and Python version downloads. Also provides uvx for running the server without installing it globally. Additional requirements depend on your chosen sandbox backend: | Setup | Additional requirements |
The server ships on npm as @devcontainers/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Python Exec Sandbox's toolset — Cursor, execute_python, check_environment and 3 more — is a fair guide to whether it matches your workflow. It is maintained by lu-zhengda; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Cursor | The Cursor tool exposed by this server. |
| execute_python | Execute a Python script with automatic dependency management. |
| check_environment | Returns information about the execution environment: Python version, uv version, platform, sandbox status, and configuration. |
| validate_script | Validates a script's PEP 723 metadata and dependencies without executing it. |
| Setup | The Setup tool exposed by this server. |
| Contributing | The Contributing tool exposed by this server. |
{
"mcpServers": {
"python-exec-sandbox": {
"command": "npx",
"args": ["-y", "@devcontainers/cli"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
All setups require: - Python 3.13+ -- to run the MCP server process - uv -- manages script execution, dependency resolution, and Python version downloads. Also provides uvx for running the server without installing it globally. Additional requirements depend on your chosen sandbox backend: | Setup | Additional requirements |
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.
AWS Labs' official server suite — current AWS docs, CDK guidance, cost analysis and service tools.
Cloud browsers for AI agents — automation sessions that run in Browserbase's fleet, not on your machine.
Workers, KV, R2 and D1 by conversation — Cloudflare's official remote servers for building and observability.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.