Skip to content

Connectors / Scheduling

Scheduling MCP connectors for Claude, ChatGPT and Cursor

5+ Scheduling connectors in the catalog, each behind the same governed MCP endpoint as everything else in Elaichi.

https://api.elaichi.ai/mcp The same for every user.
  • Their own access. An agent never gets more than the person it acts for.

  • One connection, every client. Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent.

The connectors

Scheduling connectors in the catalog

Connect one and your whole team reaches it, each inside the access they already have, without anyone handling a credential.

8 connectors

Browse all 400+ connectors →

In practice

What teams do with Scheduling connectors

Drawn from the connector pages in this category, so every line describes something one of these connectors actually does.

Operations

  • Check what a location offers today

    Ask which services a branch or store runs, how they are categorized, and which staff or rooms are set up to deliver them, without opening the Jrni admin.

  • Update office hours across every event type

    When the team moves to summer hours, update the availability schedules for all Calendly event types in one pass instead of opening each one.

  • Keep shared calendars tidy

    Create a Google Calendar for a project or a room, add the launch dates and review meetings from a list, and rename or retire the calendar when the project closes.

Sales

  • Sign up a walk-in on the spot

    Create the new member record and start a checkout for the membership they picked while they are still standing at the counter.

  • Book a discovery call while still on the phone

    Ask for a slot on the demo event type and create the booking for the prospect before the conversation ends. No tab switching, and the meeting lands in Cal.com like any other.

  • Book the follow-up before the call ends

    Ask for the next open half hour that works for you and the prospect, and have the event created in Outlook Calendar with the right attendees and a note on what was agreed.

Support

  • Schedule the callback a customer asked for

    When a ticket needs a phone call, put the callback on the agent's Apple Calendar with the customer's name and the ticket reference in the notes, then change the time if the customer replies with a better one.

  • Trace a booking setup question quickly

    When a colleague asks why a service or resource is not appearing, fetch it by reference and read its settings back in plain language.

  • Schedule callbacks from the queue

    Turn a promised callback into a Google Calendar event on the agent's calendar, with the customer's name and ticket reference in the description. Reschedule it when the customer replies with a better time.

Recruiting

  • Cancel and reschedule an interview slot

    When a hiring manager drops out, cancel the scheduled Calendly event with a note to the candidate and check the team's busy times to find the next open slot.

  • See every interview booked this week

    Pull the list of bookings for the interview event types, check who is meeting which candidate, and spot the day that is overloaded before it arrives.

  • Schedule interview panels without the back and forth

    See when each interviewer is free, create the panel events in Outlook Calendar, and move them when a candidate asks for a different day.

Once it is connected

Things to ask

Each of these is answered against the access the person asking already has, in the Scheduling account you connected.

  • List every event on the Sales calendar next week.

    Apple Calendar

  • List every Cal.com event type longer than 45 minutes.

    Cal.com

  • List next week's scheduled events for the sales team.

    Calendly

  • Which events next week have no agenda in the description?

    Google Calendar

  • List all Jrni services with no resource assigned this week.

    Jrni

  • List tomorrow's appointment reservations for the studio.

    Momence

  • Show tonight's Now Book It bookings by table.

    Now Book It

  • List my Outlook Calendar events for next Tuesday.

    Outlook Calendar

The tools

What an agent can call in Scheduling

Connectors
5+

in the Scheduling catalog

Tools
377

callable the moment you connect

Hosted sign-in
7

connect with nothing to register

Of those 377 tools, 7% delete something. Restricting an agent to reads is not a promise here, it is 177 tools admitted and the rest left out — and a restricted tool is never advertised to the model at all.

Read 47%
177 tools · list, get, search
Write 18%
69 tools · create, update, send
Delete 7%
27 tools · delete, remove, archive
Other 28%
104 tools · vendor-specific verbs

One endpoint

https://api.elaichi.ai/mcp

Every connector above answers here.

Every Scheduling connector, by depth

Tool counts are what the connector exposes today; the split is what those tools do.

Hosted sign-in takes a partnership with each vendor, and more are in progress. Until one lands, Your own app means the connector works today — you register an OAuth app once and connect.

Scheduling connectors with tool counts split by read, write and delete
Connector Tools Read · write · delete Sign-in
Jrni 133 Hosted
Momence 73 Your own app
Calendly 59 Hosted
Google Calendar 38 Hosted
Now Book It 24 Hosted
Cal.com 20 Hosted
Outlook Calendar 17 Hosted
Apple Calendar 13 Hosted

FAQ

Frequently asked questions

How many Scheduling connectors does Elaichi have?

5+ Scheduling connectors are in the catalog today, and the list grows as connectors are added. Each one arrives as a set of MCP tools an agent can call through https://api.elaichi.ai/mcp.

Can Claude, ChatGPT and Cursor all use Scheduling connectors?

Yes. Elaichi exposes one organization-wide endpoint, https://api.elaichi.ai/mcp, and Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent all connect to that same address with OAuth. Connecting a Scheduling account once makes it reachable from every one of them.

Do Scheduling connectors work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Scheduling connectors are reached over the same MCP endpoint every client uses, so anything that speaks MCP can call them — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor and the Elaichi Agent. There is no per-client setup beyond pointing the client at https://api.elaichi.ai/mcp.

Do Scheduling connectors need me to bring my own OAuth app?

Most do not. 7 of the Scheduling connectors use Elaichi's hosted sign-in, with nothing to register. The other 1 ask you to bring your own OAuth app: you register it once with the vendor and connect. Hosted sign-in for those is in progress, a vendor partnership at a time, and when one lands the only thing that changes is that the registration step goes away. Each connector's page says which it is before you start.

Can I stop an agent from writing to Scheduling tools?

Yes. Tool restrictions apply at role and individual level, and a restricted tool is never advertised to the model, so it cannot be called or guessed at from the tool list. Read-only access to a Scheduling connector is a matter of allowing the reads and leaving the writes out.

Whose access does an agent get on a shared Scheduling connection?

The access of the person the agent is acting for, resolved against their current role on every call — not the access of whoever connected the account. A colleague can use a connection without ever seeing its credential.

Nearby

Teams that connect Scheduling usually connect these too

Put Scheduling connectors in front of your team

14 days on Gold, no credit card. Connect one and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.