From 0f3e29ab8d2cd48e004d55e5b947702298f24671 Mon Sep 17 00:00:00 2001 From: Alexey Martemyanov Date: Sat, 16 May 2026 02:18:36 +0600 Subject: [PATCH] =?UTF-8?q?[2026-05-16]=20wiki-curation:=20triage=20vault?= =?UTF-8?q?=20root=20=E2=80=94=201=20file=20moved?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- Hermes calendar access.md | 1 - .../personal-os/hermes-calendar-access.md | 34 +++++++++++++++++++ 2 files changed, 34 insertions(+), 1 deletion(-) delete mode 100644 Hermes calendar access.md create mode 100644 personal/projects/personal-os/hermes-calendar-access.md diff --git a/Hermes calendar access.md b/Hermes calendar access.md deleted file mode 100644 index fa059e05..00000000 --- a/Hermes calendar access.md +++ /dev/null @@ -1 +0,0 @@ -Добавить поддержку календаря к hermes с отдельным google oauth scope diff --git a/personal/projects/personal-os/hermes-calendar-access.md b/personal/projects/personal-os/hermes-calendar-access.md new file mode 100644 index 00000000..ff842bbd --- /dev/null +++ b/personal/projects/personal-os/hermes-calendar-access.md @@ -0,0 +1,34 @@ +--- +tags: + - hermes + - ideas + - personal-os + - google-calendar +created: 2026-05-16 +--- + +# Hermes — Google Calendar Access + +Idea: add Google Calendar support to Hermes as a separate OAuth scope. + +## Idea + +Add calendar MCP connector or tool to Hermes so agents (Eagle, Kraken) can: +- Read upcoming events for context (morning brief, daily planning) +- Potentially create/update events + +## Approach + +Separate Google OAuth scope for calendar access — distinct from any existing Google auth. +Likely via a calendar MCP server or Hermes plugin. + +## Status + +- [ ] Research available Google Calendar MCP servers +- [ ] Decide scope: read-only vs read-write +- [ ] Add to Eagle's MCP config + +## References + +- [[hermes-calendar-access]] (this file) +- See also: `personal-os-architecture.md` (Eagle MCP servers section)