connect-external-oauth

Connects Google OAuth to Hermes MCP via a local proxy server.

Updated Aug 21, 2026
One-click install
npx skills add https://github.com/TylerSimons1127/vibe --skill connect-external-oauth-tylersimons1127
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: connect-external-oauth
Source: https://github.com/TylerSimons1127/vibe/tree/main/skills/software-development/connect-external-oauth
Command: npx skills add https://github.com/TylerSimons1127/vibe --skill connect-external-oauth-tylersimons1127

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gmail-mcp, and includes references (resource) components.

What problem does it solve? Hermes's hosted MCP OAuth login for Google services stalls or fails because Google's hosted endpoints do not expose RFC 9728 OAuth metadata, and on Windows the browser auto-open call can block forever, leaving the flow frozen at "Starting OAuth flow...". ## Core Features & Use Cases - Local OAuth-proxy MCP server: Runs the gmail-mcp npm package on localhost so Hermes discovery succeeds and consent redirects work with any redirect URI. - Windows hang workaround: Uses the SSH_CLIENT environment variable to force headless mode so the auth URL prints instead of blocking on webbrowser.open(). - Zombie server detection: Verifies the live server's actual client_id via curl to catch stale processes answering with corrupted credentials. - Use Case: You want Hermes to read and send Gmail through MCP tools, but hermes mcp login gmail freezes; this Skill walks you through standing up the local proxy, configuring the Google Cloud OAuth client, and completing consent. ## Quick Start Ask the agent to connect Gmail to Hermes MCP by starting the local gmail-mcp proxy server and running the login command with SSH_CLIENT set.

Frequently Asked Questions about connect-external-oauth

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect Gmail to Hermes MCP when login freezes?▼

Run a local gmail-mcp proxy server on localhost that advertises its own OAuth metadata, then point Hermes config at http://127.0.0.1:8080/mcp. Set SSH_CLIENT before running hermes mcp login so the auth URL prints instead of blocking on browser auto-open.

Why does hermes mcp login fail with no OAuth token obtained?▼

Google's hosted Gmail MCP endpoint does not expose RFC 9728 OAuth metadata, so Hermes discovery aborts before any browser opens. A local gmail-mcp server serving .well-known/oauth-authorization-server on localhost fixes discovery.

What Google Cloud setup is required for Gmail MCP OAuth?▼

Create an OAuth Web client, add http://127.0.0.1:8080/callback as an authorized redirect URI, and enable the Gmail API. In Testing publish status, every consenting Google account must be added as a Test user or consent fails with Access blocked.

Why do I get Error 401 invalid_client during Gmail OAuth?▼

A stale node process from an earlier launch may be answering on the port with a truncated or corrupted client_id. Kill all node processes, confirm the port is free with netstat, restart the server, and verify the live client_id with a curl request to the authorize endpoint.

Can I access Gmail without completing the OAuth consent flow?▼

Yes, the Himalaya CLI v2.1.0 authenticates with a Gmail app password instead of OAuth, requiring only 2-Step Verification on the account. It provides CLI commands for reading and sending mail rather than MCP tools.

Why does hermes mcp login say server gmail not found in config?▼

The command defaults to the default profile while the Gmail config lives in the chat profile, usually vibe. Run hermes --profile vibe mcp login gmail so it reads the correct config.yaml.