Runs Python code locally within an interactive REPL environment.
Most developer tooling work still happens through a UI a human drives. Python Local MCP server moves it into the conversation instead. Runs Python code locally within an interactive REPL environment.
An MCP Server that provides an interactive Python REPL (Read-Eval-Print Loop) environment.
The server publishes 4 tools. What each one is for:
python_repl — Executes Python code in a persistent sessionResources — The server provides access to REPL session history: - Custom repl:// URI scheme for accessing session history - Each session's history can be viewedTools — The server implements one tool: - python_repl: Executes Python code in a persistent session - Takes code (Python code to execute) and session_id asDebugging — Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the [MCPThe server ships on npm as @modelcontextprotocol/inspector, 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.
Configuration is passed through the environment: UV_PUBLISH_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Python Local's toolset — python_repl, Resources, Tools and 1 more — is a fair guide to whether it matches your workflow. It is maintained by Alec2435; 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 |
|---|---|
| python_repl | Executes Python code in a persistent session |
| Resources | The server provides access to REPL session history: - Custom repl:// URI scheme for accessing session history - Each session's history can be viewed as a text/plain resource - History shows input code and corresponding o |
| Tools | The server implements one tool: - python_repl: Executes Python code in a persistent session - Takes code (Python code to execute) and session_id as required arguments - Maintains separate state for each session - Support |
| Debugging | Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector). |
"mcpServers": {
"python_local": {
"command": "uv",
"args": [
"--directory",
"/path/to/python_local",
"run",
"python_local"
]
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| UV_PUBLISH_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.