Context-aware Google Calendar management with MCP protocol
Ready for 3.0What this workflow does
This AI workflow has 19 nodes and runs when an MCP client calls one of its tools (plus 1 other trigger). Along the way it connects Google Calendar.
How it runs
Trigger: When an MCP client calls one of its tools (plus 1 other trigger).
- map_data (Edit Fields (Set)): sets or maps fields
- Operation (Switch): routes items into 5 branches
- validate_availability_event (Google Calendar): work with calendar
- delete_event (Google Calendar): delete
- check_availability_to_create (Google Calendar): work with calendar
- update_calendar (Google Calendar): update
- get_event_in_time_gap (Google Calendar): get many
- Edit Fields (Edit Fields (Set)): sets 1 field: available
- If: checks a condition and branches into true / false
- response_data_get_data (Edit Fields (Set)): sets or maps fields
…plus 2 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- MCP Server Trigger
@n8n/n8n-nodes-langchain.mcpTrigger - Execute Workflow Trigger
n8n-nodes-base.executeWorkflowTrigger - Switch
n8n-nodes-base.switch - Call n8n Workflow Tool
@n8n/n8n-nodes-langchain.toolWorkflow - Google Calendar
n8n-nodes-base.googleCalendar - If
n8n-nodes-base.if - Stop and Error
n8n-nodes-base.stopAndError - Edit Fields (Set)
n8n-nodes-base.set
From the author
Google Calendar MCP – Context-Aware Calendar Operations This n8n template implements an MCP (Model Context Protocol)-compliant module for managing Google Calendar events in a context-aware, conflict-free manner. 🧠 What It Does This MCP enables structured…