RFD 0221: MCP Gateway#57882
Conversation
gabrielcorado
added
no-changelog
gabrielcorado
requested review from
greedy52,
klizhentas,
kurktchiev and
r0mant
| additional connect option for supported databases. By clicking it, they will | ||
| enable the server on the gateway. | ||
|
|
||
| <img width="871" alt="Unified Resources view in Connect with MCP support" src="assets/0221-resources-view.png"> |
There was a problem hiding this comment.
Nitpicking here, but instead of using the App icons as the main icon of the MCP and the MCP icon as a subheader, can we just use the MCP as the new icon type for them? Using the sub icon, for example, to indicate that a DB is MCP compatible, makes sense. From a UX perspective, I would want to be able to quickly visually parse MCPs in a list of available resources to me.
| The MCP Gateway remains a permanent fixture in the UI within the connection | ||
| list at the top left. | ||
|
|
||
| <img width="871" alt="Connections view in Connect with MCP option" src="assets/0221-connections.png"> |
There was a problem hiding this comment.
What is the UX if I click on the DB Connect button outside of this flow? Do I see a separate MCP connect section?
There was a problem hiding this comment.
We'll present a dialog with the connect options, similar to the one from the database WebUI connect flow.
Web UI reference
I'll add a section to cover this use.
| logging in to a different cluster or computer will automatically update the | ||
| gateway configuration. | ||
|
|
||
| ### `tsh` |
There was a problem hiding this comment.
What is the debug story for our CLI experience?
3 participants
Rendered
Related to #57094
Note
Currently, the RFD only includes the UX section. The other details are being worked and should be updated soon.