Use momo from an AI chat

Turn an AI chat request into a confirmed meeting — across calendars and external participants.

Setup

The connector address is https://mcp.momo.ai/mcp.

In Claude, add that address as a custom connector. Sign-in happens in the connector settings.

Claude does not offer sign-in inside the chat.

In ChatGPT Business, with developer mode, add the same address.

ChatGPT Enterprise and ChatGPT Edu were not part of the 9 October 2026 registration test, so this page does not say they work.

In Mistral Le Chat, add the same address as a custom connector. When Le Chat asks for client details, enter the client ID https://auth.momo.ai/clients/mistral and leave the client secret empty.

In opencode, add the address as a remote MCP server and set the OAuth client ID in opencode.json to https://auth.momo.ai/clients/opencode.

opencode keeps one connection per momo account: signing in on a second computer ends the connection on the first.

In Google Antigravity, add the same address. After you allow access, Google shows a code; paste it into Antigravity to finish the connection.

Preview and approval

Every write starts with a preview. momo tells your AI client to show it to you and to wait for your approval before anything is sent or booked.

momo's destructive tools start with a preview and tell the AI client to wait for your reply before it cancels or withdraws anything.

If your AI client offers per-tool permissions, choose "Ask before acting" for momo's write tools.

You are responsible for the mails an AI client sends through your account. momo shows the mail details in a preview and tells your AI client to wait for your reply before it sends the mail.

Calendars

momo uses the calendars already connected to your account: Google, Microsoft 365, and a CalDAV calendar you connected yourself, including iCloud.

Connecting CalDAV is the same capability as in email scheduling. MCP does not add a separate CalDAV feature and does not use a CalDAV plan flag as an access check.

Ask for the free times in a window and momo lists up to 70 bookable slots inside that window, in time order, and says when more exist. It does not look past the window.

In an AI chat, momo can make booking links you share yourself: one link for each time you choose, up to three at once.

Each link books its time once. Booking one link does not use up the others.

momo can also make a booking page that shows your free times within a window of up to 14 days. It books once.

A link closes when its time starts, and stays open for 7 days at most.

Before a guest books, momo checks your calendar again. A time that has been taken in the meantime cannot be booked.

Guests book without a momo account. They give their name and email, and both of you get a calendar invitation.

Someone signed in to momo books as themselves: the meeting goes straight into their calendar, and momo warns them if they already have something at that time.

You can revoke a link or page that has not been booked. A booked meeting is cancelled like any other.

The link carries its key after the "#", which browsers do not send to any server, so it does not appear in server logs.

The privacy policy describes what momo processes when someone books through a link.

Privacy boundaries

momo receives the parameters of the tool call, not the conversation in your AI client. The AI client processes that conversation itself.

A tool result contains status, times and email addresses. It does not contain event titles, the text of a mail, or free text from other participants.

momo, the MCP service and the authorization service each keep their own audit record: the event, the time, the service, an account id, the OAuth client id, the result and a request id.

The audit record does not contain mail text, calendar details or a recipient list. These records are deleted after 12 months.

The privacy policy is at momo.ai/privacy.

Examples

What changed on 30 October 2026

momo added booking links, a booking page, proposed times in a new request, and the free times you have in common with other momo users.

If your AI client does not show the new tools, disconnect momo in its connector settings and connect it again.

Questions

Why use momo instead of the built-in calendar connector?

A built-in calendar connector reads one calendar. momo coordinates a meeting with other people and emails them. The request starts with a preview; momo tells the AI client to wait for your approval before it sends the invitations.

momo shows as disconnected

If the connector shows as disconnected after you revoke access, reset your password, or the 90-day grant ends, reconnect it in the client's connector settings.

Claude does not offer sign-in inside the chat.

A link says it is no longer available

A link closes when its time starts, after 7 days, once it is booked, or when you revoke it. Make a new one for another time.

momo asks you to reconnect your calendar

reconnect_required means momo can no longer read your calendar. Reconnect it in your momo account at momo.ai/user, then try again.

A call is refused with invalid_request

The message names the rule the call broke, for example more than three booking links or a booking page longer than 14 days. Your AI client can correct the call and try again.

A confirmation answers commit_in_progress

momo is still booking. Send the same call again with the same approval id: it returns the result and never books twice.

A call answers calendar_unavailable

momo could not read a calendar just now. Try again in a minute; if it keeps happening, reconnect the calendar.

Security

Report a security issue to hello@momo.ai. momo.ai/.well-known/security.txt names the same contact.

Service status

momo does not publish a separate public status page. Report an incident to hello@momo.ai.

Support is hello@momo.ai.