It would be so that I can fall back to an earlier MCP version (or API) for those tools.
For example, Hubspot has a large list of tools that are not in v3, such as blogging tools and sequence enrollments which are working perfectly fine with the mcp v2, but are just not available in v3. So if I know which mcp they support, I can just dynamically render the best choice of mcp version for each app.
Yea, I think we should likely address that general need a bit differently — perhaps by expanding the set of supported tools for specific connectors you’re using, and/or by exposing additional capabilities in our MCP server like dynamic code generation based on what you’re trying to do.