The Fleece AI Brain Google Calendar connector syncs the events from every calendar in your connected Google account — title, description, start and end times, and the calendar they belong to — into a local-first knowledge base of plain Markdown and SQLite on your own machine. Recurring meetings are expanded into individual occurrences, and each event keeps a link back to Google Calendar. From there, any MCP-compatible AI app such as Claude Desktop or Cursor can read your real schedule history, with the source one click away.
What syncs from Google Calendar
Everything comes in as knowledge nodes — ordinary files you can open, link and search, not rows locked in someone else's cloud.
Events from every calendar
The connector reads your Google calendar list and pulls events from each calendar it contains, so shared and subscribed calendars sync alongside your primary one.
Titles, descriptions and times
Each event becomes a note titled by its summary, with the description, start and end times, and the source calendar name written into the body.
Recurring meetings, expanded
Repeating events sync as individual occurrences, so a weekly standup appears as each real instance rather than one abstract rule.
A link back to the source
Every event keeps its Google Calendar link, so the original is always one click from the note.
Incremental updates
Sync resumes from a per-account cursor, so each run only fetches events created or changed since the last one.
Built-in deduplication
A seen-ledger means a re-sync updates the existing note instead of creating a duplicate.
Connect Google Calendar in four steps
No IT project, no webhook plumbing — one sign-in from the desktop app.
- 01
Install Fleece AI Brain
Download the desktop app for macOS, Windows or Linux and open your vault — a folder of plain Markdown files on your machine.
- 02
Open Connectors and pick Google Calendar
In the app, open the connectors panel, choose Google Calendar, and sign in with your Google account. OAuth is brokered securely; the raw event content never transits Fleece's servers.
- 03
Choose which account to connect
The connector reads the calendars in the Google account you connect. Sign in with the account whose schedule you want remembered, and leave the rest out.
- 04
Let it sync — then ask
Sync runs in the background and stays up to date. Point Claude Desktop, Cursor or any MCP app at your Brain and ask when a decision was made or how long a project actually took.
Your calendar knows who decided what. Nothing can read it.
Your calendar is the most precise record your company keeps of its own history. Every decision had a meeting; every meeting has a subject, a time and a place in the sequence. Read end to end, your events are a chronology of how the organization actually ran — when the scope changed, which week the launch really slipped, how long the deal took from first call to signature.
But nothing can read that chronology. Calendars are built to answer "what's next", not "what happened" — search is thin, history scrolls out of reach, and the moment a quarter closes the record is effectively unreadable. The Google Calendar connector turns each event — its title, description and timing — into notes in one living knowledge graph, linked to the people and projects they mention.
Your events go from Google to your disk.
Authentication is a standard OAuth sign-in, but the sync itself calls the Google Calendar API from the desktop app on your machine, and the events land straight in your vault as Markdown and SQLite. When a managed sign-in can't hand the app a direct token, the request is proxied — but the raw event content never transits Fleece's own servers.
That is the trust model: the files are yours, they open in Obsidian or any editor, and if you ever leave you take the whole timeline with you.
- +Sync runs from your machine — raw event content never transits Fleece's servers
- +Vault = plain .md files + SQLite, 100% Obsidian-compatible, with full CRDT history
- +Works offline once synced; end-to-end-encrypted cloud sync is optional
Give every AI app your calendar's memory.
One copy-paste connects the Brain to Claude Desktop, Cursor, Cline, Zed or agents you build. From then on, "when did the pricing conversation with this account start, and what came out of it?" is answered from the actual events — with the source note one click away.
Because the Brain searches locally on meaning and exact words at once, a vague question ("the kickoff sometime in spring") and a precise one ("the review on the 14th") both land. On Teams, the organization map also shows which agents drew on that history and what they cost.
Google Calendar connector — FAQ
Does my calendar data pass through Fleece's servers?+
Sign-in uses a brokered OAuth flow, and the sync calls the Google Calendar API from the desktop app on your machine. When a managed sign-in can't expose a direct token the call is proxied, but the raw event content never transits Fleece's own servers — events land straight in your local vault, which we never see or store.
Which calendars and events does it sync, and how do I limit it?+
The connector reads every calendar in the Google account you connect and syncs their events. You scope it by choosing which account to sign in with — connect the account whose schedule you want remembered, and hide or remove any calendars you don't want from your Google calendar list before syncing.
Does it write anything back to my calendar?+
No. The connector is read-only: it pulls events into your knowledge base and never creates, edits, moves or deletes anything in Google Calendar.
How often does it sync?+
Sync runs in the background from the desktop app and resumes from where it left off, so each run only fetches events created or changed since the last one. Re-syncs update existing notes rather than creating duplicates.
Which plan do I need to connect Google Calendar?+
The local brain is free, and connectors are the paid lever: Solo (€12/month) includes up to 3 connected tools, Pro (€24/month) makes them unlimited with auto-sync. Every plan starts with a 14-day trial, no card required.
How do I ask Claude or Cursor about my schedule?+
Connect the Brain to Claude Desktop, Cursor or any MCP-compatible app with a single copy-paste. Your AI then answers from the synced calendar history, citing the exact event note it drew from.
Can I open the synced events outside the app?+
Yes. Every event is an ordinary Markdown file in your vault, fully Obsidian-compatible — open, edit or grep them with any tool, and take them with you if you ever leave.
What happens if I disconnect Google Calendar?+
Sync stops, and everything already in your vault stays yours — the notes are local files, not a mirror that vanishes with the connection.
Turn your calendar into company memory.
Connect Google Calendar in one sign-in and give your whole AI stack a readable chronology of what your company decided, and when.