v0.2.0

[abby3010]

Summary

• Pins fastmcp to an exact version (fastmcp==4.0.5) instead of the previous fastmcp>=3.2.4,<4.0.0 range. This package's dependency declaration is effectively the safety net for the whole MewCP server fleet (every consumer currently declares fastmcp>=0.1.0 / fastmcp-credentials>=0.1.0 with no ceiling), so an exact pin here is now required to stop a future fastmcp release from getting silently picked up on someone else's unrelated redeploy.
• Targets FastMCP 4 / MCP Python SDK v2 and the modern, stateless 2026-07-28 protocol only (no initialize handshake, no Mcp-Session-Id). Drops fastmcp<4.0.0 support entirely, no dual-compat shim.
• No source changes were needed. fastmcp.server.middleware (Middleware, MiddlewareContext) and fastmcp.server.dependencies (get_http_request) resolve identically under FastMCP 4, and the package never touches Context/ctx, so it has no exposure to FastMCP 4's Context-related breaking changes.
• Bumps version 0.1.1 → 0.2.0 since this is a breaking dependency-floor change, not a patch.

Testing

• Added tests/test_integration_http.py: real FastMCP app mounted as a stateless Streamable HTTP ASGI app, driven with real HTTP requests. Covers the oauth credential path via HeaderCredentialBackend end to end (previously untested outside unit mocks), alongside static, confirms MissingCredentialHeaderError surfaces correctly as a JSON-RPC error, and stress-tests ContextVar isolation under concurrent stateless requests.
• Full suite: 91/91 passing against fastmcp==4.0.5 (83 pre-existing + 8 new).
• mypy --strict: clean.
• ruff check on the new file: clean. (The repo has ~32 pre-existing lint findings elsewhere, surfaced by a newer ruff than this repo was last checked with; unrelated to this change, left untouched.)
• python -m build + twine check: both dists pass; wheel metadata confirms Requires-Dist: fastmcp==4.0.5.

Also in this release

• README rewritten for plainer languphrasing) and updated to document the new FastMCP 4 / exact-pin requirem
• CHANGELOG entry for 0.2.0.

Migration notes for consumers

Bump the fastmcp pin to 4.0.5 (or re0.2.0,<0.3.0) and redeploy. No codechanges required.

What's Changed

• Upgrade to FastMCP 4, exact-pin fastmcp, bump to 0.2.0 by @abby3010 in Upgrade to FastMCP 4, exact-pin fastmcp, bump to 0.2.0 #1

New Contributors

• @abby3010 made their first contribution in Upgrade to FastMCP 4, exact-pin fastmcp, bump to 0.2.0 #1

Full Changelog: v0.1.1...v0.2.0

---

This discussion was created from the release v0.2.0.