✕ Error during discovery for server 'google-workspace': Connection failed for 'google-workspace': MCP error -32000: Connection closed

[jailbreakerSN]

Zfter installing this extension in my cloud shell terminal, got the following error:
✕ Error during discovery for server 'google-workspace': Connection failed for 'google-workspace': MCP error -32000: Connection close

[allenhutchison]

Thanks for the bug report. I'll take a look. Is this using the default version of gemini cli in cloud shell?

[jailbreakerSN]

Yes, it was while using the default Gemini cli

[crystalin]

I got the same error. I'm using gemini (personal account) cli locally

[drewgillson]

Same issue

[allenhutchison]

@crystalin and @drewgillson in your cases were you running gemini cli on a machine with a web browser? Did you see the auth flow open in your default browser?

[drewgillson]

@crystalin and @drewgillson in your cases were you running gemini cli on a machine with a web browser? Did you see the auth flow open in your default browser?

Yes, and I auth'd successfully.

[rockcop]

Ya I had this same issue - I had auth'd successfully. It was working on my machine but when I SSH it doesn't find it.

[crystalin]

I was also using gemini on my server through SSH (I auth on the server providing the code after login in on my local chrome)

[rockcop]

@crystalin i got this working by unlocking the keychain on my mac in the SSH session before starting up gemini ‘security unlock-keychain’

[crystalin]

I'm on ubuntu server, there is no keychain service. I have ssh-agent with key forwarding but that doesn't help

[allenhutchison]

I think there are a few issues here in this bug:

1. Provide a way to do headless authentication. The extension currently requires a web browser on the host the extension is running on to complete the oauth process. If you ssh into a server and you can't spawn a web browser, then you won't be able to log in. This work is tracked in Enable oauth flow in environments without web browser  #63

2. Unlocking your keychain when you ssh into a machine where you have previously authenticated. This may be limited to mac os but as @rockcop pointed out here: ✕ Error during discovery for server 'google-workspace': Connection failed for 'google-workspace': MCP error -32000: Connection closed #30 (comment) you may have to manually unlock the keychain on mac os to get to the auth token we store there for the extension.

3. Other issues? I'm not sure if there are other issues besides these two, but please let me know if you are seeing other things.

[crystalin]

Thanks for looking at it.

So you mean for 1. that it is not enough to open the link on a browser and write the code to the headless server ? When registering the extension it seems to have validated the auth, but I suspect there might be addition steps needed ?

[allenhutchison]

@crystalin that's right. The oauth exchange spawns a local server that your web browser gets redirected to, that server gets the credentials and then stores them in the secure storage for your OS. When you ssh into a host, even if you open the web on another machine, we current lack the mechanism to get the credentials back into the host you started on. That is the work I'm tracking in #63

[thedavil]

Same issue here. Enterprise Google account. I have a working browser etc. but no auth flow was launched ever.
Calls to core /auth work fine - they relaunch the web auth flow.

[allenhutchison]

@thedavil when you say that a call to core /auth worked ok, do you mean that you used the npm run auth-utils from the repo or that you used the auth.clear / auth.refreshToken in the MCP server? Or are you referring to the /auth command in Gemini CLI? If the latter there is no way for me to share the credential with Gemini CLI so you have to authenticate with the MCP server separately.