Skip to content

Fix startup failure with MCP 2.0 - #9

Open
flujo-app wants to merge 1 commit into
Kiln-AI:mainfrom
flujo-app:fix/mcp-2-compatibility
Open

Fix startup failure with MCP 2.0#9
flujo-app wants to merge 1 commit into
Kiln-AI:mainfrom
flujo-app:fix/mcp-2-compatibility

Conversation

@flujo-app

Copy link
Copy Markdown

What does this PR do?

Fresh installs can resolve mcp==2.0.0, but Kilntainers 0.1.3 imports the MCP 1.x mcp.server.fastmcp API. This causes the kilntainers entry point to fail immediately with ModuleNotFoundError.

Constrain MCP to the compatible 1.x release line and refresh the lockfile metadata. The lower bound remains unchanged.

Related Issues

No existing issue found.

Contributor License Agreement

I, @flujo-app, confirm that I have read and agree to the Contributors License Agreement.

Verification

  • uv run pytest -q -m "not integration and not e2e and not http_integration" — 294 passed, 134 deselected
  • uv run pytest -q src/kilntainers/test_cli.py src/kilntainers/test_server.py — 84 passed
  • Built wheel metadata contains Requires-Dist: mcp<2,>=1.26.0
  • A repaired tool install resolves MCP 1.29.0 and kilntainers --help succeeds

Checklists

  • Tests have been run locally and passed
  • New tests have been added to any work in /lib (not applicable; no /lib code changed)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants