Cal.com MCP vs IntoCal hosted MCP: let Claude book meetings without self-hosting

Short answer: You no longer need to self-host anything to let Claude book meetings. Cal.com offers a hosted MCP server that connects to your own Cal.com account, plus a local version you run with Node.js and an API key. IntoCal gives every user a hosted MCP endpoint at https://api.intocal.com/mcp/yourname that works two ways: with your key, your own assistant manages your calendar; without a key, other people's assistants can request a booking with you, held until the guest confirms by email.

The question behind "without self-hosting"

Early MCP guides for scheduling tools all looked the same: install Node, run a package with npx, paste an API key into a JSON file, restart Claude Desktop. That works on one laptop, but it breaks the moment you want Claude on the web, on your phone, or on a colleague's machine. A hosted endpoint is a URL you paste once; there is nothing to keep running.

Cal.com MCP: what it is today

Cal.com documents two ways to connect:

• Hosted: add https://mcp.cal.com/mcp as a connector in Claude and approve access to your Cal.com account in the sign-in window. No API key needed.
• Local: run npx @calcom/cal-mcp@latest with a CAL_API_KEY, which needs Node.js 18 or later on the machine running Claude.

Both are built for one job: letting you, the account owner, ask your assistant to look at and change your own Cal.com schedule. If you already use Cal.com, the hosted connector is the easy route and you do not need to switch.

IntoCal hosted MCP: what's different

IntoCal's endpoint is per person and public by address, which allows a second use case: someone else's AI assistant booking time with you.

• Owner mode (with your sk_live_ key): your assistant can list event types, query open slots, create confirmed bookings, list bookings, list team members and cancel bookings.
• Public mode (no key): any MCP-capable assistant can list your event types, check slots and call request_booking. The booking is held as pending and the guest gets an email link to confirm, so an AI cannot fill your week with fake meetings.
• Teams: list_hosts_for_event and book_with_host let an assistant pick a team member by language, skill or category, and slots respect each member's connected Outlook or Google calendar.

Side-by-side

Set up IntoCal in Claude in about two minutes

1. Go to intocal.com/start. Sign up free if you haven't; it brings you back to the same page.
2. Connect your Outlook or Google calendar and create at least one event type, so there is something to book.
3. Click Generate API key. Copy the sk_live_ key; it is shown once.
4. In Claude Desktop, open Settings → Developer → Edit Config and paste the block below with your key.
5. Restart Claude and ask: "What 30-minute slots do I have on Thursday afternoon?" Then: "Book Maria Lind, maria@example.com, at the first one."

{
  "mcpServers": {
    "intocal": {
      "command": "npx",
      "args": ["-y", "@intocal/mcp"],
      "env": { "INTOCAL_API_KEY": "sk_live_..." }
    }
  }
}

If Claude says it cannot reach the server, work through MCP not connecting in Claude Desktop; the cause is almost always the config path, an old Node version, or a key pasted with a trailing space.

Let other people's assistants book you

Share the same URL without a key, for example in your email signature or on your website: https://api.intocal.com/mcp/yourname. When a client asks their assistant to "find time with you next week", it can read your real availability and request a slot. You see the request in your bookings once the guest confirms by email. AI assistants can also find IntoCal through /.well-known/mcp.json on intocal.com.

Which should you pick?

• Already on Cal.com and only you will use the assistant: use Cal.com's hosted connector.
• Outlook-first, want clients' AIs to book you, or want it on the Free plan: use IntoCal.

For the bigger picture of how agents book meetings, read how to book meetings with AI agents over MCP, or see the full MCP setup guide.