Any interest in an MCP server companion (aisuite as MCP server, not just client)?

aisuite currently supports MCP as a client (calling out to external MCP servers as tool sources), but there doesn't seem to be a way to expose aisuite's own multi-provider routing as an MCP server, so that a client like Claude Cowork can call "ask any of these 21 providers" as a single tool.

I put together a small personal script that does this: one MCP tool, ask_language_model(provider, model, question), backed by aisuite.Client(), with credentials pulled from the OS keyring per provider. It's since been translated to English (was Dutch) and has a small test suite (33 tests, with CI), but it's still not packaged for distribution.

Before I'd consider polishing it into a real PR, I wanted to check: is there any interest in this from the maintainers, and if so, would it belong in this repo, or is a separate companion package (e.g. aisuite-mcp-server) the better shape?

One concrete reason to keep it separate: aisuite's own mcp extra pins mcp<2.0.0 (needed for the MCP client feature), while building an MCP server requires mcp>=2.0.0 (the MCPServer class only exists from 2.0 on). Bundling both into the same package would create an internal version conflict between aisuite's own extras.

Script for reference: https://github.com/Davidver1/aisuite-mcp-server

For context: I checked existing issues and pull requests first. #245 asks for the opposite direction (aisuite calling out to external MCP servers, which is already supported), and the open MCP pull requests (#302, #383) are all client-side as well. This issue is specifically about exposing aisuite's own routing as an MCP server, which doesn't seem to exist yet.