Hello @thatjeffsmith-oracle et. al.
When connecting to the sqlcl -mcp server, my code gives this WARNING:
Feb 25, 2026 10:58:00 AM io.modelcontextprotocol.server.McpAsyncServer$AsyncServerImpl lambda$asyncInitializeRequestHandler$5
INFO: Client initialize request - Protocol: 2025-11-25, Capabilities: ClientCapabilities[experimental=null, roots=null, sampling=null], Info: Implementation[name=mcp, version=0.1.0]
Feb 25, 2026 10:58:00 AM io.modelcontextprotocol.server.McpAsyncServer$AsyncServerImpl lambda$asyncInitializeRequestHandler$5
WARNING: Client requested unsupported protocol version: 2025-11-25, so the server will sugggest the 2024-11-05 version instead
Connected to internal SQLcl MCP server
Is that something we can expect to be addressed in future release of SQLCL? Can we expect a streamable-http protocol support as well? :)
Another question: Would you say that the sqlcl mcp server is a “production” ready tool, in the sense I should feel confident in deploying it as a part of an enterprise solution?
Cheers
Borkur