Bear Brown
← All N8N workflows
AI & researchAgentChat TriggerDebug HelperExecute Workflow TriggerGoogle Calendar Tool

Build your first AI MCP Server

Configured with Agent, Chat Trigger, Debug Helper, Execute Workflow Trigger, and additional nodes. Review the connections and setup before adapting this template.

Download workflow JSONView files on GitHub ↗22 nodes · MIT
Workflow preview
AI & modelsAI AgentAgentIntegrationSearchEventGoogle Calendar ToolIntegrationCreateEventGoogle Calendar ToolIntegrationUpdateEventGoogle Calendar ToolIntegrationDeleteEventGoogle Calendar ToolTriggerGoogle Calendar MCPMcp TriggerTriggerWhen Executed byAnother WorkflowExecute Workflow TriggerRoutingSwitchSwitchTransformConvert Text to UpperCaseEdit FieldsTransformConvert Text to LowerCaseEdit FieldsSubworkflowConvert TextTool WorkflowTriggerWhen chat messagereceivedChat TriggerData storeSimple MemoryMemory Buffer WindowIntegrationCalendar MCPMcp Client ToolIntegrationMy FunctionsMcp Client ToolTriggerMy Functions ServerMcp TriggerIntegrationRandom user dataDebug HelperSubworkflowGenerate random userdataTool WorkflowTransformReturn only some fieldsEdit FieldsWeb / APIJoke RequestHTTP RequestSubworkflowRandom JokesTool WorkflowAI & modelsOpenAI 4oOpenAI Chat Model

Node categories in this workflow

  • AI & models
  • Integration
  • Trigger
  • Routing
  • Transform
  • Subworkflow
  • Data store
  • Web / API

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.

Workflow node names, types, and operations
NodeCategoryTypeOperation
AI AgentAI & modelsAgentSee node parameters
SearchEventIntegrationGoogle Calendar ToolgetAll
CreateEventIntegrationGoogle Calendar ToolSee node parameters
UpdateEventIntegrationGoogle Calendar Toolupdate
DeleteEventIntegrationGoogle Calendar Tooldelete
Google Calendar MCPTriggerMcp TriggerSee node parameters
When Executed by Another WorkflowTriggerExecute Workflow TriggerSee node parameters
SwitchRoutingSwitchSee node parameters
Convert Text to Upper CaseTransformEdit FieldsSee node parameters
Convert Text to Lower CaseTransformEdit FieldsSee node parameters
Convert TextSubworkflowTool WorkflowSee node parameters
When chat message receivedTriggerChat TriggerSee node parameters
Simple MemoryData storeMemory Buffer WindowSee node parameters
Calendar MCPIntegrationMcp Client ToolSee node parameters
My FunctionsIntegrationMcp Client ToolSee node parameters
My Functions ServerTriggerMcp TriggerSee node parameters
Random user dataIntegrationDebug HelperSee node parameters
Generate random user dataSubworkflowTool WorkflowSee node parameters
Return only some fieldsTransformEdit FieldsSee node parameters
Joke RequestWeb / APIHTTP RequestSee node parameters
Random JokesSubworkflowTool WorkflowSee node parameters
OpenAI 4oAI & modelsOpenAI Chat ModelSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. 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

  • googleCalendarOAuth2Api
  • openAiApi

Workflow notes

Activate the workflow to make the MCP Trigger work

Activate the workflow to make the MCP Trigger work

In order to make the MCP server available, you need to activate the workflow.

Then copy the Production URL of the MCP Trigger and paste it in the corresponding MCP Client tool.

MCP Clients

MCP Clients

For every tool here you need to obtain he corresponding Production URL from the MCP Triggers on the right 👉

Try these example requests with the AI Agent

Try these example requests with the AI Agent

My Functions MCP

  1. Use your tools to convert this text to lower case: EXAMPLE TeXt

  2. Use your tools to convert this text to upper case: example TeXt

  3. Generate 5 random user data, please.

  4. Please obtain 3 jokes.

Calendar MCP

  1. What is my schedule for next week?

  2. I have a meeting with John tomorrow at 2pm. Please add it to my Calendar.

  3. Adjust the time of my meeting with John tomorrow from 2pm to 4pm, please.

  4. Cancel my meeting with John, tomorrow.

The My Functions MCP calls this sub-workflow every time.

The My Functions MCP calls this sub-workflow every time.

A subworkflow is a separate workflow that can be called by other workflows and is able to receive parameters. Learn more about sub-workflows here

Google Calendar tools require credentials

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.

Author

Author

Solomon

Freelance consultant from Brazil, specializing in automations and data analysis. I work with select clients, addressing their toughest projects.

Currently running the Scrapes community with Simon 💪

For business inquiries, email me at user@example.com Or message me on Telegram for a faster response.

Check out my other templates

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

Need help?

Need help?

For getting help with this workflow, please create a topic on the community forums here: https://community.n8n.io/c/questions/

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.

Build your first AI MCP Server

Build your first AI MCP Server

Purpose and structure

This folder contains the Build your first AI MCP Server workflow. Its executable nodes use agent, chatTrigger, debugHelper, executeWorkflowTrigger, googleCalendarTool, httpRequest, lmChatOpenAi, mcpClientTool, mcpTrigger, memoryBufferWindow, set, switch, toolWorkflow. 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 Executed by Another Workflow, When chat message received, My Functions Server

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/Debughelper/1184_Debughelper_HTTP_Create_Webhook.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 an MCP Server and Client

More in AI & research

"Hey Siri, Ask Agent" workflow#️⃣Nostr #damus AI Powered Reporting + Gmail + Telegram(G) - Email Classification