Create a subclass of MCPToolset to simplify connections to Google Managed MCP servers

[slilichenko]

Base MCPToolset can be tricky to configure when connecting to the newly announced Google Managed MCP servers. The primary complexity is the need to dynamically refresh authentication token obtained using the default application credentials. While it can be done using header provider, this feature is not documented is not well known. Also, incapsulating the actual URLs of the MCP servers can improve usability of the toolset. For example,

bigquery_toolset = GoogleManagedMCPToolset(Product.BigQuery)

would be all that's needed to access the default BigQuery toolset in production environment (deployed on a managed GKE/CloudRun/Agent Engine). Obviously, additional parameters might be needed to configure/filter the tools, but the complexity of authentication and access would be hidden from the developer. It should also simplify integration of with the UI-based Agent Builder (no need to configure complex auth providers).

[saifxyzyz]

Hey @slilichenko , can I work on this?

[llalitkumarrr]

Hello @slilichenko ,

Thank you for raising this issue, we appreciate your inputs.

Hello @saifxyzyz ,

If you have the time, would you be open to submitting a pull request? We highly value community contributions.