fix(mcp): require Google Drive OAuth client credentials and real login

[nehaprasad-dev]

What does this PR do?

• Fixes Google Drive MCP OAuth: require client_id/client_secret, real login via tool call, fail fast instead of 120s timeout.

Related Issue

• Fixes [Bug]: Official MCP server for Google Drive authenticates successfully, then always times out for any tool #34775

Type of Change

• Bug fix

Changes Made

• Validate Drive MCP OAuth config (tools/mcp_oauth.py, mcp_oauth_manager.py)
• Login runs authenticated probe + checks tokens (hermes_cli/mcp_config.py)
• Fast auth errors on tool calls (tools/mcp_tool.py)

Tests

How to Test

• Config: auth: oauth + oauth.client_id / client_secret for https://drivemcp.googleapis.com/mcp/v1
• hermes mcp login → browser OAuth, tokens in ~/.hermes/mcp-tokens/
• Use a Drive MCP tool — no timeout

Checklist

Code

• Contributing Guide read
• Conventional Commits
• No duplicate PR

Only related changes

Full pytest tests/ -q

Tests added

Platform tested: Ubuntu WSL
Documentation & Housekeeping

Docs — N/A

cli-config.yaml.example — N/A

CONTRIBUTING.md / AGENTS.md — N/A

Cross-platform — N/A

Tool schemas — N/A

Screenshots / Logs

Optional: login without URL vs with credentials; tool call success vs old timeout.

[teknium1]

Thanks for the focused Google Drive MCP investigation. This is an automated hermes-sweeper review; current main already implements the reported behavioral fix.

• 27a2c4f36ff323e5edc300496d001e28a0c35678 (fix(mcp): stop reporting false OAuth success when no token was obtained, shipped in v2026.6.5) fixed [Bug]: Official MCP server for Google Drive authenticates successfully, then always times out for any tool #34775.
• hermes_cli/mcp_config.py:803 verifies a token was persisted after the OAuth probe; a tools-list-only response without a token now reports that authentication did not complete and shows the pre-registered oauth.client_id / oauth.client_secret configuration.
• tests/hermes_cli/test_mcp_config.py:857 covers the exact Google Drive case: tools can be listed without auth, but login must not report success.
• The related issue's maintainer resolution also records PR fix(mcp): stop reporting false OAuth success when no token was obtained #34807 / commit 27a2c4f3 as the fix.

Closing as implemented on main.