Turn "Let's Meet Next Week" into a Real Calendar Invite with SuperIntern MCP and Google Calendar
Every meeting ends the same way: "Great discussion, let's regroup next week." Everyone nods. Nobody sends the invite.
Three days later someone posts in the channel: "Did we ever schedule that follow-up?" Now you are digging through your notes to remember what the next session was even supposed to cover, guessing at a time that works, and writing an agenda from memory. The information you need exists: the decisions, the open items, the owners are all sitting in your meeting notes. The invite just never wrote itself.
Until now, that is. In this article we connect SuperIntern's MCP and Google Calendar to Claude, and turn "let's meet next week" into a scheduled event with a real agenda, in one prompt. We will also use the same wiring for a pre-meeting briefing and a weekly focus-time sweep.
⚠️ This article was independently compiled based on publicly available information and user feedback as of August 2026.
Table of contents
- What we're building: before / after
- How it works: three roles
- Setup
- Demo 1: the follow-up invite, minutes after the meeting
- Demo 2: a briefing before tomorrow's meetings
- Demo 3: a Friday sweep that blocks focus time for next week
- Tips and caveats
- Going further: the same pattern, other tools
- FAQ
What we're building: before / after
Before: After each meeting, scheduling the follow-up is a chore made of four small chores: reread the notes, figure out what the next session should cover, find a slot, write the agenda. So it slips. The follow-up gets scheduled late, without an agenda, or not at all.
After: You ask Claude once: "We agreed to meet again next week. Draft the invite." Claude pulls the meeting summary through SuperIntern MCP, extracts the decisions and open items, checks your calendar for openings, and shows you a complete event draft: title, attendees, time, and a description that doubles as the agenda. You review it, say "go", and the invite lands in everyone's inbox.
Two design points make this trustworthy. First, SuperIntern records your meetings botless, from a desktop app, so the notes the agenda is built from exist for every meeting, including external calls where you would never get a recording bot approved. Second, the calendar write only happens after you approve the draft. Claude proposes; you confirm; the invite goes out. Sending a calendar invite notifies real people, so we keep a human in that loop on purpose.
How it works: three roles
| Role | Player | What it does |
|---|---|---|
| Meeting data | SuperIntern MCP | Serves transcripts, AI summaries, and meeting notes, read-only |
| Judgment and drafting | Claude (AI client) | Extracts decisions and open items, checks availability, drafts the event |
| Action target | Google Calendar (connector) | Creates and updates calendar events, manages invites |
MCP (Model Context Protocol) is an open standard for connecting AI assistants to external tools safely. SuperIntern's MCP hands your meeting data to the AI client read-only. The calendar side is Claude's official Google Calendar connector, which can check availability, create events, update them, and RSVP.
Note who does what: the event is created by Claude through the Google Calendar connector, not by SuperIntern. SuperIntern never writes to your calendar, and nothing can write back into SuperIntern; the MCP has no write operations at all. Claude can only read the meetings you can see in SuperIntern yourself.
Setup
Two connections, no API keys. Both are done from a login screen.
1. Connect SuperIntern MCP to Claude
In Claude, go to Settings, then Connectors, choose "Add custom connector", and register this URL:
https://mcp.app.super-intern.com/mcp
A SuperIntern login screen opens; sign in and approve. Plan requirements (Plus or higher for personal workspaces, admin enablement on Enterprise) and setup steps for other clients like Claude Code and Cursor are covered in our MCP setup guide.
2. Connect Google Calendar to Claude
Add the Google Calendar connector from Claude's connector settings and authenticate with your Google account. See the official help article for current availability and plan details.
To confirm both sides are live, ask:
List my 3 most recent SuperIntern meetings,
and my calendar events for tomorrow
If both come back, you are ready.
Demo 1: the follow-up invite, minutes after the meeting
The highest-value moment is right after a meeting where someone said "let's do this again next week." While the summary is fresh in SuperIntern, ask:
Get the AI summary of today's "Acme rollout planning" meeting.
We agreed to meet again next week. Find a free 45-minute slot
on my calendar next Tue-Thu afternoon and draft a follow-up event:
same attendees as today, and a description with three sections:
1) what we decided today, 2) open items with owners and due dates,
3) proposed agenda for the follow-up.
Show me the draft first. Only create it after I say go.
Claude reads the summary, picks a slot, and comes back with something like this:
Draft: Acme rollout, follow-up Thu, Aug 27, 2:00 to 2:45 PM, with sara@, ken@, tanaka@acme.com
Decided today: pilot starts with the CS team (10 seats, 2 weeks); SSO is a launch requirement. Open items: security questionnaire back to Acme by Aug 21 (Sara); sandbox access for Acme IT (Ken). Proposed agenda: pilot kickoff logistics, security review status, rollout timeline draft.
Reply "go" and I will create the event and send the invites.
You reply "go", and the invite is on everyone's calendar, agenda included.
The difference from writing this by hand is not just the five minutes saved. The agenda is grounded in the actual summary, so the next meeting starts from what was really decided, not from what the organizer half-remembered a week later.
Demo 2: a briefing before tomorrow's meetings
The same wiring runs in the opposite direction: instead of the meeting feeding the calendar, the calendar tells Claude which meetings to prepare you for. The evening before, or with your morning coffee, ask:
Look at my calendar for tomorrow. For each external meeting,
search my SuperIntern meetings for past conversations
with the same people, and brief me: key points from the last
conversation, anything we promised them, open items still pending.
Flag any promise that looks overdue.
Claude cross-references tomorrow's attendees against your meeting history and returns a briefing:
10:00 Acme, pilot check-in (last met Aug 13) You promised the security questionnaire by Aug 21: due in 4 days, in progress. Acme's IT lead asked about SAML certificate rotation; Ken took it as homework. No answer recorded yet.
2:00 Northwind, intro call (first meeting, no history) No prior conversations found. Sara met their VP Ops at the June webinar per the "Partner outreach" notes.
This is the fastest version of the ritual every account manager already does by scrolling through old notes. Here it takes one prompt, and it never misses a meeting because the calendar itself is the checklist.
Demo 3: a Friday sweep that blocks focus time for next week
Action items die in the gap between "assigned in a meeting" and "scheduled as actual work time". On Friday afternoon, close that gap for the whole week at once:
List this week's meetings and pull each AI summary.
Collect every action item assigned to me, with due dates.
Then find free slots on my calendar next week and propose
focus blocks to get them done, one block per theme,
scheduled before each deadline. Show me the plan;
create the blocks I approve as private events,
with the task list in the description.
Claude aggregates your homework across every meeting of the week, then turns it into concrete blocks:
Found 7 action items assigned to you across 5 meetings.
- Mon 9:00 to 10:30, "Security questionnaire" (due Wed): from Acme pilot check-in
- Tue 2:00 to 3:00, "Q3 pricing draft" (due Thu): from pricing sync, includes the two open questions from the transcript
- Thu 9:00 to 9:45, "Interview feedback" (due Fri): from the two candidate debriefs
Approve all three?
These are private solo events, no attendees, so this variation is zero-risk to run weekly. The point is structural: commitments made out loud in meetings become time on your calendar before they can evaporate.
Tips and caveats
Keep the confirm-before-create step. Unlike an email draft that sits harmlessly in a folder, a calendar event with attendees sends real notifications the moment it is created. Ending every scheduling prompt with "show me the draft first, create only after I say go" is the one habit that makes this workflow safe to use daily. For solo focus blocks (Demo 3), you can relax this.
Double-check external attendees. Claude fills in attendees from the meeting record, which is exactly why you should glance at the list before saying go. The wrong-guest-on-the-invite failure mode is rare but expensive.
Fix the description structure in your prompt. "Decided / open items / agenda" as three labeled sections makes every invite you send look the same, and makes the output stable enough to trust. Prompts that work well are worth saving as team snippets.
Let the transcript keep the agenda honest. If a topic is contested, ask Claude to quote the transcript for each "decided" item. The agenda then reflects what was actually said, which is the whole point of building it from a primary source.
Feed SuperIntern good names. The cleaner the meeting titles and the more consistently attendee names and product names are transcribed, the better the cross-referencing in Demos 2 and 3 works. Registering frequent proper nouns in SuperIntern's custom dictionary pays off here.
Writes touch only your calendar. SuperIntern data cannot be modified through the MCP. If a draft event is wrong, you throw it away or delete the event; your meeting record is untouched either way.
Going further: the same pattern, other tools
"SuperIntern MCP provides the data, Claude decides, another tool receives the action" is a pattern that extends well beyond scheduling:
- Gmail: draft the follow-up email from the same meeting notes. We covered it in the Gmail edition of this series
- CRM: log the meeting outcome to the deal record. See the HubSpot edition
- Slack: post the recap to the team channel while the meeting is still running. See the Slack edition
A natural combo: one prompt that schedules the follow-up (this article) and drafts the recap email (Gmail edition) from the same summary.
FAQ
Q. Is SuperIntern MCP available on the free plan?
A. No. Personal workspaces need the Plus plan or higher. Team plan workspaces can use it as-is; on Enterprise, an admin has to enable MCP access in workspace settings first.
Q. Can Claude send calendar invites without my approval?
A. The Google Calendar connector can create events, and events with attendees do notify them. That is why every prompt in this article ends with "show me the draft first, create only after I say go." Keep that line in your prompts and the send stays under your control.
Q. Does SuperIntern write to my Google Calendar?
A. No. Events are created by Claude through Claude's Google Calendar connector. SuperIntern MCP only serves meeting data, read-only; SuperIntern itself never touches your calendar.
Q. Can the AI modify or delete my meeting notes?
A. No. SuperIntern's MCP exposes no write operations. The only thing that changes in any of these workflows is your Google Calendar, and only after you approve.
Q. Whose meetings can Claude see?
A. Only the meetings your own SuperIntern account can view. Access follows your existing permissions, and the OAuth grant can be revoked at any time.
Q. Does this work with clients other than Claude?
A. SuperIntern MCP works with MCP-capable clients such as Claude Code, Codex, and Cursor. Google Calendar access varies by client, so check your client's connector or MCP options for the calendar side.
SuperIntern already remembers what your meetings decided. This workflow makes your calendar act on it.