create-python-replLABSCO SUMMARY
Two tools, and the second one is the whole point.
Code execution servers usually run each snippet in a fresh process, which means loading the dataframe again on every question. Addressing a long-lived REPL by ID removes that: load once, then ask five follow-up questions against the object still in memory.
What it is
A thin server over ForeverVM. It creates a Python REPL and hands back an ID; every later call runs code in that same REPL, so variables and imports persist instead of starting from an empty interpreter each time.
What you get
- Create a Python REPL and get its ID back
- Run code in a named REPL and get the result of the execution
- Persistent state across calls, because the REPL is addressed by ID rather than recreated
- Several REPLs at once if you want separate working contexts
Requirements
Node, and the install command does the client wiring: npx forevervm-mcp install --claude. For other clients the package is forevervm-mcp and the vendor documents the configuration. Running it locally for development points the client at npm with the repository path.
Setup effort
One command — npx forevervm-mcp install --claude
USE CASES
01
Exploring data across several questions
Create the REPL once, load the data in the first call, and keep querying the same objects in the calls that follow.
02
Working through a calculation step by step
Run each step as its own snippet and inspect the result before writing the next, with the intermediate values still in scope.
03
Keeping two lines of work apart
Create a second REPL and address it by its own ID, so one experiment cannot overwrite the other's variables.
2 tools
Listed in project docs. Your client may show a different list.
run-python-in-replBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
npx on PATH
INSTALLATION
Connect your client
Server setup
Claude Desktop
TERMINAL
npx forevervm-mcp install --claude
