Audit standing meetings before an AI agent moves them

A full calendar is a ledger of unreviewed choices

A full week shows up in the recurring invites nobody reviews. Each standing block is a recurring charge: meeting hours, attention, and the assumption that the meeting still earns its slot. If you are weighing an AI agent that can read and move your schedule, start with the debt, not the automation.

Google Calendar's Model Context Protocol (MCP) server, a connector for AI tools, is in developer preview and lets AI agents securely read a user's schedule and create, update, or delete calendar events. That capability is useful only if the calendar already contains meetings worth protecting.

Before any agent touches a recurring invite, ask the same question: What decision or outcome does this meeting protect, and who owns it? If the answer is blank, the invite is a recurring block with no purpose.

One question sorts keep, cut, and async

Run the audit on every standing meeting, not just the obvious ones. The question forces a choice: keep the meeting, cut it, or convert it to async. A manager with a full calendar can usually tell the difference in the same review, but the habit is what matters.

The answer should name a decision, a deadline, a dependency, or an owner. A label that only says the group is syncing does not name an outcome. A meeting that protects a decision, deadline, or dependency passes. If the meeting exists to keep a relationship warm, say so and decide whether that is worth the recurring cost.

Ownership is the part most calendars skip. A meeting without an owner becomes a shared task, and shared tasks get renewed by default. If no one can say who is responsible for the outcome, the invite should not survive the audit.

Give the agent a narrow, visible mandate

Once the audit is done, the AI agent has a narrower role. It can move a meeting that has a clear owner and a clear reason. It should not invent a reason for a meeting that failed the test.

The practical question is who can reschedule meetings, and what an agent may delete. Google's Calendar MCP server uses OAuth 2.0 for authentication and authorization. A configured Google Calendar MCP client can check a user's schedule with the calendar.list_events tool. Those details define what the agent may see and do.

If you connect Claude, an AI assistant, to Google Calendar's remote MCP server, you need a Claude Enterprise, Pro, Max, or Team plan. That plan requirement is a small control, but the bigger control is your own list of meetings that deserve to be moved.

MCP hosts such as Google Antigravity can read, modify, and delete data in a user's Google Account when connected through the Google Calendar MCP server. Treat that access as a standing permission: grant it only after the calendar has been cleaned, and review it before expanding the agent's role.

A review of recurring meetings should happen before you grant automation. Automation permissions are easier to defend when the audit is visible. If an agent can move a meeting, the team should be able to see why the meeting was kept, cut, or converted. That visibility is what turns a full calendar into a managed one.

Graceful cancellation is a skill. The note should say the standing invite is being retired, name the owner, and point to the replacement channel. It should not ask for permission to stop a meeting that no one can justify. A short, direct message is easier to accept than a vague request for a quick sync.

Keep this checklist: each item is a test you can run on a single invite before you flag it for an agent to reschedule.

• Keep the meeting if it protects a named decision, and the owner can state the decision in a sentence.
• Cut the meeting if the outcome is only staying aligned, and no owner can name what changes after it.
• Convert to async if the work is status, review, or approval, and a written update would move the decision faster.
• Cancel gracefully by sending a short note: the meeting is being retired, the owner is named, and the replacement channel is stated.

Send the note, update the invite, and let the agent handle only the meetings that passed the audit.