Relax anyio version so it is compatible with MCP servers

[Antonio-RiveroMartnez]

Description

We’ve run into a dependency conflict between fastmcp and firebolt-sdk due to incompatible anyio version requirements:

• fastmcp → depends on mcp, which has a hard requirement on anyio>=4.5 (ref)
• firebolt-sqlalchemy → depends on firebolt-sdk which, since 1.6.0, has a hard requirement on anyio<4.5 (ref)

Because of a high/critical security vulnerability, we had to upgrade to a newer firebolt-sqlalchemy (1.1.0) which pulls in firebolt-sdk>=1.6.0, and this introduced the conflict.

Request

Could the anyio<4.5 pin in firebolt-sdk be relaxed or removed (if it’s compatible with ≥4.5)? Or is there any hard limitation/issue that's forcing the <4.5?

It would help unblock usage with mcp when building MCP servers that connects to Firebolt

How to reproduce

python -m venv venv && source venv/bin/activate
pip install "mcp>=1.2.0" "firebolt-sqlalchemy>=1.1.0"

[ptiurin]

Hi @Antonio-RiveroMartnez , thanks for a detailed report!

anyio>4.5 affects the way our tests (or rather mocks) work so it was pinned to avoid blocking features. I'll look into what can be done to relax it.
In the meantime, you can force upgrade anyio after installing firebolt-sdk/sqlalchemy connector:

pip install firebolt-sqlalchemy
pip install -U anyio

It will complain about incompatibility but should work as usual.

[Antonio-RiveroMartnez]

Hey @ptiurin thanks for the quick response, I'll try your suggestion. Appreciated the help with this.

[ptiurin]

This is now fixed in firebolt-sdk 1.15.0

[Antonio-RiveroMartnez]

Awesome @ptiurin! Truly appreciated, thanks