Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
Description from the maker (original English)
Outlook.com, Microsoft 365, Google, iCloud, CalDAV: free time, events, invites, bookings, polls.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://calendar.lumman.co/mcpRun this in your terminal
claude mcp add --transport http calendar https://calendar.lumman.co/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"calendar": {
"url": "https://calendar.lumman.co/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"calendar": {
"type": "http",
"url": "https://calendar.lumman.co/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://calendar.lumman.co/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain lumman.co (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 220 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.3.0) reached the registry 5 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Agent-Native Google Calendar - manage events, sync, and public booking
Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Outlook.com, Microsoft 365, Google, iCloud, CalDAV: free time, events, invites, bookings, polls.
Multi Calendar is a remote MCP server run by Lumman Ltd. It puts every calendar account you connect - Outlook.com and Hotmail, Microsoft 365, Google, iCloud, Fastmail and other CalDAV calendars, several of each - behind one connector, so an AI client can find time free in all of them in one call, read and change events, answer invitations, and hand out booking links, booking pages and group polls. This repository holds what clients install: the manifests for Claude Code, Cursor, Gemini CLI and Antigravity, three skills and their evals. The server itself is not in it.
You need a Lumman account with at least one calendar account connected - in the window your AI client opens when it first connects, or at https://lumman.co/mcp/account/multi-calendar. Sign in there with Google, Microsoft, a passkey or an emailed code. Outlook.com, Hotmail and Microsoft 365 calendars connect with Microsoft sign-in, Google calendars with Google sign-in, iCloud calendars with an app-specific password made at Apple, and Fastmail and other CalDAV calendars with their address and a password. Each calendar account's permissions - seeing events, changing events, and inviting and replying - are set on the same page, and your time zone, working hours and other scheduling preferences on its Scheduling page, https://lumman.co/mcp/account/multi-calendar/scheduling.
Open Multi Calendar in Claude's connectors directory, https://claude.ai/directory/connectors/lumman-multi-calendar, and press Connect. The listing connects at https://calendar.lumman.co/mcp.
/plugin marketplace add lumman-lab/multi-calendar
/plugin install multi-calendar@multi-calendar
The plugin adds the connector at https://calendar.lumman.co/mcp and the three skills below. The first time a skill reaches the connector, Claude Code asks you to sign in; if it does not, run /mcp and choose the multi-calendar server.
Add the connector to ~/.cursor/mcp.json:
{
"mcpServers": { "multi-calendar": { "url": "https://calendar.lumman.co/mcp" } } }
Run MCP: Add Server, choose HTTP, paste https://calendar.lumman.co/mcp and name it multi-calendar. Or add it to your user mcp.json:
{
"servers": { "multi-calendar": { "type": "http", "url": "https://calendar.lumman.co/mcp" } } }
gemini extensions install https://github.com/lumman-lab/multi-calendar
The extension adds the connector at https://calendar.lumman.co/mcp and the three skills below. Its first call opens Lumman's sign-in in your browser; /mcp auth multi-calendar opens it again.
agy plugin install https://github.com/lumman-lab/multi-calendar
The plugin adds the connector at https://calendar.lumman.co/mcp and the three skills below, for the Antigravity CLI, app and IDE alike. To sign in, run /mcp in the CLI, open multi-calendar_multi-calendar and choose Authenticate, or in the app or IDE press Authenticate next to it under Agent settings, Customizations; approve on the Lumman page that opens, then paste the code Antigravity's page shows back into Antigravity.
Works fully on ChatGPT Business, Enterprise and Edu.
https://calendar.lumman.co/mcp, choose OAuth, tick the box and press Create as a plugin.Add a remote MCP server at https://calendar.lumman.co/mcp: Streamable HTTP, OAuth 2.1 with dynamic client registration. No key or client id is needed.
The connector answers a client's first call with where to sign in. The client registers itself with Lumman's authorisation server and opens a Lumman page that names it: sign in, add a calendar if none is connected, and approve. Every client you approve is listed under Connected AI clients at https://lumman.co/mcp/account/multi-calendar, where its access can be taken back.
Claude Code, Cursor, Gemini CLI and Antigravity load three skills with the connector, and pick one by themselves when a request matches it. In Claude Code each is also a command, such as /multi-calendar:week.
free-time - when you are free across every calendar, within your working hours, or when everyone in one of your circles is, with every calendar it could not read named. Books nothing.meetings - a meeting with guests shown to you as a draft, then made and its invitations sent only after you say yes to that draft.week - the week across every calendar, each meeting once, day by day, with clashes and unanswered invitations named. Changes nothing.Examples:
The connector offers these requests ready-made; a client shows them as prompts or commands.
week_ahead - The week ahead. Every meeting of the next seven days across all your calendars, with clashes and invitations still to answer.daily_agenda - Today's agenda. Today across all your calendars at a glance, made to run as a scheduled task.answer_invitations - Invitations to answer. Invitations still waiting for your answer across all your calendars, each answered only as you say.schedule_meeting - Set up a meeting. Find a time every calendar has open and send the invitations once you say yes to the draft.| Tool | Name |
|---|---|
calendars_list | List calendars |
events_list | Read events |
events_get | Read an event |
free_times_find | Find a time |
events_create | Create an event |
events_edit | Change an event |
events_cancel | Cancel an event |
events_respond | Answer an invitation |
preferences_get | Read scheduling preferences |
preferences_set | Change scheduling preferences |
busy_everywhere_set | Show busy time everywhere |
booking_links_create | Make a booking link |
booking_page_set | Set up a booking page |
polls_create | Make a group poll |
polls_results | Read a poll's answers |
polls_book | Book a poll's time |
links_polls_list | List open links and polls |
links_polls_close | Close a link or poll |
circles_invite | Invite people into a circle |
circles_list | List circles |
circles_free_times_find | Find a time for a circle |
Every client sends its calls to https://calendar.lumman.co/mcp, run by Lumman. Signing in runs through the authorisation server that address names. Lumman keeps no copy of your calendars: events are read from Microsoft, Google, Apple or the calendar's own server when a client asks, when a guest opens your booking page or link, when a member of your circle searches, and - where you show busy time in another calendar - by Lumman's own pass that keeps those busy blocks current. The words of every event a client reads - an invitation from a stranger included - are screened for prompt attacks by Google Cloud's Model Armor, as are the words of every event a client writes before they reach your calendar, and the events are passed on only to the client you approved. A booking link, booking page or poll keeps what it needs to offer times - its meeting's name and length, and for a poll the addresses it is for and their answers until it closes. What the connector passes on, and to whom, is in the privacy policy: https://lumman.co/privacy.
The meetings skill asks the client to show a meeting and wait for your yes. What the connector itself enforces is each calendar account's permissions, set at https://lumman.co/mcp/account/multi-calendar: with inviting and replying off, no invitation is sent from that account, whatever a client asks. A meeting at a time outside a guest's working day, where their time zone is known, is not sent until the client passes on that you agreed.
claude plugin eval . runs three cases, one per skill, and thirteen choose-* cases, against an invented week across an Outlook.com and a Google calendar, with an iCloud and a CalDAV account in their own cases, answered from fixed mock files under evals/. Each choose-* case is a request in a person's own words - what is on, when they are free or available, scheduling, moving, an invitation, a booking page, a poll, an iCloud or a Fastmail calendar - that the connector's tools should take, and three are requests no calendar tool should take. They read the tools' own descriptions, saved in evals/mocks/multi-calendar/_tools.json; the mocks carry no server instructions. Run on 2 November 2026 with Claude Code 2.1.308 and model claude-sonnet-5-5, three runs per case: all thirteen passed 3 of 3.
To see what the skills add, each of the three skill cases ran in two setups with the connector's tools in place: once with the plugin as shipped, once with its skills/ folder removed (claude plugin eval --ablation none). Run on 18 October 2026 with Claude Code 2.1.292, model claude-sonnet-5-5 and claude-sonnet-5-5 as the judge (--judge-model), three runs per case each way:
Overall score 1.00 with the skills and 0.67 without. Three runs per case is a small sample, and the mocks answer the same whatever Claude changes.
Report a vulnerability privately through GitHub, as SECURITY.md describes.
Write to the address under Contact Us in Lumman's privacy policy: https://lumman.co/privacy.
The files in this repository are under the MIT licence in LICENSE. The Multi Calendar service they connect to is provided under Lumman's terms: https://lumman.co/terms.