Help / AI assistants (MCP)

AI assistants overview

42min has a built-in MCP server — a standard way for AI assistants to work with other apps. Connect an assistant such as Claude or ChatGPT to your 42min account and you can ask it things like "am I free Thursday afternoon?", "book Anna for 42 minutes next week", or "cancel my 3 pm and let the attendee know" — the assistant does it through your account, with your permission. Everything starts from the AI assistants (MCP) page under Integrations.

What it is

MCP (Model Context Protocol) is an open standard supported by Claude (web and desktop), ChatGPT, Claude Code, Cursor, and many other AI tools. 42min exposes your account to a connected assistant as a set of tools — check availability, list and create bookings, search contacts, manage scheduling polls, and more. The full list is on What your assistant can do.

Three things define how it behaves:

• It acts as you. The assistant sees exactly what you can see in the dashboard, based on your role — no more, no less. A regular member works with their own schedule; an admin can work org-wide. Details in Permissions and security.
• You approve access once. When you connect, 42min shows a consent screen describing what the assistant will be able to do. You can disconnect it at any time.
• It's host-side only. The assistant helps you manage your scheduling. Your invitees still book through your normal booking page — there's no assistant-facing booking flow for them.

When to use it

• Ask "what does my week look like?" and get a summary of upcoming meetings.
• Find a free slot and book a meeting with someone in one sentence.
• Cancel or reschedule a booking — the attendee is notified and calendars are updated, same as doing it in the dashboard.
• Generate single-use booking links to paste into an email the assistant is drafting.
• Set up a roundtable (group scheduling poll) with candidate times and participants.
• Look up a contact and their meeting history before a call.

How to get started

1. Open AI assistants (MCP) (Integrations → AI assistants).
2. Copy the endpoint URL shown in Step 1.
3. Add it to your assistant and sign in — client-specific steps are in Connecting your assistant.

Common pitfalls

• A banner says MCP is disabled. Your organization's admin can turn AI assistant access off for everyone, and on some servers the feature is rolled out gradually. See Permissions and security.
• The assistant can't see a colleague's calendar. That's by design — access follows your dashboard role. See the role table.
• Looking for a machine-to-machine integration instead? If you're building a script or product integration rather than connecting a chat assistant, use the REST API.