Is there an official Google Calendar or Outlook Calendar MCP server?
No. Google and Microsoft publish calendar APIs, not MCP servers, and each requires its own developer application and its own consent screen. The community servers that exist wrap one of the two, so an assistant sees half your week: your own agenda on one side, the client calendar you were invited to on the other, and no way to answer “when am I actually free on Thursday”. Nilyo connects both kinds of account behind one set of tools.
One URL, OAuth, about two minutes
The server is at https://nilyo.com/mcp over streamable HTTP. Add it as a connector in Claude, ChatGPT, Cursor or any MCP client and choose OAuth: the client registers itself, opens a browser once, and you sign in and authorize the accounts the agent may reach. No key to generate, nothing to paste into a config file.
Resolve the calendar, never guess its name
An account holds several calendars — personal, work, a shared team one, subscribed holidays — and their identifiers are not their display names. calendar_list_calendars returns the exact ids, and every later action takes one; passing a name returns a corrective error naming the listing to run first. It sounds pedantic until an assistant books a client meeting in your holidays calendar, which nobody sees until the client does.
“What do I have tomorrow, across all my calendars?”
Times only mean something with a timezone
The classic failure of calendar automation is a naive local time: an event created at 14:00 with no offset lands at the wrong hour for whoever reads it elsewhere. Event times carry an explicit offset, so “Thursday at 2pm” is resolved once and stays that instant for everyone. It matters most exactly when it is hardest to notice — a meeting with somebody in another country.
“Book thirty minutes with Ada on Thursday afternoon and invite her by email.”
Creating an event notifies real people
Writing to a calendar is not bookkeeping: creating an event emails the attendees, and a blind retry after an ambiguous failure invites them twice. So writes are explicit, the state is read back rather than assumed, and a failed creation is reported instead of retried. Answering an invitation is its own action too — accepting, declining or tentative — because it is visible to the organiser.
“Accept the invitation for Friday and decline the one that overlaps.”
A calendar is only useful next to the rest
On its own a calendar assistant is a thin wrapper on a screen you already have open. It becomes useful next to the other accounts: who am I meeting tomorrow, what do I know about them on LinkedIn, what did we last say by email or on WhatsApp. That briefing is one prompt when the accounts sit behind the same server, and four copy-pastes when they do not.
“Who am I meeting tomorrow, what do I know about them on LinkedIn, and what did we last say by email?”
Common questions
Is there an official Google Calendar MCP server?
No. Google publishes a Calendar API, not an MCP server. Nilyo is a hosted MCP server that connects your Google calendar — and your Microsoft one — behind the same tools, so an assistant sees the whole week rather than one vendor’s half.
Does it work with Outlook and Microsoft 365?
Yes, with the same tools as Google. That is the point: one interface over both, because most people’s week is split across the two.
Can it create events and invite people?
Yes. Creating an event emails the attendees, so it is an explicit action and it is never retried blindly after an ambiguous failure — a duplicate invitation is visible to everyone you invited.
Will it get the timezone right?
Event times carry an explicit offset rather than a naive local time, which is the usual cause of meetings booked an hour off for the person on the other end.
Can it answer invitations for me?
It can accept, decline or mark tentative when you ask. It is a visible action to the organiser, so it stays something you request rather than something it decides.
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.