Google Calendar

Live

OAUTH 2.0

CALENDAR

Calendar

Meetings, availability, and scheduling all live in Google Calendar. Your agent can check availability, read event details, and create meetings, scoped to the calendar the user authorized.

  • Acts as the user: Calendar access and event creation stay tied to the Google 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.
Google Calendar
agent · Acme Q3
Run
Schedule a 30-minute sync with the product team next Tuesday at 2pm.
S
googlecalendar_create_event
77ms
Scheduling agent
Done. 30-minute sync scheduled for Tuesday Nov 5 at 2:00pm. Calendar invite sent to product team members.
Sources: 1 event created, product calendar
googlecalendarmcp
1 event
18:29
Message Claude...

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

CALL ANY TOOL
List calendars, create and update events, and retrieve event details. Same toolkit, every framework, no auth plumbing.
googlecalendar_add_calendar_to_list
List add calendar to
Subscribe the authenticated user to an existing calendar by adding it to their calendar list. This does not create a new calendar; use Create Calendar for that. Requires a valid Google Calendar OAuth2 connection.
Parameters
Name
Type
Required
Description
calendar_id
string
Required
ID of the existing calendar to subscribe to
color_id
string
Optional
Color ID for this calendar in the user's list, from the calendar section of the Colors resource
hidden
boolean
Optional
Whether the calendar is hidden from the user's calendar list UI
selected
boolean
Optional
Whether the calendar's events are displayed in the UI
googlecalendar_clear_calendar
Clear calendar
googlecalendar_create_calendar
Create calendar
googlecalendar_create_event
Create event
googlecalendar_delete_acl_rule
Delete acl rule
googlecalendar_delete_calendar
Delete calendar
googlecalendar_delete_event
Delete event
googlecalendar_get_acl_rule
Get acl rule
googlecalendar_get_calendar
Get calendar
googlecalendar_get_calendar_list_entry
Get calendar list entry
googlecalendar_get_colors
Get colors
googlecalendar_get_event_by_id
Get event by id
googlecalendar_get_setting
Get setting
googlecalendar_import_event
Import event
googlecalendar_insert_acl_rule
Insert acl rule
googlecalendar_list_acl_rules
List acl rules
googlecalendar_list_calendars
List calendars
googlecalendar_list_event_instances
List event instances
googlecalendar_list_events
List events
googlecalendar_list_settings
List settings
googlecalendar_move_event
Move event
googlecalendar_query_freebusy
Query freebusy
googlecalendar_quick_add_event
Quick add event
googlecalendar_remove_calendar_from_list
List remove calendar from
googlecalendar_search_events
Search events
googlecalendar_transfer_calendar_ownership
Transfer calendar ownership
googlecalendar_update_acl_rule
Update acl rule
googlecalendar_update_calendar
Update calendar
googlecalendar_update_calendar_list_entry
Update calendar list entry
googlecalendar_update_event
Update event
Build your Agent
Drop the toolkit in, point it at the user, and your agent can list, create, and update Google Calendar events 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: ["googlecalendar"], toolNames: ["googlecalendar_list_events", "googlecalendar_create_event", "googlecalendar_get_event"] },
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: ["googlecalendar"], toolNames: ["googlecalendar_list_events", "googlecalendar_create_event", "googlecalendar_get_event"] },
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: ["googlecalendar"], toolNames: ["googlecalendar_list_events", "googlecalendar_create_event", "googlecalendar_get_event"] },
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/googlecalendar",
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 managing Google Calendar.
Search & recall
Copy the prompt
Copied
What meetings do I have tomorrow?
Copy the prompt
Copied
Find all events with [person name] this month.
Copy the prompt
Copied
List all meetings with [keyword] in the title this week.
Copy the prompt
Copied
What is on my calendar for next Monday?
Scheduling & creation
Copy the prompt
Copied
Schedule a 30-minute call with [email] next Tuesday at 2pm.
Copy the prompt
Copied
Create a recurring weekly standup every Monday at 9am.
Copy the prompt
Copied
Block 2 hours on Friday afternoon for deep work.
Copy the prompt
Copied
Add [person email] to the [event name] meeting.
Updates & management
Copy the prompt
Copied
Move my 3pm meeting tomorrow to 4pm.
Copy the prompt
Copied
Cancel all meetings on [date].
Copy the prompt
Copied
Update the description of [event name] to: [text].
Copy the prompt
Copied
List all events I have organized this week.
SEE HOW AUTH WORKS
Users authorize Google Calendar once. Their Google credentials stay vaulted, every call is checked, and every action is logged.
1
Authorize
Your user connects
Google Calendar
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
Google Calendar
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
Google Calendar
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
Google Calendar
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.
Support and Ops Teams
Email-to-calendar agent
Reads scheduling intent out of Gmail threads, resolves the times everyone actually has free, and creates the event on the user's own Google Calendar. No shared service account.
GTM and RevOps Teams
Sales call prep agent
Reads tomorrow's calls from Google Calendar, mines past Granola notes and Attio history for context, and delivers each rep a prep brief in Slack, scoped to the calls that rep actually owns.
Support and Ops Teams
Meeting prep
Pulls agenda, participant context, and open action items before every meeting.
Engineering Teams
Slack triage
Polls Slack for new messages, classifies bugs and support requests with a LangGraph router, files GitHub issues or Zendesk tickets, and confirms in the thread.
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
Read scheduling intent out of Gmail threads, resolve mutual free time, and create the Google Calendar event.
SALES
Sales call prep agent
Read tomorrow's calls from Google Calendar, mine Granola notes and Attio history, and deliver each rep a prep brief in Slack.
OPS
Meeting prep agent
Assemble the agenda, HubSpot attendee history, and open action items from Gmail before every meeting on the calendar.
ENGINEERING
Slack triage agent
Classify new Slack messages as bugs or support requests, file the GitHub issue or Zendesk ticket, and reply in the thread.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
01.
Events booked on the wrong calendar
A shared Google service account looks fine in a demo. In production, every event created or modified appears on the wrong calendar, from the wrong identity. Calendar permissions break. Meeting invites come from a bot. Scalekit resolves the actual user's OAuth token, so events land on the right calendar.
// shared bot token
token = "sk_googlecalendar_shared_xxx"
audit → bot_service_account
user_filter → broken

// scalekit · per-user
token = resolve(user_id)
audit → user_abc
scope → enforced ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Google Calendar today. Zoom, Outlook, Calendly 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 Google Calendar 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 Google Calendar 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 Google Calendar?
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 Google Calendar.

What happens when a user revokes Google Calendar 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 create events on shared calendars?
Yes, if the authorizing user has write access to that calendar in Google. Shared team calendars, group calendars, and the user's own calendar all work. Access mirrors what the user can do natively.

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"": {
""googlecalendar"": {
""url"": ""https://mcp.scalekit.com/googlecalendar"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.googlecalendar]
url = ""https://mcp.scalekit.com/googlecalendar""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""googlecalendar"": {
""url"": ""https://mcp.scalekit.com/googlecalendar"",
""type"": ""http""
}
}
}