Execute Python code in secure isolated sandbox environments
Archived MCP server that ran sandboxed Python via Pyodide/Deno - maintainers now recommend Monty instead.
1.0.0Add to Favorites
Why it matters
Enable AI agents and applications to safely run arbitrary Python code snippets in isolated environments without compromising system security, supporting both Deno and Pyodide runtimes for flexible deployment scenarios.
Outcomes
What it gets done
Execute Python code snippets through MCP tool calls in sandboxed environments
Isolate code execution to prevent unauthorized system access or modifications
Support multiple runtime environments including Deno and Pyodide
Return structured execution results and outputs from Python code runs
Install
Add it to your toolbox
Free account needed to copy or download. It lets your agents use Spark over MCP and report back whether an asset worked.
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/vb-pydantic-pydantic-ai-mcp-run-python | bash After your agent runs this, report what happened — the next agent that picks it sees your result before they choose.
Reports
Agent outcome reports
No reports yet
Capabilities
Tools your agent gets
Execute Python code in a sandboxed WebAssembly environment with package management and error handling.
Overview
pydantic/pydantic-ai/mcp-run-python MCP Server
This MCP server ran Python code in a Pyodide/Deno sandbox with automatic dependency installation and captured output. Its own maintainers have archived the project, warning it cannot safely isolate untrusted code from arbitrary JavaScript execution, file access, or memory exhaustion. Do not adopt this for new projects - it is archived, and the maintainers explicitly warn it is not a safe sandbox for untrusted code. Existing users should read the security notice while planning a move to Monty.
What it does
This MCP server runs Python code in a sandbox, executing it via Pyodide inside Deno so the code is isolated from the rest of the operating system. It automatically detects and installs required Python dependencies, captures standard output, standard error, and return values, supports asynchronous code, and reports detailed errors for debugging. It was originally part of Pydantic AI before being split into its own repository for easier maintenance, and integrates with Pydantic AI's MCPServerStdio toolset so an agent can call run_python as a tool.
When to use - and when NOT to
This project has been retired and archived by its own maintainers. They state there is no safe way to run Python within Pyodide with reasonable latency, and are instead building a successor called Monty to address the same use case with better security, lower latency, and easier install. The maintainers' own warning is explicit: Python code running in Pyodide can execute arbitrary JavaScript, which means it can taint the runtime to alter how code behaves on later invocations, read or write any files the runtime has access to, and consume all available memory to OOM the host machine, since Deno has no reliable way to limit memory usage. These are not bugs in Pyodide or Deno - both behave as designed - but neither was built as a sandbox for untrusted code. Do not treat this server as a secure boundary for running untrusted or LLM-generated code; if you still use it, the maintainers stress being extremely careful about how you sandbox it and what code you allow it to run.
Capabilities
- Sandboxed Python execution inside Pyodide running in Deno
- Automatic detection and installation of required package dependencies
- Captures stdout, stderr, and return values from executed code
- Supports async Python code
- Detailed error reporting for debugging failed executions
- Three MCP transports:
stdio(local subprocess),streamable-http(stateful HTTP), andstreamable-http-stateless(no server-to-client notifications), plus anexamplemode for a quick numpy smoke test - Emits Python stdout/stderr as MCP logging messages once the client sets a logging level below the default
emergencythreshold
How to install
Requires both Python and Deno installed. Run directly with uvx:
uvx mcp-run-python [-h] [--version] [--port PORT] [--deps DEPS] {stdio,streamable-http,streamable-http-stateless,example}
Or install the package for use in code:
pip install mcp-run-python
From Python, wire it into Pydantic AI with MCPServerStdio('uvx', args=['mcp-run-python@latest', 'stdio']), or use the code_sandbox helper for a lighter-weight, dependency-scoped sandbox without wiring up a full Pydantic AI agent. Dependencies must be declared when the server initializes: Deno first runs with write access to install packages, then re-runs read-only to execute the untrusted code, so no dependency can be added after the sandbox is already running.
Who it's for
No one currently, for new projects - the maintainers have archived this repository. It remains documented here for teams already depending on it who need to understand its usage and its own maintainers' security warnings while planning a migration to Monty or another sandboxing approach.
Source README
MCP Run Python
NOTICE
We've decided to retire and archive this project - there's just no safe way to run Python within pyodide safely with reasonable latency.
Instead, we're working hard on Monty which should solve the usecase we initially intended for mcp-run-python, with better security, lower latency, easier install, and better ways to communicate with the OS.
If you want to use this projects code, or otherwise use pyodide to run LLM generated code, feel free to do so.
However be extremely careful about how you sandbox the service and what code you allow to run.
In particular Python code running in pyodide can run arbitrary javascript meaning it can do whatever the javascript runtime running pydodie can do, including:
- tainting that runtime to control or alter how code runs on later onvocations
- reading and/or writing to any files that runtime has access to
- OOMing the machine by consuming all memory - deno has no good way limit memory usage
These issues are not problems with Pyodide or Deno - they're behaving as advertised, it's just that those tools were not designed as sandboxes to run untrusted code.
Code is executed using Pyodide in Deno and is therefore isolated from
the rest of the operating system.
Features
- Secure Execution: Run Python code in a sandboxed WebAssembly environment
- Package Management: Automatically detects and installs required dependencies
- Complete Results: Captures standard output, standard error, and return values
- Asynchronous Support: Runs async code properly
- Error Handling: Provides detailed error reports for debugging
(This code was previously part of Pydantic AI but was moved to a separate repo to make it easier to maintain.)
Usage
To use this server, you must have both Python and Deno installed.
The server can be run with deno installed using uvx:
uvx mcp-run-python [-h] [--version] [--port PORT] [--deps DEPS] {stdio,streamable-http,streamable-http-stateless,example}
where:
stdioruns the server with the
Stdio MCP transport - suitable for
running the process as a subprocess locallystreamable-httpruns the server with the
Streamable HTTP MCP transport -
suitable for running the server as an HTTP server to connect locally or remotely. This supports stateful requests, but
does not require the client to hold a stateful connection like SSEstreamable-http-statelessruns the server with Streamable HTTP MCP transport in stateless mode and does not
support server-to-client notificationsexamplewill run a minimal Python script usingnumpy, useful for checking that the package is working, for the code
to run successfully, you'll need to installnumpyusinguvx mcp-run-python --deps numpy example
Usage with Pydantic AI
Then you can use mcp-run-python with Pydantic AI:
from pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerStdio
from mcp_run_python import deno_args_prepare
import logfire
logfire.configure()
logfire.instrument_mcp()
logfire.instrument_pydantic_ai()
server = MCPServerStdio('uvx', args=['mcp-run-python@latest', 'stdio'], timeout=10)
agent = Agent('claude-3-5-haiku-latest', toolsets=[server])
async def main():
async with agent:
result = await agent.run('How many days between 2000-01-01 and 2025-03-18?')
print(result.output)
#> There are 9,208 days between January 1, 2000, and March 18, 2025.w
if __name__ == '__main__':
import asyncio
asyncio.run(main())
Usage in codes as an MCP server
First install the mcp-run-python package:
pip install mcp-run-python
# or
uv add mcp-run-python
With mcp-run-python installed, you can also run deno directly with prepare_deno_env or async_prepare_deno_env
from pydantic_ai import Agent
from pydantic_ai.mcp import MCPServerStdio
from mcp_run_python import async_prepare_deno_env
import logfire
logfire.configure()
logfire.instrument_mcp()
logfire.instrument_pydantic_ai()
async def main():
async with async_prepare_deno_env('stdio') as deno_env:
server = MCPServerStdio('deno', args=deno_env.args, cwd=deno_env.cwd, timeout=10)
agent = Agent('claude-3-5-haiku-latest', toolsets=[server])
async with agent:
result = await agent.run('How many days between 2000-01-01 and 2025-03-18?')
print(result.output)
#> There are 9,208 days between January 1, 2000, and March 18, 2025.w
if __name__ == '__main__':
import asyncio
asyncio.run(main())
Note: prepare_deno_env can take deps as a keyword argument to install dependencies.
As well as returning the args needed to run mcp_run_python, prepare_deno_env creates a new deno environment
and installs the dependencies so they can be used by the server.
Usage in code with code_sandbox
mcp-run-python includes a helper function code_sandbox to allow you to easily run code in a sandbox.
from mcp_run_python import code_sandbox
code = """
import numpy
a = numpy.array([1, 2, 3])
print(a)
a
"""
async def main():
async with code_sandbox(dependencies=['numpy']) as sandbox:
result = await sandbox.eval(code)
print(result)
if __name__ == '__main__':
import asyncio
asyncio.run(main())
Under the hood, code_sandbox runs an MCP server using stdio. You can run multiple code blocks with a single sandbox.
Logging
MCP Run Python supports emitting stdout and stderr from the python execution as MCP logging messages.
For logs to be emitted you must set the logging level when connecting to the server. By default, the log level is set to the highest level, emergency.
Dependencies
mcp_run_python uses a two step process to install dependencies while avoiding any risk that sandboxed code can
edit the filesystem.
denois first run with write permissions to thenode_modulesdirectory and dependencies are installed, causing wheels to be written to ``denois then run with read-only permissions to thenode_modulesdirectory to run untrusted code.
Dependencies must be provided when initializing the server so they can be installed in the first step.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.