Read-Only Calendar Access for Fund Agents: A Connection Checklist

An agent needs meeting context to keep a deal board honest. It does not need permission to edit invitations. Before connecting a fund calendar, check the exact calendars it can read, whether its key can write, what happens to unrelated events, and how access stops. GPAgent applies those checks when a firm connects CalendarMCP to its Relationship Manager.

1. Decide which calendar connection owns the job. GPAgent uses its direct Google Calendar connection when present; CalendarMCP is optional.
2. In CalendarMCP, give the key read access to the calendars you intend to share and turn off Write for each of them.
3. In GPAgent's Integrations page, paste the key and inspect the live check before saving it.
4. Review the reported accounts and calendar count, then verify the exact calendar grants in CalendarMCP. A read-only key for the wrong calendar is still the wrong connection.
5. After connection, inspect agent activity and disconnect if the scope changes or the connection is no longer needed.

Start with the meeting you want on a deal card

A partner call is on the calendar, but the deal board still says the team has not met the company. That is the useful job for calendar access: reconcile a relevant meeting with an existing deal so the next review starts from what actually happened. It is not a license for an agent to accept invitations, move meetings, or copy the firm's whole schedule into a CRM.

GPAgent's Relationship Manager reads calendar events for that reconciliation. The calendar connection is one input to the workflow, not a command channel for the agent. The product's agentic investing team guide explains where that role fits among the other fund jobs.

Check before connecting	What to look for in GPAgent	Why it matters
Calendar scope	The live check names the accounts and counts the readable calendars	A valid key may cover more calendars than the firm meant to share
Write permission	A key that can change events is refused	Reading meeting context does not require changing invitations
Run-time permission	The key is checked again before each agent run	A later permission change cannot quietly turn an old approval into broader access
Unrelated meetings	Non-deal events are not stored as deal records; activity receipts keep counts, not their titles	A private appointment is not investment memory
Disconnect	GPAgent stops reads and deletes its stored copy of the key	The firm can stop this integration without erasing prior deal updates

Connect CalendarMCP without granting write access

For a firm using CalendarMCP, set the key's calendar permissions there first. In GPAgent, open Integrations, choose CalendarMCP, and paste that key. The connection sheet checks it live. It reports which accounts the key reaches and how many calendars are readable. If the key can write to any calendar, GPAgent refuses to save it and points you back to CalendarMCP to turn off Write. A key with no readable calendars is refused too.

Do not treat a successful check as the end of the review. Read the accounts and calendar count shown in the sheet, then inspect the exact calendar grants in CalendarMCP. If a partner's personal calendar should not be included, narrow the key at its source before connecting it. GPAgent accepts the key's granted read scope; it cannot infer which of those calendars the fund intended to share.

Direct Google Calendar is the default provider when both connections exist. CalendarMCP is the optional path for calendars connected there; connecting both does not make the Relationship Manager read from both by default. If you only need the direct fund calendar, you do not need a CalendarMCP key.

Check what happens after you connect

The permission check runs again when GPAgent opens the CalendarMCP connection for an agent run. If the key later gains write access, loses read access, or is rejected, that run does not read through it. The activity trail is where the fund checks whether the calendar job ran and what it did, not a claim that every meeting became a deal update.

Disconnecting CalendarMCP in GPAgent stops future reads and removes GPAgent's stored key. It does not revoke the key at CalendarMCP. Rotate it there if you want to retire the credential itself. Past deal updates remain, so review them separately if the original calendar scope was wrong.

If your team is evaluating an agentic fund workflow, see the GPAgent platform, then join the waitlist to tell us which calendar-to-deal handoff you need. The connection itself lives in the authenticated Integrations page, not in this public article.

FAQ

Can a GPAgent calendar connection change or answer invitations?

No. GPAgent's CalendarMCP path refuses a key with write access, and its calendar workflow reads events rather than changing invitations. It rechecks that permission before each run.

Will every calendar event become a deal note?

No. The reconciliation job uses meeting context to match relevant deals. Non-deal event titles are not kept in the activity receipt; the receipt records counts instead. A calendar connection is not a general-purpose schedule archive.

What if the key's permissions change later?

GPAgent checks the key again when the agent runs. A key that becomes writable or can no longer read a calendar is not used for that read. Fix the permissions in CalendarMCP, then reconnect or replace the key in GPAgent as needed.

Does disconnecting GPAgent revoke my CalendarMCP key?

No. It deletes GPAgent's copy and stops this integration's reads. Rotate the key in CalendarMCP if the credential itself should no longer work elsewhere.