LabscoMCP early access ↗
barvhaimMCP SERVER

Python Interpreter MCP

Run Python code and get stdout, stderr, the exit code and any files it produced back.

by barvhaim ↗Sandboxed Code ExecutionCommunity

LABSCO SUMMARY

Execution kept in a service you choose, not in your shell.

The server does not run the code itself; it forwards to an interpreter service you host, which is where the sandboxing decisions live. That also means nothing works until that service is up, and moving it is a matter of changing one URL in main.py.

What it is

A one-tool server that forwards Python code to a code-interpreter REST service and returns the complete execution result.

What you get

  • Arbitrary Python executed on the interpreter service rather than in your client
  • The full result: stdout, stderr, the exit code, and any files the run generated
  • An async HTTP client between the server and the interpreter service
  • A configurable interpreter endpoint, pointed at a local execute URL out of the box

Requirements

Python 3.11 or higher, uv, and a Python interpreter REST API service listening on a local port. BeeAI Code Interpreter is the one the project names.

Setup effort

One command — uvx python-interpreter-mcp