Back to Catalog

Build an MCP server with Google Calendar and custom functions

SolomonSolomon
69759 views
2/3/2026
Official Page

Learn how to build an MCP Server and Client in n8n with official nodes.

> ⚠ Requires n8n version 1.88.0 or higher.

In this example, we use Google Calendar and custom functions as two separate MCP Servers, demonstrating how to integrate both native and custom tools.

How it works

The AI Agent connects to two MCP Servers. Each MCP Trigger (Server) generates a URL exposing its tools. This URL is used by an MCP Client linked to the AI Agent.

Whenever you make changes to the tools, there’s no need to modify the MCP Client. It automatically keeps the AI Agent informed on how to use each tool, even if you change them over time.

That’s the power of MCP 🙌

Who is this template for

Anyone looking to use MCP with their AI Agents.

How to set up

Instructions are included within the workflow itself.

Check out my other templates

👉 https://n8n.io/creators/solomon/

n8n MCP Server with Google Calendar and Custom Functions

This n8n workflow demonstrates how to set up a Model Context Protocol (MCP) server that can interact with an AI Agent. It includes an example of using custom functions (tools) to extend the AI Agent's capabilities, specifically for interacting with Google Calendar.

What it does

This workflow acts as an MCP server, receiving requests from an MCP client and routing them to an AI Agent. The AI Agent is configured with a chat model, memory, and several tools, including a custom n8n workflow tool and an MCP client tool.

Here's a step-by-step breakdown:

  1. Listens for MCP Requests: The workflow starts with an "MCP Server Trigger" node, which acts as the entry point for requests from an MCP client.
  2. Initializes AI Agent: Upon receiving a request, an "AI Agent" node is activated. This agent is the core of the intelligent processing.
  3. Configures AI Agent:
    • It uses an "OpenAI Chat Model" for its language understanding and generation capabilities.
    • A "Simple Memory" node provides conversational memory, allowing the AI Agent to remember previous interactions within a session.
    • It's equipped with two tools:
      • "Call n8n Workflow Tool": This tool allows the AI Agent to execute other n8n workflows as custom functions. This is where you would define specific actions the AI can take (e.g., interacting with Google Calendar).
      • "MCP Client Tool": This tool enables the AI Agent to potentially make requests to other MCP servers or even itself, allowing for complex, multi-agent interactions.
  4. Processes AI Agent Output: The output from the "AI Agent" is then passed to an "Edit Fields (Set)" node, which is likely used to format or modify the AI's response before further processing.
  5. Conditional Routing (Switch): A "Switch" node is present, suggesting that the workflow can route the AI Agent's response based on certain conditions. This allows for different actions depending on the AI's output.
  6. Debug/Output: A "DebugHelper" node is included, which is useful for inspecting the data flow and debugging the workflow during development. An "HTTP Request" node is also present on an output path, indicating that the workflow might make external API calls based on the AI's decision.
  7. External Workflow Execution: An "Execute Workflow Trigger" node is available, which could be used by the "Call n8n Workflow Tool" to trigger a specific sub-workflow (e.g., one that interacts with Google Calendar).
  8. Chat Trigger: A "Chat Trigger" node is also present, which could be used as an alternative or additional entry point for chat-based interactions with the AI Agent, separate from the MCP server.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance (self-hosted or cloud).
  • OpenAI API Key: For the "OpenAI Chat Model" to function.
  • Google Calendar Account: If you intend to implement the Google Calendar integration using the "Call n8n Workflow Tool" to trigger a separate workflow.
  • MCP Client: Another n8n workflow or application capable of sending requests to this MCP server.

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON file.
    • In your n8n instance, go to "Workflows" and click "New".
    • Click the "Import from JSON" button and paste the workflow JSON.
  2. Configure Credentials:
    • OpenAI Chat Model: Configure the "OpenAI Chat Model" node with your OpenAI API Key.
    • Google Calendar (if applicable): If you implement the Google Calendar integration, ensure you have Google Calendar credentials set up in your n8n instance and configured in the sub-workflow that the "Call n8n Workflow Tool" will trigger.
  3. Activate the Workflow: Enable the workflow in n8n.
  4. Interact via MCP Client: Send requests from your MCP client to the webhook URL provided by the "MCP Server Trigger" node. The AI Agent will process these requests, using its language model and available tools to generate a response.
  5. Customize Tools:
    • To add custom functionality (like Google Calendar interactions), create a separate n8n workflow that performs the desired action.
    • Configure the "Call n8n Workflow Tool" in this MCP server workflow to trigger your custom workflow, passing relevant data as input.
    • Ensure the custom workflow is designed to receive input from the "Call n8n Workflow Tool" and return a meaningful output for the AI Agent.

Related Templates

Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets

This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.

Ranjan DailataBy Ranjan Dailata
161

Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax

Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions

Daniel NkenchoBy Daniel Nkencho
601

Automate Dutch Public Procurement Data Collection with TenderNed

TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte

Wessel BulteBy Wessel Bulte
247