io.github.gradion-ai/ipybox
Unified execution environment for Python code, shell commands, and programmatic MCP tool calls
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
ipyboxclaude mcp add ipybox -- uvx ipybox==0.9.2 --workspace '<directory_path>' --sandbox --sandbox-config '<file_path>' --log-level '<DEBUG|INFO|WARNING|ERROR|CRITICAL>'
{
"mcpServers": {
"ipybox": {
"command": "uvx",
"args": [
"ipybox==0.9.2",
"--workspace",
"<directory_path>",
"--sandbox",
"--sandbox-config",
"<file_path>",
"--log-level",
"<DEBUG|INFO|WARNING|ERROR|CRITICAL>"
]
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
ipybox
mcp-name: io.github.gradion-ai/ipybox
ipybox is a unified execution environment for Python code, shell commands, and programmatic MCP tool calls.
Overview
ipybox executes code blocks in a stateful IPython kernel. A code block can contain any combination of Python code, shell commands, and programmatic MCP tool calls. Kernels can be sandboxed with sandbox-runtime, enforcing filesystem and network restrictions at OS level.
It generates Python APIs for MCP server tools via mcpygen, and supports application-level approval of individual tool calls and shell commands during code execution. ipybox runs locally on your computer, enabling protected access to your local data and tools.
[!NOTE] Next generation ipybox
This is the next generation of ipybox, a complete rewrite. Older versions are maintained on the 0.6.x branch and can be obtained with
pip install ipybox<0.7.
Documentation:
- 📚 Documentation
- 🏗️ Architecture
- 🤖 llms.txt
- 🤖 llms-full.txt
Capabilities
| Capability | Description |
|---|---|
| Stateful execution | State persists across executions in IPython kernels |
| Unified execution | Combine Python code, shell commands, and programmatic MCP tool calls in a code block |
| Shell command execution | Run shell commands via !cmd syntax, capture output into Python variables |
| Programmatic MCP tool calls | MCP tools called via generated Python API ("code mode"), not JSON directly |
| Python tool API generation | Typed functions and Pydantic models generated from MCP tool schemas via mcpygen |
| Application-level approval | Individual approval of tool calls and shell commands during code execution |
| Lightweight sandboxing | Optional kernel isolation via Anthropic's sandbox-runtime |
| Local execution | No cloud dependencies, everything runs locally on your machine |
Usage
| Component | Description |
|---|---|
| Python SDK | Python API for building applications on ipybox |
| MCP server | ipybox as MCP server for code actions and programmatic tool calling |
| Claude Code plugin | Plugin that bundles the ipybox MCP server and a code action skill |
[!TIP] Freeact agent
Freeact is a general-purpose agent built on ipybox.
Frequently asked questions
What is io.github.gradion-ai/ipybox?
Unified execution environment for Python code, shell commands, and programmatic MCP tool calls
How do I install io.github.gradion-ai/ipybox?
It runs on your machine. In Claude Code: claude mcp add ipybox -- uvx ipybox==0.9.2 --workspace '<directory_path>' --sandbox --sandbox-config '<file_path>' --log-level '<DEBUG|INFO|WARNING|ERROR|CRITICAL>'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.github.gradion-ai/ipybox need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is io.github.gradion-ai/ipybox open source?
Yes. Its code is on GitHub under the Apache-2.0 license.
Who maintains io.github.gradion-ai/ipybox?
It is published by gradion-ai. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.