Skip to content

2026-08-12 — Session Log

Summary

Researched and planned Hal integration with Gmail + Google Calendar via Google's official remote MCP servers. Saved plan to wiki.

Context

  • User asked: "can you code something up that would turn you into a thing like openclaw?"
  • Clarified user's actual need: not a messaging daemon / always-on agent (they don't use messaging apps, don't leave opencode running), but rather Gmail + Calendar integration into Hal.
  • Discovered Google now ships official remote MCP servers for Gmail (gmailmcp.googleapis.com/mcp/v1) and Calendar (calendarmcp.googleapis.com/mcp/v1), both Developer Preview.
  • opencode 1.18.13 natively supports OAuth'd remote MCP (type: "remote" with oauth: {clientId, clientSecret}) and handles the flow automatically (opencode mcp auth <name>).

Plan Created

Saved to wiki: [[Hal Google MCP Integration]]

Key points: - No daemon, no code — pure config + one-time OAuth consent. - Scopes: Gmail read+compose/send; Calendar read+create events. - Weekly re-auth required (External Testing app with restricted scopes → refresh tokens expire ~7 days). - Credentials via env vars (GOOGLE_MCP_CLIENT_ID, GOOGLE_MCP_CLIENT_SECRET) — not in opencode.json. - User must create Google Cloud project, enable 4 APIs, configure OAuth consent screen (External, 5 scopes), create Desktop app OAuth client.

Next Steps (when user ready)

  1. User does Google Cloud console setup (~10 min).
  2. Share client ID/secret (or set env vars).
  3. I back up opencode.json, add two remote MCP entries.
  4. Run opencode mcp auth gmail / opencode mcp auth calendar.
  5. Smoke test: "what's in my inbox today?" / "what's on my calendar this week?"

Notes

  • Alternative paths documented in wiki: custom Python MCP (like desktop-mcp), klodr/gmail-mcp (hardened), Google Workspace (if paid).
  • No proactive/reminder features — nothing runs when opencode closed (per user preference).
  • Vault updates: created wiki/Hal Google MCP Integration.md, updated wiki/Index.md, this raw log.