Calendly

Live

OAUTH 2.0

CALENDAR

Calendar

Every meeting booked, event type configured, and invitee captured lives in Calendly. Calendly MCP gives your agent authenticated access to your scheduling scoped to the user who authorized it.

  • Acts as the user: Access and write actions stay tied to the Calendly account that authorized the agent.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: User permissions enforced. 90-day audit trail.
Calendly
agent · Acme Q3
Run
What meetings are on my calendar tomorrow and who are the invitees?
S
calendly_events_list
68ms
Scheduling agent
3 meetings tomorrow. 10am with sarah@acme.com (intro call), 2pm with james@globex.com (demo), 4pm group with 4 invitees (Q4 planning).
Sources: 3 events, primary calendar
calendlymcp
3 events
18:29
Message Claude...

Tools your scheduling agent reaches for on Calendly, scoped per user.

CALL ANY TOOL
List event types, scheduled events, and invitees. Cancel or inspect any booking.
calendly_activity_log_list
List activity log
Returns a list of activity log entries for a Calendly organization. Requires Enterprise plan.
Parameters
Name
Type
Required
Description
organization
string
Required
Organization URI, e.g. https://api.calendly.com/organizations/{uuid}.
action
string
Optional
Filter by action type (e.g. user.created, event_type.updated).
actor
string
Optional
Filter by actor user URI.
count
integer
Optional
Number of results per page (max 100).
max_occurred_at
string
Optional
Filter entries occurring before this time (ISO 8601).
min_occurred_at
string
Optional
Filter entries occurring at or after this time (ISO 8601).
page_token
string
Optional
Token for fetching the next page of results.
sort
string
Optional
Sort field and direction, e.g. occurred_at:asc or occurred_at:desc.
calendly_current_user_get
Get current user
calendly_data_compliance_events_delete
Delete data compliance events
calendly_data_compliance_invitees_delete
Delete data compliance invitees
calendly_event_invitee_get
Get event invitee
calendly_event_invitees_list
List event invitees
calendly_event_type_availability_schedules_list
List event type availability schedules
calendly_event_type_availability_schedules_update
Update event type availability schedules
calendly_event_type_available_times_list
List event type available times
calendly_event_type_create
Create event type
calendly_event_type_get
Get event type
calendly_event_type_memberships_list
List event type memberships
calendly_event_type_update
Update event type
calendly_event_types_list
List event types
calendly_group_get
Get group
calendly_group_relationship_get
Get group relationship
calendly_group_relationships_list
List group relationships
calendly_groups_list
List groups
calendly_invitee_create
Create invitee
calendly_invitee_no_show_create
Create invitee no show
calendly_invitee_no_show_delete
Delete invitee no show
calendly_invitee_no_show_get
Get invitee no show
calendly_locations_list
List locations
calendly_one_off_event_type_create
Create one off event type
calendly_organization_get
Get organization
calendly_organization_invitation_create
Create organization invitation
calendly_organization_invitation_get
Get organization invitation
calendly_organization_invitation_revoke
Organization Invitation Revoke
calendly_organization_invitations_list
List organization invitations
calendly_organization_membership_delete
Delete organization membership

For more tools, view docs.

Build your Agent
Drop the toolkit in, point it at the user, and your scheduling agent can use Calendly from the first run.
Python · LlamaIndex
import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["calendly"], toolNames: ["calendly_user_get", "calendly_event_types_list", "calendly_events_list"] },
pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
name: t.tool.definition.name,
description: t.tool.definition.description,
schema: z.object({}).passthrough(),
func: async (args) => {
const { data } = await sk.tools.executeTool({
toolName: t.tool.definition.name,
identifier: "user_123",
params: args,
});
return JSON.stringify(data);
},
}));

const agent = createReactAgent({ llm, tools: lcTools });
import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["calendly"], toolNames: ["calendly_user_get", "calendly_event_types_list", "calendly_events_list"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
type: "function",
function: {
name: t.tool.definition.name,
description: t.tool.definition.description,
parameters: t.tool.definition.input_schema,
},
}));

const resp = await openai.responses.create({
model: "gpt-4o", input: prompt, tools: llmTools,
});
import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["calendly"], toolNames: ["calendly_user_get", "calendly_event_types_list", "calendly_events_list"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
name: t.tool.definition.name,
description: t.tool.definition.description,
input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
model: "claude-sonnet-4-6", max_tokens: 1024,
tools: llmTools,
messages: [{ role: "user", content: prompt }],
});
import { Agent } from "@google/adk/agents";
import {
MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
connectionParams: new StreamableHTTPConnectionParams({
url: "https://mcp.scalekit.com/calendly",
headers: { Authorization: `Bearer ${userScopedToken}` },
}),
});

const agent = new Agent({
name: "agent", model: "gemini-2.0-flash",
tools: await toolset.getTools(),
});
Try these prompts
Paste any prompt into your agent to start using Calendly.
Search & recall
Copy the prompt
Copied
What meetings do I have this week?
Copy the prompt
Copied
Show me all active event types.
Copy the prompt
Copied
List invitees for [event name].
Copy the prompt
Copied
Get the meeting URL for tomorrow's first call.
Action & coordination
Copy the prompt
Copied
Cancel the 3pm meeting tomorrow: reason [reason].
Copy the prompt
Copied
Pull invitee responses for [event].
Copy the prompt
Copied
List bookings on my [event type] this month.
Copy the prompt
Copied
What is the last booking from [email]?
Reporting
Copy the prompt
Copied
How many meetings did I host this week?
Copy the prompt
Copied
Top 5 invitees by meeting count this month.
Copy the prompt
Copied
Cancellation rate on [event type].
Copy the prompt
Copied
Average lead time on bookings this quarter.
SEE HOW AUTH WORKS
Users authorize Calendly once. Their credentials stay vaulted, every call is checked, and every action is logged.
1
Authorize
Your user connects
Calendly
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
2
Store
Their
Calendly
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
3
Resolve
When your agent calls a
Calendly
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
4
Audit
Every
Calendly
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
Same per-user auth pattern across other scheduling agents and MCP connectors. Working code, live demos, fork what fits.
OPS
Email-to-calendar scheduling agent
Parse scheduling intent from Gmail threads and create Google Calendar events with the right attendees and timezone.
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.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.
01.
Bookings created under the wrong identity
A shared Calendly token looks fine in a demo. In production, every event created and availability checked logs as a service account. Booking attribution breaks. Rep-level scheduling rules break. Scalekit resolves the actual user's token so every Calendly action is attributed correctly.
// shared token
audit → bot_service_account
user_filter → broken

// scalekit
audit → user_abc
scope → enforced ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Calendly today. Google Calendar, Zoom, Outlook 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 2.0 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 team members' bookings?
Only if the authorizing user is on the same Calendly organization with the right role. Team member events surface for org admins; ICs see their own. Cross-org access stays denied.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""calendly"": {
""url"": ""https://mcp.scalekit.com/calendly"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.calendly]
url = ""https://mcp.scalekit.com/calendly""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""calendly"": {
""url"": ""https://mcp.scalekit.com/calendly"",
""type"": ""http""
}
}
}