mirror of
https://github.com/google/skills.git
synced 2026-09-14 20:00:20 +08:00
Cloud IX Team
d9ed0bd5c4
On some clients the Developer Knowledge MCP server does not connect at all, and the skill did not describe the situation its users are actually in. The connection failure is structural rather than a misconfiguration. The Claude-facing manifest declares the server with no auth method, so the client follows the MCP authorization spec, discovers the protected-resource metadata, and is pointed at Google as the authorization server. Completing that handshake without a pre-registered client requires dynamic client registration, and Google's discovery documents advertise no registration endpoint. The client cannot mint an identity, the handshake ends, and no answer_query, search_documents or get_documents tool is ever exposed. The skill previously said a declared tool might return an error. The tools are not there to return one. The REST fallback is therefore the only transport on those clients, and the skill documented it as needing an API key. It does not. The v1 REST API accepts an ordinary Google bearer token, so anyone with an authenticated gcloud has a working path already and needs nothing installed or configured. That form is now shown first, with the API key kept as the alternative, and the REST fallback reference is reordered to match so the two do not disagree. Where a bearer token is refused, the note explains that the application-default credential often succeeds where the account credential does not, because which one the API accepts depends on how the environment was authenticated. A verification step also now sits between retrieval and output. The skill told an agent to answer immediately upon receiving the documentation response, without checking that what came back was documentation. PERMISSION_DENIED, UNAUTHENTICATED, HTTP 401 or 403, an empty result set, or any error payload is a failed lookup even when the tool reported no error. On a failure the agent tries the other transport once, and if that also fails it says it could not reach Developer Knowledge and is answering without it. PiperOrigin-RevId: 974811356