Nilyo
Sign inGet started →
Claude + Calendar

Connect your calendar to Claude

Claude speaks MCP natively, so adding your calendar is one connector and one sign-in. What it does better than a one-shot integration is the preparation: it reads the event, then the guests, then what you last said to them, and only then tells you what the meeting is about.

Add the connector

In Claude, open settings, go to connectors and add a custom connector with the URL https://nilyo.com/mcp. Choose OAuth: Claude registers itself and opens a browser once so you sign in with Google or Microsoft. It works the same on claude.ai, in the desktop app and in Claude Code, and the same connected calendar is reachable from all three.

Let it read before it proposes

Ask for the outcome rather than the steps. “Prepare my Thursday” is enough: it lists the events, opens the ones with external guests, looks those people up, checks what you last exchanged, and gives you a briefing — or tells you nothing needs preparing. Reading a calendar is free of consequence, which is exactly why letting it read widely is safe.

“Prepare my Thursday: who am I seeing, what do I know about them, what did we last say?”
“Is anything double-booked next week?”

Put the rules in a Project

A Claude Project keeps your instructions across conversations: which calendar is the work one, never book before 9, always confirm before inviting someone external, the tone of a confirmation email. The tools stay the same; the judgement around them becomes yours instead of being re-explained every time.

Writes stay deliberate

Creating or moving an event notifies the attendees, so it is an explicit action, and an ambiguous failure is reported rather than retried. Answering an invitation is its own action for the same reason. Claude is good at deciding what should be proposed; it is you who decides what gets sent.

“Move the 3pm to Friday and tell the attendees why.”

The calendar is the spine of the rest

On its own, a calendar assistant is a wrapper on a tab you already have open. Next to LinkedIn, a mailbox and WhatsApp it becomes the thing that starts every briefing, because the meeting is what tells the assistant who to look up and why.

Common questions

Can Claude access my calendar?

Through an MCP connector, yes: it reads your Google and Microsoft calendars and events, and can create, move, cancel or answer them when you ask.

Does it work in Claude Code and the desktop app?

Yes, same server URL and same connected account across claude.ai, the desktop app and Claude Code.

Will it invite people on its own?

No. Inviting notifies real people, so it is an explicit action, and you can make confirmation a standing rule in a Project instruction.

Can it work across two calendars?

Yes, and that is usually the point: a personal Google calendar and a work Microsoft one answered in one question.

How Calendar works with Nilyo

Connection. Included with a Google or Microsoft sign-in: one identity gives email and calendar and counts as one account.

What your agent can do. Calendars, events in a date range, creating, updating, cancelling and restoring events, RSVPs.

Pacing and safety. No local budget.

  • Combine with LinkedIn and email for meeting briefs: attendees are matched to profiles and past conversations.

All Calendar guides

Related guides

Give Nilyo to your agent.

Paste one setup link. Your agent can guide OAuth, account connection and the first useful action.

© 2026 Nilyo.