Yuan

@domdomegg Yeap! Here's the image identifier: us-central1-docker.pkg.dev/database-toolbox/toolbox/toolbox:latest @rdimitrov Yes, our image is in a registry that allow read from `allUsers`. And yes, it shouldn't need any authentication to access the...

Hi @tuannvm Thanks for submitting this proposal!! :) Let's try to discuss how this might look like~ Here are some initial thought -- 1. We are thinking of adding the...

> We are thinking of adding the mcp-server as a new source instead. For example: > > Yes, in that mode, genai-toolbox has to act as an MCP client; hence...

@wagnerjt We welcome open source contributors for this feature once an implementation is finalized. Let's see if we hear back from @tuannvm :) MCP just released their official [go-sdk](https://github.com/modelcontextprotocol/go-sdk). We...

@tuannvm > per my understanding on the discussion the next action items would be: > > * Configurable connection to multiple remote MCP servers > * Dynamic fetching and merging...

@wagnerjt > [@Yuan325](https://github.com/Yuan325) > > Using `go-sdk` sounds good to me and I can start off with one of the transports that the go-sdk supports and run with that. Your...

@wagnerjt > I am running with your tool flow suggestion. And will keep the tool name as-is. We can extend upon this with other feedback. (a) conflict between local Toolbox's...

@wagnerjt Sounds good, thank you! Sorry it's taking awhile to review your PR. I'll get back to you tomorrow on the draft PR once discussed with my team regarding implementing...

Hi @wagnerjt ! :) The source structs that are defined in the PR looks good. However, there are some further thoughts that needs to be finalized for tools retrieved from...

@wagnerjt The main motivation for opt 1 is incase user wants to remove a certain parameter. In that case, it will be either (1) specify no params - Toolbox will...