# NousResearch/hermes-agent · Google Drive MCP OAuth login and timeout problems

## Open now

- Nothing open on GitHub.

These members center on the Google Drive MCP server's OAuth login behavior: one bug report describes authentication appearing to succeed and then tool calls timing out, while two fix-titled changes concern requiring OAuth client credentials with a real login and avoiding false success reports when no token was obtained. The titles alone do not establish how the items relate causally or whether any issue has been closed out.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #34807. Verify it addresses your case.
- **Recommended:** read PR #34807 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-34807`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

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

## Prior & competing PRs

- **#34807: fix(mcp): stop reporting false OAuth success when no token was obtained**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_cli/mcp_config.py`, `tests/hermes_cli/test_mcp_config.py`, `website/docs/user-guide/features/code-execution.md`, `website/docs/user-guide/features/mcp.md`
- **#34787: fix(mcp): require Google Drive OAuth client credentials and real login**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `27a2c4f36ff323e5edc300496d001e28a0c35678`, `#34775`, `#34807`

## Fix status

- Merged to main in PR #34807 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-05-29`.
- Subsystem: `mcp`