anthropics / anthropics/claude-ai-mcp
[BUG] Google Compute Engine
- Lingua principale
- Nessun dato sulla lingua
- Stelle
- 471
- Fork
- 76
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
### MCP server URL or name
Google Compute Engine
### How are you connecting to this server?
From browsing the MCP server directory
### Where does the issue occur?
When pressing the Connect button
### When did you last reproduce this?
2026-09-02, 6:57 AM EDT
### Browser and OS
Reproduced via claude.ai. Tried on Samsung Internet (Android phone) and Safari (iPad) — same "Failed to start MCP authorization" error on both browsers and both devices.
### Describe the issue
The Google Compute Engine connector fails to authorize. Current error shown: "Failed to start MCP authorization" (toast notification, no error ID displayed, tapping the message does not reveal further detail). Reproducible and persistent, connector currently unusable. The Google Cloud BigQuery connector produces the identical error and was filed as a separate issue per this repo's guidance.Previously reported at anthropics/claude-code#90669 under a different error description (redirect_uri_mismatch, Error 400), closed by the github-actions bot as out of scope for that repo ("this doesn't appear to be about Claude Code"). Not clear whether the underlying issue changed since that report or the same root cause is now surfacing with different error text. Refiling here per that repo's guidance pointing MCP/connector issues to claude-ai-mcp.
### Error details
```shell
"Failed to start MCP authorization" — no error ID shown, tapping it does nothing.
```
### Expected behavior
Successful OAuth completion and a working connection to the Google Cloud BigQuery and Google Compute Engine connectors.
### Additional context
Prior report: https://github.com/anthropics/claude-code/issues/90669 (closed without review, wrong repo). Companion issue: BigQuery
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Valutazione
Questa issue non è ancora stata valutata.