Connect your AI Agents to Google Calendar in minutes

Available tools
list_acl_rules
List all access control rules for a calendar. Returns permissions for each user/group including role and scope. Supports pagination and incremental sync.
get_acl_rule
Retrieve details of a specific ACL rule by ID. Returns role and scope. Rule ID format: 'user:email@example.com' or 'group:group@example.com'.
create_acl_rule
Grant access to a calendar by creating an ACL rule. Share with users, groups, domains, or make public. Specify role and scope type.
update_acl_rule
Completely replace an ACL rule. For partial updates, use patch_acl_rule instead.
patch_acl_rule
Partially update an ACL rule. Only provided fields are modified. Safer than update_acl_rule for simple permission changes.
delete_acl_rule
Permanently delete an ACL rule, removing user/group access. Cannot be undone.
watch_acl_rules
Set up push notifications for ACL rule changes. Requires publicly accessible HTTPS endpoint. Returns channel ID and resource ID to stop the watch later.
get_calendar
Retrieve complete metadata for a calendar including title, description, timezone, and location.
create_calendar
Create a new secondary calendar with custom title, description, timezone, and location.
update_calendar
Update calendar metadata (title, description, timezone, location). Owner only. For user-specific settings like color/visibility, use update_calendar_in_list.
delete_calendar
Permanently delete a secondary calendar and all events. Cannot be undone. Cannot delete primary calendar. For temporary removal, use remove_calendar_from_list.
clear_calendar
Permanently delete ALL events from a calendar without deleting the calendar itself. Cannot be undone. Calendar structure and sharing remain intact.

How to set up Merge Agent Handler
In an mcp.json file, add the configuration below, and restart Cursor.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5 "headers": {
6 "Authorization": "Bearer yMt*****"
7 }
8 }
9 }
10}
11Open your Claude Desktop configuration file and add the server configuration below. You'll also need to restart the application for the changes to take effect.
Make sure Claude is using the Node v20+.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "command": "npx",
5 "args": [
6 "-y",
7 "mcp-remote@latest",
8 "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
9 "--header",
10 "Authorization: Bearer ${AUTH_TOKEN}"
11 ],
12 "env": {
13 "AUTH_TOKEN": "yMt*****"
14 }
15 }
16 }
17}Open your Windsurf MCP configuration file and add the server configuration below.
Click on the refresh button in the top right of the Manage MCP server page or in the top right of the chat box in the box icon.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "command": "npx",
5 "args": [
6 "-y",
7 "mcp-remote@latest",
8 "https://ah-api.merge.dev/api/v1/tool-packs/<tool-pack-id>/registered-users/<registered-user-id>/mcp",
9 "--header",
10 "Authorization: Bearer ${AUTH_TOKEN}"
11 ],
12 "env": {
13 "AUTH_TOKEN": "<ah-production-access-key>"
14 }
15 }
16 }
17 }In Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows), run "MCP: Open User Configuration".
You can then add the configuration below and press "start" right under servers. Enter the auth token when prompted.
Learn more in the official documentation ↗
1{
2 "inputs": [
3 {
4 "type": "promptString",
5 "id": "agent-handler-auth",
6 "description": "Agent Handler AUTH_TOKEN", // "yMt*****" when prompt
7 "password": true
8 }
9 ],
10 "servers": {
11 "agent-handler": {
12 "type": "stdio",
13 "command": "npx",
14 "args": [
15 "-y",
16 "mcp-remote@latest",
17 "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
18 "--header",
19 "Authorization: Bearer ${input:agent-handler-auth}"
20 ]
21 }
22 }
23}FAQs on using Merge's Google Calendar MCP server
FAQs on using Merge's Google Calendar MCP server
What are common use cases for a Google Calendar MCP server?
The "best" use cases will naturally depend on your agents, but here are a few common scenarios:
- Meeting management: Your agent can coordinate cross-team meetings by checking availability across multiple calendars
- Lead nurturing: Your agent can automatically create calendar events when deals reach certain stages in CRM systems
- Ticket escalations: Your agent can schedule follow-up meetings based on ticket status changes in project management tools
- Task reminders: Your agent can create calendar reminders for upcoming project deadlines pulled from task management systems
- Automated email scheduling: Your agent can parse messages in an app like Slack or email to identify scheduling needs and create calendar invites
What MCP servers should I use alongside the Google Calendar MCP server?
Like the previous question, the best complementary MCP servers will depend on your agentic use cases. That said, here are a few that you’ll likely need to use with the Google Calendar MCP server:
- Slack MCP server: Bridges calendar scheduling with team communication and collaboration workflows
- Gmail MCP server: Connects email-based scheduling requests with calendar management and meeting coordination
- Linear MCP server: Links project management timelines and task tracking with calendar scheduling
- Salesforce MCP server: Integrates customer communications and other sales pipeline activities with meeting scheduling
- Google Drive MCP server: Connects document management and file storage with calendar events
What are popular tools for Google Calendar’s MCP server?
Here are a few common tools across data categories:
Event tools
- <code class="blog_inline-code">create_event</code>
- <code class="blog_inline-code">get_event</code>
- <code class="blog_inline-code">update_event</code>
- <code class="blog_inline-code">delete_event</code>
- <code class="blog_inline-code">List_events</code>
Calendar tools
- <code class="blog_inline-code">get_calendar_from_list</code>
- <code class="blog_inline-code">add_calendar_to_list</code>
- <code class="blog_inline-code">update_calendar_in_list</code>
Availability tools
- <code class="blog_inline-code">check_availability</code>
- <code class="blog_inline-code">find_meeting_times</code>
- <code class="blog_inline-code">query_freebusy</code>
Can I set custom security rules for Google Calendar tool calls in Merge Agent Handler?
You can easily set a wide range of rules. Here are just a few examples:
- Credit card numbers: Block any <code class="blog_inline-code">create_event</code> tool calls that contain credit card numbers in the event title or description before they're created in Google Calendar
- Social security numbers: Prevent your agents from adding SSNs to calendar event descriptions or attendee notes
- Email addresses: Redact email addresses from get_event or list_events responses, so agents only see masked versions (e.g., j*@merge.dev)
- Phone numbers: Automatically redact phone numbers from calendar event details when agents retrieve them
- Meeting URLs: Log whenever your agents access or share meeting links from calendar events to monitor for potential data exfiltration
What makes Merge Agent Handler’s Google Calendar MCP server better than alternative Google Calendar MCP servers?
Here are just a few reasons:
1. Enterprise-grade security
Merge Agent Handler provides a security gateway and data loss protection (DLP) that scans tool inputs and outputs for sensitive data and automatically blocks/redacts according to configured rules. This prevents data misuse and enforces strong governance.
2. Built-in authentication and credential handling
Merge Agent Handler manages authentication, credential prompting, and validation for each registered user, ensuring that agents only act with approved permissions across MCP connectors.
3. Connector Studio for customization
If you need custom Google Calendar actions or extended behaviors, Connector Studio allows you to add and modify its tools, whether it's a tool's description, name, or schema.
4. Real-time observability with searchable logs
Merge Agent Handler logs every tool call and underlying API request, giving your team full auditability and visibility into your agents' behaviors.
Explore other MCP servers built and managed by Merge








Ready to try it out?
Whether you're an engineer experimenting with agents or a product manager looking to add tools, you can get started for free now
