email-mcp-access

Connect Gmail to Hermes via a local gmail-mcp OAuth proxy or Himalaya CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Google's hosted Gmail MCP endpoint does not advertise OAuth metadata, so Hermes's mcp login fails before any browser opens. This Skill provides two working routes to give Hermes full email access: a local gmail-mcp proxy that exposes proper OAuth metadata, and a Himalaya CLI fallback that bypasses OAuth entirely with an app password. ## Core Features & Use Cases - Local Gmail MCP Proxy Setup: Install and run domdomegg's gmail-mcp v2.4.0 with your own Google OAuth client, including the required redirect_port/redirect_host pin so the token exchange succeeds. - Google Cloud Console Guidance: Step-by-step OAuth consent screen, client creation, and test-user configuration, with documented workarounds for computer_use's inability to click Google Console widgets. - Himalaya CLI Fallback: A known-good v2.1.0 config using IMAP/SMTP with a 16-character Gmail app password when OAuth is blocked. - Use Case: You want your Hermes agent to read, search, and send Gmail. Follow Route A to stand up the local proxy, register the redirect URI in Google Cloud, run hermes mcp login gmail, and the token is saved for persistent email tool access. ## Quick Start Set up Gmail access for my Hermes agent using the local gmail-mcp proxy route, and fall back to Himalaya with an app password if OAuth consent is blocked.

Frequently Asked Questions about email-mcp-access

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

FAQPage Schema
How do I connect Gmail to Hermes via MCP?▼

Run domdomegg's gmail-mcp v2.4.0 locally with your Google OAuth client ID and secret, then point Hermes at http://127.0.0.1:8080/mcp with auth: oauth. Pin redirect_port: 8080 and redirect_host: 127.0.0.1 in the Hermes config so the callback matches the URI registered in Google Cloud.

Why does Hermes mcp login fail with the Google-hosted Gmail endpoint?▼

The hosted endpoint gmailmcp.googleapis.com does not advertise OAuth metadata (no RFC 9728 protected-resource document). Hermes aborts during metadata discovery before any browser opens, reporting that no OAuth token was obtained. Use a local gmail-mcp proxy instead.

How do I access Gmail without OAuth using Himalaya?▼

Himalaya authenticates with a 16-character Gmail app password over SASL PLAIN, bypassing OAuth entirely. Enable 2-Step Verification, generate an app password, and use the v2.1.0 config schema with imap.sasl.plain and smtp.sasl.plain keys; the old backend.host keys are rejected.

Why does Google consent return Error 403 access_denied?▼

While the OAuth app is in Testing status, only emails listed under OAuth consent screen, Audience, Test users can consent. Add your Gmail address as a test user in the Google Cloud Console to resolve the access_denied error.

Can computer_use click Google Cloud Console buttons?▼

No. Synthetic clicks via SendInput or PowerShell mouse_event reach the browser but not Google Console's GfElements handlers, so sign-in tiles, Add users, and dialog buttons never register. Navigate by deep-link URLs instead and have a human perform the final console clicks.