Calendly MCP connector for AI agents

Calendly MCP tools for AI agents

CALL ANY TOOL

12 tools covering availability.

calendlymcp_availability_get_user_availability_schedule

Use: fetch details for one named availability schedule. when

Use: fetch details for one named availability schedule. when: user asks about specific schedule rules or needs rules for a named schedule. needs: schedule uri from `availability-list_user_availability_schedules`. do: read `rules` array and `timezone` for display or to inform event-type updates. avoid: writing to this schedule—use event-type-level update for changes. then: report schedule details to user or use rules for availability queries.

Parameters

Name

Type

Required

Description

uri

string

Required

Availability schedule URI. not a browsable link — never show to users.

calendlymcp_availability_list_user_availability_schedules

Use: list all named availability schedules for the connected

calendlymcp_availability_list_user_busy_times

Use: list a user's busy time blocks within a date range. whe

calendlymcp_event_types_create_event_type

Use: create a new event type on the connected account. when:

calendlymcp_event_types_get_event_type

Use: fetch full details for one event type by uri. when: bef

calendlymcp_event_types_list_event_type_availability_schedule

Use: read the current availability schedule (rules) for an e

calendlymcp_event_types_list_event_type_available_times

Use: list bookable time slots for an event type within a dat

calendlymcp_event_types_list_event_types

Use: list all event types for the connected user or org. whe

calendlymcp_event_types_update_event_type

Use: update fields on an existing event type. when: user ask

calendlymcp_event_types_update_event_type_availability_schedule

Use: overwrite the availability schedule for an event type.

calendlymcp_locations_list_user_meeting_locations

Use: list allowed meeting location kinds for a user. when: b

calendlymcp_meetings_cancel_event

Use: cancel a scheduled meeting on behalf of the connected h

Build your Agent

Same auth pattern across every framework.

from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="calendlymcp")

mcp = MultiServerMCPClient({
    "calendlymcp": {
        "url": "https://mcp.scalekit.com/calendlymcp",
        "headers": {"Authorization": "Bearer " + token}
    }
})
tools = await mcp.get_tools()

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "calendlymcp" });

const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/calendlymcp
// Pass: Authorization: Bearer + token

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "calendlymcp" });

const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/calendlymcp
// Pass: Authorization: Bearer + token

from google.adk.agents import LlmAgent
from scalekit import ScalekitClient

client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="calendlymcp")
# Connect to MCP at https://mcp.scalekit.com/calendlymcp
# Pass: Authorization: Bearer + token

Try these prompts

Paste any prompt into your agent to get started.

Get started

Copy the prompt

Copied

Use: Fetch profile for a specific user by URI?

Copy the prompt

Copied

Use: Create a single-use share link for a one-on-one event type with per-link overrides When: User wants a single-use li?

Advanced

Copy the prompt

Copied

Use: List routing forms for the org?

Copy the prompt

Copied

Use: Revoke a pending organization invitation?

SEE HOW AUTH WORKS

User authorises once. Every agent call after uses their token with scope enforcement.

Authorize

Your user connects

Calendly MCP

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Calendly MCP

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Calendly MCP

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Calendly MCP

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other connectors.

OPS

Email-to-calendar scheduling agent

Parse scheduling intent from Gmail threads and create Google Calendar events with the right attendees and timezone.

Gmail

Google Calendar

View agent

SALES

Sales call prep agent

Pull Granola notes and Attio contact history to draft a pre-call brief before every sales meeting. Zero rep input.

Granola

Attio

View agent

Why Scalekit

Secure your agent's access. Connectors ship in minutes

Other connector libraries treat auth as a demo afterthought.

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential.

// shared token
 audit → bot_service_account

 // scalekit
 audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

One connector today. Ten tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Calendly as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Calendly OAuth token stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Calendly?
Yes. Pass a tool name filter to listScopedTools so the scheduling agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Calendly.

What happens when a user revokes Calendly access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Can the agent see other people's availability?
Only calendars the authorizing user can already see in Calendly. Busy times, schedules, and event types resolve per user, so the agent books like the person, not like an admin.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit