Secure Python sandbox β MCP servers, APIs, shells and host functions as native Python objects.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Code. Filesystem. Context. Tools.
What if agents had one tool to rule them all?
Parselbox is an embeddable Python runtime where AI agents call tools as code β MCP servers, APIs, and shells become native Python objects. Disk-backed workspace, packages, and networking built in; a single-process execution layer powered by Deno and Pyodide.
https://github.com/user-attachments/assets/d4e43d16-3aa3-4e29-83c7-a1d3885b8045
[!TIP] Drop the Parselbox MCP alongside existing MCP server configurations. Agents instantly get a Python runtime, MCP tools as code, support for skills and a disk-backed workspace.
Parselbox packages programmatic tool calling as a local, open-source execution layer. Drop it into an existing MCP configuration with uvx, or embed the Python API into any agent stack.
Beyond code execution, Parselbox provides a stateful, disk-backed workspace with packages, controlled networking, background tasks and progressive discovery.
Deno + Pyodide provide a single-process runtime with explicit filesystem and network permissions β no containers or microVMs required. It also enables JavaScript/npm interoperability, WASM/WASI integration and generative UI through MCP Apps.
Most agent stacks expose each capability as a separate tool. As integrations grow, tool schemas consume more context. The model must also carry intermediate results, transform data and route values between calls.
An execution layer moves orchestration out of the context window and into code. Capabilities are discovered on demand, then composed with full control flow. A single execution can coordinate multiple tools while variables, state and files remain inside the runtime.
The result is less context bloat, fewer model-to-tool round trips and complex workflows expressed as code rather than chains of individual calls.
No containers, no VMs β just a single, lightweight Deno + Pyodide process (~160 MB). Deno permissions, memory caps, timeouts, network allowlists. Snapshot caching and crash recovery.
MCP servers, REST + OpenAPI, GraphQL, shell, functions and classes β all native Python objects. Stateful across calls. Pydantic auto-conversion. Credentials stay on the host.
Full CPython with js() interop β use JS packages as native Python. require() for npm, local TypeScript, and .wasm modules. Virtual bash() for shell. Auto-install packages on import.
require() any .wasm β library exports become Python methods, WASI programs become callable commands; drop one in bin/ to run it from bash() too. In-process, inherits the sandbox's mounts and permissions, installs nothing on the host.
Append .task() to any call β parallel fan-out with asyncio.gather, check progress, tail logs, drive interactive sessions with send(), await later.
Disk-backed workspace β host mounts (ro/rw), input files at /files/, outputs persisted to real directories. New and modified files are detected and returned per call.
help(), search(), inspect(), preview() β agents discover only what they need, when they need it.
display() renders HTML inline in the chat (MCP Apps), with Tailwind + daisyUI injected. Or serve a full app β built-in HTTP server with static files, live reload, file upload, and @api routes that compose across tools.
Parselbox uses Deno for the secure sandbox runtime.
1. Install Deno
2. Install Parselbox
Wire any tool into the sandbox β MCP servers, REST/GraphQL, shells, host objects β and the agent calls them as native Python, composing them with real control flow over a disk-backed workspace and both the Python and npm package ecosystems.
Example:
The Parselbox CLI runs a standalone MCP server β every sandbox option is available as a flag.
[!TIP] The "loopback" trick:
- Add the Parselbox MCP alongside your existing MCP servers.
- Point
--mcpat that same config file.- On startup, Parselbox connects to the other servers, exposes their tools inside the sandbox, and starts its own MCP server.
Don't worry β Parselbox detects and avoids connecting to itself. No infinite loops of doom.
Example:
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/parselbox)<a href="https://allmcps.com/mcp/parselbox"><img src="https://allmcps.com/api/badge/parselbox?style=directory" alt="Parselbox on AllMCPs" /></a>