mcp-forge/docs
Hans Aschauer 244a3e5574 Implement real Jupyter backend with jupyter-client
- Replaced mock exec() implementation with real Jupyter protocol
- Uses jupyter-client (host) to connect to ipykernel (container) via ZMQ
- 1:1 mapping: one container per session, one kernel per container
- Proper Jupyter message protocol for code execution
- Kernel lifecycle management (start, execute, shutdown, restart)
- Namespace inspection via introspection code
- Idle kernel cleanup
- Connection file management
- Backed up old implementation as kernel_old.py

TODO:
- Container image needs ipykernel installed
- Need to implement proper port mapping for ZMQ
- Need to mount connection file into container
- Add better kernel readiness check
- Implement restart_kernel properly with KernelManager
- Write tests
2026-02-07 08:06:44 +01:00
..
architecture1.md Implement real Jupyter backend with jupyter-client 2026-02-07 08:06:44 +01:00
development-methodology.md initial commit after one day coding agent session 2026-02-07 07:45:57 +01:00
HTTP_TRANSPORT.md initial commit after one day coding agent session 2026-02-07 07:45:57 +01:00
todo.md Implement real Jupyter backend with jupyter-client 2026-02-07 08:06:44 +01:00