Build an MCP Server with Google Calendar
Configured with Agent, Chat Trigger, Google Calendar Tool, OpenAI Chat Model, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Integration
- Trigger
- AI & models
- Data store
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| SearchEvent | Integration | Google Calendar Tool | getAll |
| CreateEvent | Integration | Google Calendar Tool | See node parameters |
| UpdateEvent | Integration | Google Calendar Tool | update |
| DeleteEvent | Integration | Google Calendar Tool | delete |
| Google Calendar MCP | Trigger | Mcp Trigger | See node parameters |
| AI Agent | AI & models | Agent | See node parameters |
| When chat message received | Trigger | Chat Trigger | See node parameters |
| Simple Memory | Data store | Memory Buffer Window | See node parameters |
| Calendar MCP | Integration | Mcp Client Tool | See node parameters |
| gpt-4o | AI & models | OpenAI Chat Model | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
googleCalendarOAuth2ApiopenAiApi
Workflow notes
Introduce
Introduce
This tutorial focuses on guiding users through the process of deploying MCP service with Google Calendar. By following this step - by - step guide, you'll be able to leverage the powerful features of MCP Server with Google Calendar, such as creating, reading, updating, and deleting events.
Author
Author
SunGuannan
Freelance consultant from China, specializing in automations and data analysis. I work with select clients, addressing their toughest projects.
For business inquiries, email me at user@example.com.
Step1: Google Calendar tools require credentials
Step1: Google Calendar tools require credentials
If you don't have your Google Credentials set up in n8n yet, watch this video to learn how to do it.
If you are using n8n Cloud plans, it's very intuitive to setup and you may not even need the tutorial.
Step 2: Create MCP Server Trigger and activate
Step 2: Create MCP Server Trigger and activate
Log in to n8n and create a new workflow. On the new workflow page, click “Add First Step” to open a searchable menu of nodes and triggers.
Type “MCP Server Trigger” in the search bar and select it from the results to start your workflow.
This sets up how n8n receives events from the MCP Server, laying the groundwork for integrating Google Calendar into your automation.
Step 3: Incorporate Google Calendar Tools
Step 3: Incorporate Google Calendar Tools
After creating the MCP Server Trigger, rename it to "Google Calendar MCP " for clarity.
Click "Tools" and type "Google Calendar" in the search bar to find tools for various Google Calendar operations.
You can add multiple tools, each for a specific task. For example, "Get Many" retrieves multiple events, "Create" makes new ones, "Update" modifies existing events, and "Delete" removes them. Use these tools to build customized, efficient workflows for your Google Calendar data.
Step 4: Copy Your MCP Server Trigger URL and Activate Your Workflow
Step 4: Copy Your MCP Server Trigger URL and Activate Your Workflow
Double - click on the "Google Calendar MCP" node. On the node detail page, you'll locate the production URL, which might look something like "https://xxx/mcp/my - calendar/sse". Make sure to copy this URL as it will be used later in your workflow setup.
After obtaining the URL, save the workflow. Then, check the "Inactive" button to activate the trigger. Once activated, your workflow will start listening for events from the MCP Server, enabling seamless integration with the Google Calendar service.
Step 5: Create a New Workflow for AI Agent
Step 5: Create a New Workflow for AI Agent
At this stage, you're required to create a new workflow. Once the new workflow interface is open, click on the "Add First Step" option. In the list of available nodes and triggers that appears, search for and select the "on Chat Message" option to add it to your workflow. This sets the initial trigger for your AI-Agent-related workflow.
Step 6: Add AI Agent Node
Step 6: Add AI Agent Node
After successfully creating the Chat Messages Trigger, you can proceed to add an "AI Agent" node right after it. Double - click on this newly added "AI Agent" node to open its configuration panel.
In the configuration, you'll need to add a specific option. Under the System Message field, enter the following text: "You are a helpful assistant. Current datetime is {{ $now.toString() }}". This message provides the AI with the current date and time, which can be useful for context in various interactions.
Next, select an appropriate Large Language Model (LLM) from the available options. This model will be responsible for handling the chat and delivering events.
To enable continuous and context - aware conversations, add memory to the Agent. This allows the AI Agent to remember previous interactions, providing a more seamless and engaging chat experience.
Finally, search for and add the "MCP Client" tool. In the SSE Endpoint section of the "MCP Client" configuration, paste the URL that you copied in Step 4. This step connects the AI Agent workflow to the MCP Server, enabling data flow and interaction between the two.
Why model 4o? 👆
Why model 4o? 👆
After testing 4o-mini it had some difficulties handling the calendar requests, while the 4o model handled it with ease.
Depending on your prompt and tools, 4o-mini might be able to work well too, but it requires further testing.
Let's Try!
Let's Try!
Build an MCP Server with Google Calendar
Build an MCP Server with Google Calendar
Purpose and structure
This folder contains the Build an MCP Server with Google Calendar workflow. Its executable nodes use agent, chatTrigger, googleCalendarTool, lmChatOpenAi, mcpClientTool, mcpTrigger, memoryBufferWindow. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Google Calendar MCP, When chat message received
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Googlecalendartool/1071_Googlecalendartool_Stickynote_Create_Triggered.json MIT; preserve source notices.
Canvas section labels
These name areas of the original canvas; they do not include explanatory instructions.
- Learn How to Build a MCP Server with Google Calendar
- Enjoy It! 😊 😊 😊