mcp-clickhouse v0.6.0
This release moves mcp-clickhouse to FastMCP 4 and adds MCP 2026-07-28 support while preserving legacy MCP clients and the standalone HTTP+SSE transport.
Before upgrading
- Custom middleware that sets ClickHouse client overrides must await
Context.set_state()and useserializable=False. - The standalone HTTP+SSE transport remains available but is deprecated. Use Streamable HTTP for new deployments.
- Deployments that used FastMCP 2's default OAuth proxy client storage must have clients register and authorize again.
- FastMCP no longer supports Supabase HS256 verification. Use RS256 or ES256.
- Modern HTTP clients should send
MCP-Protocol-Versionon every POST request.
Highlights
- Supports MCP
2026-07-28withserver/discover, sessionless requests, response caching hints, and request metadata validation. - Keeps initialize compatibility for MCP
2024-11-05through2025-11-25. - Preserves static token and OAuth authentication, Host and Origin checks, trusted proxy handling, and the minimal unauthenticated
/healthendpoint. - Fixes pagination token races and preserves cursors across failures and cancellation.
- Runs metadata work in a separate bounded executor so schema discovery does not delay queries.
- Reports the mcp-clickhouse package version in protocol responses.
Full Changelog: v0.5.0...v0.6.0