MCP guides · Google Calendar
Calendar MCP is the unlock that makes 'find me 30 minutes' actually work.
Without it, every scheduling ask devolves into screenshots and copy-paste. With it, an agent reads your week, proposes real slots, and books holds. The cheapest 15-minute MCP install you will run.
The problem
Why this matters
Scheduling is the work that looks like five minutes and consumes an hour. Pull up calendar, scan three days, paste three options into an email, get a counter, paste again, finally book. By the time the meeting is on the calendar, half the energy you needed for the meeting is gone.
The default LLM workflow makes this worse, not better. You paste your week into a chat, get back made-up times, paste them in, realize the model invented a Tuesday slot that conflicts with your kid's pickup. There is no way to fix this by adding more prompt instructions.
MCP plus Google Calendar fixes it structurally. An agent that can actually read your calendar (and respect the constraints you care about) proposes real times. The 'I think I'm free' becomes 'here are three slots that work, want me to book?'.
What you get
What MCP unlocks here
Real availability, not LLM hallucination
Calendar MCP fetches your actual free/busy and your meeting events. The agent's proposed slots are real slots, not invented ones. The single biggest reliability gain you'll get from any MCP install.
Constraints you actually have
Block out kid pickup, focus blocks, no-meeting mornings. An agent that respects them ('avoid before 9am ET, avoid Wednesday afternoons') is the closest thing to a real chief of staff that current AI gets you.
Booking, not just suggesting
The win is closing the loop, not surfacing it. With write access scoped properly, the agent creates the calendar hold, sends the invite, sets the conference link. You see the booked event and move on.
Plays well with the rest of the stack
Calendar pairs with Gmail MCP for 'find time and propose to the recipient in this thread,' with CRM MCP for 'book the discovery call and update the deal stage,' with Nerve's pipeline for 'every overdue deal gets a proposed meeting time.'
Setup
Three steps to a working agent
Pick a Calendar MCP server
Community-maintained Google Calendar MCP servers cover list_events, get_event, find_free_slots, create_event. Nerve's own MCP exposes nerve_find_time (ranked slot suggestions across your constraints) and nerve_calendar_create. Either way, prefer servers that respect provider rate limits.
Scope OAuth to read + write events
events.readonly + events for write is enough. Avoid full calendar admin scopes. If you have multiple Google accounts, decide whether the agent reads all of them (work + personal merged availability) or just the work one.
Give the agent a recurring outcome
Stop chatting. Start asking: 'find time with X this week given my constraints,' 'every morning, surface meetings I should prep for,' 'book the three meetings I owe.' The recurring outcome is where Calendar MCP pays for itself, not the one-off lookup.
Signal
What people doing this say
The first time the agent booked a meeting end-to-end (proposed the slot, sent the invite, added the Zoom link) without me doing anything, I felt the future arrive.
Founder, climate tech (paraphrased)
I gave the agent my constraints once. Three months later, it still respects them. That's the part nobody talks about.
Operator, agency owner
Calendar MCP plus a pipeline tracker is the difference between 'I should book a meeting with this prospect' and 'meeting is on the calendar.'
Patrick Hillstrom, Nerve
FAQ
Common questions
Will the agent send invites without my approval?
Only if you scope it that way. The safe default is the agent proposes the slot and the invite, you tap approve. Nerve queues calendar creates as actions you confirm from the dashboard. Auto-send-invites is opt-in per workflow.
How does it handle multiple calendars (work + personal)?
Most Calendar MCP servers can be configured to read multiple calendars per Google account. Nerve's fan-out covers primary + selected + additional readable calendars per account, capped per account to keep latency manageable. You can also override per-user via a discovery mode flag.
What about Outlook / Microsoft 365?
Microsoft Graph has its own MCP server pattern. The principles are identical: read free/busy, write events, respect scopes. Nerve has Microsoft 365 calendar wired alongside Google, so the same agent reasoning works on both.
Can the agent suggest times that account for travel, prep, or back-to-back?
Yes, if you tell it the rules. 'Leave 15 minutes buffer between meetings,' 'no meetings during my flight to Austin Wednesday.' The MCP server returns raw availability; the agent applies your rules. Nerve's TimeFinderSkill is exactly this layer.
How is this different from Calendly?
Calendly is a shared booking link for inbound. Calendar MCP is an agent that books on your behalf for outbound and reciprocal scheduling. Different unit: link for them to use, vs. agent for you to direct.
Who this is for
Roles where this matters most
Nerve for working parents
An agent team that handles the logistics of family life so you can show up at work without dropping the ball at home. Built for working parents.
Nerve for newly promoted executives
Newly promoted executives drown in the gap between the old job and the new one. Nerve is the AI agent team that runs the operational layer so you can spend your first 90 days on the work that actually compounds.
Nerve for recruiters
Recruiting is a sales pipeline with worse forecasting and weirder buyers. Nerve runs the operations layer so your selling time stays on the calls that move searches forward.
Nerve for solo lawyers
Solo and small-firm lawyers run a practice on time-tracking, intake, and client follow-through. Nerve is the AI agent team that handles the practice's operations layer so your billable hours stay billable.
Nerve for executive coaches
Executive coaches scale on depth, not volume. Nerve is the AI agent team that handles client prep, session followup, and roster management so your time stays on the conversations that matter.
Nerve for wealth advisors
Wealth advisors run relationship businesses with high-touch expectations. Nerve is the AI agent team for the operations layer so your time stays on the conversations that compound trust.
Stop screenshotting your calendar. Wire it to an agent.
Start free, no credit cardMore MCP guides
Other MCP guides
The best MCP servers for founders, ranked by real founder workflows
MCP turns Claude into an agent team that touches your actual stack. These are the MCP servers a working founder hooks up first, why each one matters, and how Nerve wires them together.
Best MCP servers for sales teams: the pipeline-grade stack
The MCP servers a working sales team actually uses, ranked. CRM, inbox, calendar, and conversation surfaces, with notes on what each one does well and where it falls short.
MCP server setup guide: from zero to a working agent in 30 minutes
The honest guide to installing your first MCP server with Claude. Hosts, auth, gotchas, and what to do after the hello-world example works.
Claude MCP integration for Gmail: a working founder's setup guide
How to wire Gmail to Claude over MCP so an agent can triage, search, and draft from your real inbox. The 15-minute setup, the gotchas, and what changes when it's live.
Claude MCP integration for Salesforce: an agent that writes the right field
How to wire Salesforce to Claude over MCP so an agent can read your pipeline, log activities, and update deals without you swivel-chairing between tabs.
Claude MCP integration for Slack: where the real evidence of work lives
How to wire Slack to Claude over MCP so an agent can read threads, search context, and respond as you (when you let it). The quiet workhorse of MCP setups.