Hermes,
at your command.

Things to ask it

Just say it in the chat.

A few of the things Hermes can handle today. Phrase them naturally — it figures out which tool to reach for.

How to talk to it

A phrasing cheat-sheet.

You never need exact commands — but here’s the kind of thing each integration responds to.

Connected systems

Integrations matrix.

Every connected service, how it’s built, and its current status. Google services are in-house adapters over official Google APIs.

Under the hood

How it’s actually built.

Hermes runs as a small set of services on a private VPS. Every Google integration is an in-house adapter calling Google’s official APIs — no third-party connectors hold your data.

The shape of it

System architecture.

Messages flow in from WhatsApp or email, through the gateway to the GLM-5.1 agent, which reaches in-house MCP adapters that speak to each provider’s official API.

flowchart TD
  U["📱 You · WhatsApp / Email"] --> GW["Hermes Gateway
(systemd · allowlisted)"]
  GW --> AG["Hermes Agent
GLM-5.1 · persona · memory"]
  AG -. fallback / senses .-> AUX["Gemini · Groq Whisper
vision · STT · TTS"]
  AG --> MCP{{"MCP adapters (stdio)"}}
  subgraph INH["In-house adapters · official Google APIs"]
    CAL["gcal"]
    DRV["gdrive · Docs"]
    SHT["gsheets"]
    SLD["gslides"]
    TSK["gtasks"]
    CON["gcontacts"]
  end
  subgraph EXT["Other integrations"]
    CU["clickup"]
    C7["context7"]
    TV["Tavily"]
  end
  MCP --> INH
  MCP --> EXT
  INH --> GAPI["Google APIs
Calendar · Drive · Docs · Sheets · Slides · Tasks · People"]
  CU --> CUAPI["ClickUp API"]
  AUTH["gauth.py · 1 OAuth client
1 token · 0600 file"] -. credentials .-> INH

Trust & data

Security & privacy.

Plain-language account of where your data lives, what Hermes can touch, and how access is locked down.

• ◆
  Your data stays on your turf. Everything runs on your VPS and talks directly to your Google account. No third-party server sits in the middle holding your data.
• ◆
  Official auth, minimal scopes. One Google OAuth client with only the scopes each feature needs — Calendar, Drive, Docs, Sheets, Slides, Tasks, Contacts. Nothing broader.
• ◆
  One token, well guarded. A single refresh token in a 0600 file (owner-only) behind a shared helper. No secrets in the config file.
• ◆
  Locked to you. WhatsApp and email are allowlisted to your number and addresses — no one else can talk to it.
• ◆
  Auditable by design. The Google adapters are ~300 lines of our own code calling Google’s official libraries; you can read every line in ~/.hermes/custom-mcp/.
• ◆
  What it can’t do. No admin/Workspace powers, no access to other people’s accounts, and destructive ClickUp actions are deliberately excluded.
• ◆
  Recoverable. Weekly encrypted-at-rest backups of the whole setup; tokens are revocable and re-mintable at any time.

Keeping it running

Operations & recovery.

The handful of things worth knowing to run, watch, and recover Hermes.

Common questions

FAQ.

What's next

Roadmap & ideas.

Recently shipped, what's parked, and ideas worth exploring next.

✅ Recently shipped

💡 Ideas to explore next

Current limitations

• ▲
  Google Maps is parked — using free Maps-lite (OpenStreetMap) instead; Google's version needs billing.
• ▲
  Google Keep is unavailable — its API is Workspace-only and won't work with a personal account.
• ▲
  Unverified-app caps — the OAuth app is in production but unverified: a one-time consent warning and a 100-user cap (you're the only user).
• ▲
  Maps-lite is driving-only — OpenStreetMap routing covers car routes; walking/transit aren't wired yet.

History

Changelog.

How Hermes got here, by date.