Adding Multiple GitHub MCPs for Accessing Different Repositories

Hi Gregor. When you set up GitHub, you choose what repos it can access. Then, it comes down to prompting (either agent level or message level) to tell it which specific repo(s) to target. So a single GitHub connection is sufficient to satisfy many agents with different repo needs. Does that make sense?

sure, makes sense! I’ll try it that way

One thing I'm not entirely clear on is that the connection flow offers to connect either to everything you have access to (user level), or to a specific GitHub org. But how then would one connect to multiple orgs, without opening up to everything? Sébastien Flory maybe you can shine some light on this? Thanks!

Right now, multiple github tools can't be added. (same for all internal tools)

access to multiple orgs has never been requested so far.

Understood. One thing I noticed is that whether you choose Disconnect or Remove, the dust-agent on GitHub never gets removed from the org. And a small bug: if you modify the scope of an existing agent on GitHub, it correctly makes the change, but then gives "This URL was unexpectedly visited outside of the Dust Connections setup flow. Please close this window and try again from Dust." when the redirection happens. It's harmless since the change is effective, but quirky. I'm actually surprised that GitHub would even do the OAuth redirection when I'm just updating an existing agent from the GitHub UI.

David Ebbo I guess you'll have to fix these 🙂