mcp-forge/pyproject.toml
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

30 lines
595 B
TOML

[project]
name = "mcp-forge"
version = "0.1.0"
description = "Add your description here"
readme = "README.md"
authors = [
{ name = "Hans Aschauer", email = "hans.git@ch23.de" }
]
requires-python = ">=3.13"
dependencies = [
"fastmcp>=2.14.5",
"jupyter-client>=8.8.0",
"podman>=5.7.0",
"pydantic>=2.12.5",
"pyyaml>=6.0.3",
]
[project.scripts]
mcp-forge = "mcp_forge.__main__:main"
[build-system]
requires = ["uv_build>=0.9.26,<0.10.0"]
build-backend = "uv_build"
[dependency-groups]
dev = [
"pytest>=9.0.2",
"pytest-asyncio>=1.3.0",
"pytest-mock>=3.15.1",
]