durable-mcp 0.1.1

Durable Model Context Protocol (MCP) helpers for building resumable MCP servers on top of Reboot durable workflows.

Reboot Durable MCP

A framework for building durable MCP servers.

• Takes advantage of the protocols ability to resume after disconnection.

• Allows for the server itself to be restarted(!) and any existing requests to be retried safely thanks to Reboot workflows.

THIS IS IN PRE-ALPHA STAGE, EXPECT CHANGES, BUG FIXES, ETC; DO NOT RUN IN PRODUCTION!

First grab all dependencies:

uv sync

Activate the venv:

source .venv/bin/activate

Generate code:

rbt generate

Make sure you have Docker running:

docker ps

And run the test(s):

pytest tests

Publishing to PyPI

1. Tag the release (use semantic versioning):

git tag v0.x.y

2. Update the version in pyproject.toml to match the tag:

TAG=$(git describe --tags --abbrev=0 | sed 's/^v//')
sed -i "s/^version = \".*\"/version = \"$TAG\"/" pyproject.toml
git add pyproject.toml && git commit -m "chore: set version to $TAG"

2. Clean old build artifacts:

rm -rf dist build *.egg-info

3. (Ensure deps) Install build + upload tools (if not already in the env):

uv pip install --upgrade build twine

4. Build sdist and wheel:

python -m build

5. Validate artifacts:

twine check dist/*

6. Upload to PyPI:

twine upload dist/*

7. Push tag:

git push --follow-tags origin main

Notes:

• Ensure api/ generated code and reboot/ sources are committed before building.
• If you add new packages or data files update pyproject.toml [tool.hatch.build.targets.wheel].packages or MANIFEST.in.
• Type information is included via reboot/py.typed.

Supported client --> server requests:

• initialize
• tools/call
• tools/list
• prompts/get
• prompts/list
• resources/list
• resources/read
• resources/templates/list
• resources/subscribe
• resources/unsubscribe
• completion/complete
• logging/setLevel

Supported client --> server notifications:

• notifications/initialized
• notifications/roots/list_changed

Supported client <-- server requests:

• elicitation/create
• roots/list
• sampling/createMessage

Supported client <-- server notifications:

• notifications/progress
• notifications/message
• notifications/prompts/list_changed
• notifications/resources/list_changed
• notifications/tools/list_changed
• notifications/resources/updated

Supported client <--> server notifications:

• notifications/cancelled

TODO:

• EventStore support for resumability
• Docs
• yapf
• Push to durable-mcp in pypi.org
• Pydantic state for each session