NousResearch/hermes-agent

Google Drive MCP OAuth login and timeout problems

Cluster 34775 · mcp. Data as of 2026-10-28 11:56 UTC

Nothing open on GitHub. Fix merged in #34807 on 29 May 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #34807. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #34807. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #34807, then check it covers your case.

Read #34807 Pick up a Lab task

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.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#34807 fix(mcp): stop reporting false OAuth success when no token was obtained

merged to main

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

1 PR closed without merging

From the close comments: done elsewhere 1

#34787 fix(mcp): require Google Drive OAuth client credentials and real login · done elsewhere → 27a2c4f, #34775, #34807

Closed issues · 1

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

How this cluster was grouped

Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
Pairwise link density 0.67: the share of item 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.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem: mcp
Merged PRs: #34807
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 29 May 2026

For your agent

The same facts, typed.

cluster/34775.json
cluster/34775.md