hermes-google-mcp

# hermes-google MCP server giving Hermes (Claude Code running as a personal assistant) scoped access to Gmail, Google Calendar, and Google Drive through a dedicated Hermes Google account — without granting access to your personal Google account. See [`docs/superpowers/specs/2026-04-23-hermes-google-design.md`](docs/superpowers/specs/2026-04-23-hermes-google-design.md) for the full design. ## Quick Start Add hermes-google to your project's `.mcp.json`: ```json { "mcpServers": { "hermes-google": { "type": "stdio", "command": "uvx", "args": ["hermes-google-mcp@latest"] } } } ``` ## Google Account Setup 1. Sign up for a plain Gmail account (e.g., `[email protected]`) 2. In [Google Cloud Console](https://console.cloud.google.com/): create a project, enable the Gmail, Calendar, and Drive APIs 3. Create an **OAuth 2.0 Client ID** (type: Desktop application) and download the client secret JSON 4. Save it as `~/.config/hermes-google/oauth_client.json` 5. Run the setup script: ```bash git clone https://github.com/jimmy-larsson/hermes-google.git cd hermes-google ./scripts/setup.sh ``` The setup script creates the config, runs the OAuth flow (saving the token to `~/.config/hermes-google/token.json`), and prints the remaining manual steps. ### Host-Side OAuth The OAuth flow opens a browser for consent — it must run on your host machine, not inside a headless container. If your config and credentials live inside a container (e.g. Docker-mounted `~/.config/hermes-google/`), you need to: 1. Copy `config.toml` and `oauth_client.json` to the **host** filesystem at `~/.config/hermes-google/` 2. Run the OAuth flow from the host: ```bash uvx hermes-google-mcp@latest auth login ``` 3. The resulting `token.json` is saved on the host — it will be picked up by the container through the volume mount ## Gmail Setup Create filters in your **personal** Gmail to route emails to the Hermes account: 1. For each sender you …