OpenRuna
Sign in
← Workflows

Build an MCP Server with Google Calendar

23 nodes · googleCalendarTool, mcp, agent, chat, memoryBufferWindow, mcpClientTool

Engine
n8n
Nodes
23
Trigger
scheduled/triggered
Source file
1071_Googlecalendartool_Stickynote_Create_Triggered.json

Workflow flow

IntegrationsGoogleCalendarToolMCPAgentChatMemoryBufferWindowMcpClientToolLmChatOpenAi@n8n/n8n-nodes-langchain.mcp@n8n/n8n-nodes-langchain.agent@n8n/n8n-nodes-langchain.chat@n8n/n8n-nodes-langchain.memoryBufferWindow@n8n/n8n-nodes-langchain.mcpClientTool+1 more
100%

SearchEvent

GoogleCalendarTool

CreateEvent

GoogleCalendarTool

UpdateEvent

GoogleCalendarTool

DeleteEvent

GoogleCalendarTool

TRIGGER

Google Calendar MCP

@n8n/n8n-nodes-langchain.mcp

TRIGGER

When chat message received

@n8n/n8n-nodes-langchain.chat

Simple Memory

@n8n/n8n-nodes-langchain.memoryBufferWindow

Calendar MCP

@n8n/n8n-nodes-langchain.mcpClientTool

gpt-4o

@n8n/n8n-nodes-langchain.lmChatOpenAi

AI Agent

@n8n/n8n-nodes-langchain.agent

10 steps · flows top to bottom, branches left to right

Browse by integration

googleCalendarToolmcpagentchatmemoryBufferWindowmcpClientToollmChatOpenAi
Browse all integrations →
Download n8n JSONDownload sanitized JSONDownload flow graph

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

Free n8n workflow: Build an MCP Server with Google Calendar. 23 nodes across googleCalendarTool, mcp, agent, chat, memoryBufferWindow, mcpClientTool, lmChatOpenAi, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

"Build an MCP Server with Google Calendar" is an n8n automation built from 23 nodes spanning googleCalendarTool, mcp, agent, chat, memoryBufferWindow, mcpClientTool, lmChatOpenAi. 23 nodes · googleCalendarTool, mcp, agent, chat, memoryBufferWindow, mcpClientTool Execution begins at the scheduled/triggered trigger and flows through the 23 configured nodes. OpenRuna shows the full flow diagram, an integration breakdown, and a one-click JSON export for n8n's "Import from file". Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Benchmark it against your current googleCalendarTool integration to spot missing steps or redundant nodes.
  • Fork it to add error handling, retries, or a notification step without designing the 23-node flow from scratch.
  • Use it as a starting template when wiring googleCalendarTool, mcp, agent, chat, memoryBufferWindow, mcpClientTool, lmChatOpenAi — adjust node parameters to your accounts and record IDs.
  • Import "Build an MCP Server with Google Calendar" into n8n, reconnect credentials for googleCalendarTool, mcp, agent, chat, memoryBufferWindow, mcpClientTool, lmChatOpenAi, and run the same automation in your own workspace.

Example output

Imported into n8n, "Build an MCP Server with Google Calendar" exposes 23 configured nodes. Trigger type: scheduled/triggered. Integrations: googleCalendarTool, mcp, agent, chat, memoryBufferWindow, mcpClientTool, lmChatOpenAi. Set your credentials on the googleCalendarTool node, then verify each downstream node picks them up. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Paste the exported JSON for "Build an MCP Server with Google Calendar" into Claude and ask it to explain each of the 23 nodes. Claude is good at suggesting credential mappings for googleCalendarTool, mcp, agent, chat, memoryBufferWindow, mcpClientTool, lmChatOpenAi, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "Build an MCP Server with Google Calendar" to your accounts — which googleCalendarTool, mcp, agent, chat, memoryBufferWindow, mcpClientTool, lmChatOpenAi credentials to create and which node parameters to change first.

Cursor

Open the downloaded JSON in Cursor and use Agent mode to refactor hard-coded URLs into env vars, or to generate tests for any Code nodes. Keep the OpenRuna flow diagram open so you do not break connection order across the 23 nodes.

Frequently asked questions

How do I import "Build an MCP Server with Google Calendar" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "Build an MCP Server with Google Calendar" use?
It uses: googleCalendarTool, mcp, agent, chat, memoryBufferWindow, mcpClientTool, lmChatOpenAi. The flow diagram above shows how each service connects across the 23 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own googleCalendarTool and mcp credentials in n8n after import.
What trigger type does "Build an MCP Server with Google Calendar" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "Build an MCP Server with Google Calendar" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for googleCalendarTool, mcp, agent, chat, memoryBufferWindow, mcpClientTool, lmChatOpenAi.

Related resources