Build and operate n8n workflows from Claude with Gemini and MCP tools

Workflow preview

100%

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

1. Workflow Overview

Quick Overview This workflow exposes an MCP server endpoint for Claude Desktop and provides tools to build new n8n workflows from plain English prompts using Google Gemini, plus tools to list, insp...

Best for

Engineering automation workflows
AI Chatbot automation workflows
advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.executeworkflowtrigger, @n8n/n8n-nodes-langchain.googlegemini, n8n-nodes-base.code, n8n-nodes-base.httprequest, n8n-nodes-base.stickynote, @n8n/n8n-nodes-langchain.mcptrigger, @n8n/n8n-nodes-langchain.toolworkflow

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Țugui Dragoș.

Original n8n.io source

1.1 Workflow description

Title: Build and operate n8n workflows from Claude with Gemini and MCP tools
Workflow name: Build and operate n8n workflows from Claude with Gemini and MCP tools

Quick Overview

This workflow exposes an MCP server endpoint for Claude Desktop and provides tools to build new n8n workflows from plain-English prompts using Google Gemini, plus tools to list, inspect, activate/deactivate workflows and review executions via the n8n Public API.

How it works

Receives MCP tool requests on the MCP Server Trigger endpoint (path concierge) from a connected MCP client such as Claude Desktop.
Routes “build workflow” requests to a sub-workflow that sends the plain-English description to Google Gemini and asks it to return strict n8n workflow JSON (nodes and connections).
Normalizes the generated JSON, adds required workflow fields, and creates the new workflow by calling the n8n Public API.
Returns a compact result containing the created workflow ID and a link, leaving the workflow inactive for review.
Routes “operate” requests (list/get workflows, activate/deactivate, list/get executions) to a shared sub-workflow that maps each action to the correct n8n Public API endpoint.
Calls the n8n Public API with an API-key header and returns a trimmed JSON response for lists and execution data.

Setup

Import the MCP server workflow plus the two tool sub-workflows (Concierge Build Workflow and Concierge n8n Operate) and re-link each Tool Workflow node to the correct imported workflow ID.
Create an n8n API key and configure an HTTP Header Auth credential that sends it as X-N8N-API-KEY for the HTTP Request nodes.
Replace the https://YOUR_N8N_DOMAIN placeholders in the sub-workflows with your n8n instance base URL (with the Public API enabled).
Add Google Gemini API credentials for the node that generates workflow JSON.
Activate only the MCP server workflow to expose the Production URL, then configure Claude Desktop (for example via mcp-remote) to call that URL.
For production use, switch the MCP trigger authentication to Bearer Auth and set the same token in your MCP client configuration.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Receive Build Request

Type / Role: n8n-nodes-base.executeWorkflowTrigger - executeWorkflowTrigger
Config choices: Version 1.2

Block 2 - Generate Workflow JSON

Type / Role: @n8n/n8n-nodes-langchain.googleGemini - googleGemini
Config choices: Version 1.2

Block 3 - Normalize Workflow

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 4 - Create Workflow

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.4

Block 5 - Build Result

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 6 - Sticky Note 7999b84a

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 7 - Sticky Note 32553e69

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 8 - Sticky Note 5c5f0c62

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 9 - Build Request

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 10 - Call n8n API

Type / Role: n8n-nodes-base.httpRequest - httpRequest
Config choices: Version 4.4

Block 11 - Shape Response

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 12 - Sticky Note e7a636c9

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 13 - Sticky Note f7a7db8f

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 14 - MCP Server: Concierge

Type / Role: @n8n/n8n-nodes-langchain.mcpTrigger - mcpTrigger
Config choices: Version 1.1

Block 15 - List Workflows

Type / Role: @n8n/n8n-nodes-langchain.toolWorkflow - toolWorkflow
Config choices: Version 2.2

Block 16 - Get Workflow

Type / Role: @n8n/n8n-nodes-langchain.toolWorkflow - toolWorkflow
Config choices: Version 2.2

Block 17 - Activate Workflow

Type / Role: @n8n/n8n-nodes-langchain.toolWorkflow - toolWorkflow
Config choices: Version 2.2

Block 18 - Deactivate Workflow

Type / Role: @n8n/n8n-nodes-langchain.toolWorkflow - toolWorkflow
Config choices: Version 2.2

Block 19 - List Executions

Type / Role: @n8n/n8n-nodes-langchain.toolWorkflow - toolWorkflow
Config choices: Version 2.2

Block 20 - Get Execution

Type / Role: @n8n/n8n-nodes-langchain.toolWorkflow - toolWorkflow
Config choices: Version 2.2

Block 21 - Build Workflow

Type / Role: @n8n/n8n-nodes-langchain.toolWorkflow - toolWorkflow
Config choices: Version 2.2

Block 22 - Sticky Note f2006dc0

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 23 - Sticky Note 60687e1a

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 24 - Sticky Note a7bdfa9a

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Showing the first 24 of 26 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow	Build and operate n8n workflows from Claude with Gemini and MCP tools
Complexity	advanced
Nodes	26
Categories	Engineering, AI Chatbot
Author	Țugui Dragoș
Published	07 Jun 2026

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/16165/16165.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source Engineering workflows AI Chatbot workflows

Frequently asked questions

What does Build and operate n8n workflows from Claude with Gemini and MCP tools do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Engineering, AI Chatbot use case.

Țugui Dragoș

18 workflows

Nodes

n8n-nodes-base.executeworkflowtrigger @n8n/n8n-nodes-langchain.googlegemini n8n-nodes-base.code n8n-nodes-base.httprequest n8n-nodes-base.stickynote @n8n/n8n-nodes-langchain.mcptrigger @n8n/n8n-nodes-langchain.toolworkflow

Complexity

advanced

Published 07 Jun 2026

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/16165/16165.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Build self-improving agent skills with cognee

## Quick overview A self-improving loop for agent skills, powered by the cognee Verified Node. When a skill's review scores below your threshold, it proposes a rewrite, and you approve the before/after diff before it's applied. No code required. ## How it works 1. Execute your workflow. 2. Set the demo inputs (skill name, dataset name, skill procedure markdown, review task text, and the score threshold). 3. Ingest the skill into cognee. 4. Cognee reviews the skill’s performance and returns a JSON with a score and gaps. 5. If the score is below the threshold, the workflow requests a cognee improvement proposal for the skill. 6. The workflow retrieves the full proposal from cognee and builds a human-readable before/after diff. 7. If the proposal is approved, the workflow applies the improvement in cognee, fetches the updated skill, and outputs the updated procedure and diff. ## Setup 1. Create a cognee API credential in n8n and use it in all cognee nodes (Ingest Skill, Review Skill, Propose Improvement, Get Proposal, Apply Improvement, Get Skill). Information for the credential (URL and API key) can be found in your Cognee Cloud account. 2. Update the skill parameters (skill_name, dataset_name, skill_markdown, task_text, score_threshold, and approved) to match your use case. 3. Ensure the referenced cognee dataset name exists so the skill can be stored and retrieved consistently.

View

Orchestrate multi-agent energy optimization with OpenAI GPT and Claude

## Quick Overview This workflow runs manually to orchestrate multi-agent analysis for a thermodynamic system, using OpenAI and Anthropic models to interpret sensor inputs, optimize energy usage, plan and execute tasks, validate results, and send an HTTP alert if validation fails. ## How it works 1. Starts when you manually trigger the workflow with initial system state, temperature, energy budget, and a task queue. 2. Uses OpenAI (GPT-5-mini) to analyze the provided sensor context, detect anomalies, and output structured sensor readings with confidence scores. 3. Uses OpenAI (GPT-5-mini) plus a calculator and custom energy-analysis code tool to compute efficiency/entropy metrics and propose an optimized energy allocation. 4. Uses OpenAI (GPT-5-mini) to build an execution plan and energy estimate for the queued tasks based on the optimized budget and sensor state. 5. Uses Anthropic (Claude Sonnet) to execute the planned task sequence within the estimated energy limit and return structured outcomes and actual energy usage. 6. Uses Anthropic (Claude Sonnet) to validate thermodynamic compliance by comparing planned vs. actual energy and generating recommendations. 7. If validation passes, compiles a final system report and returns the final system state; if validation fails, generates recalibration parameters and posts a JSON alert to an external webhook endpoint. ## Setup 1. Add credentials for OpenAI (Chat) and Anthropic (Chat) so the Perception, Energy Optimization, Planning, Execution, Validation, and Recalibration agents can run. 2. Replace the placeholder alert webhook URL in the HTTP Request step and configure HTTP Header Auth credentials for the target alerting endpoint. 3. Provide the required input fields on trigger (systemState, temperature, energyBudget, and taskQueue) or adjust the prompts to match your data structure. 4. If your execution step needs real environment context, add or connect a node that supplies the referenced environment data (the workflow currently references “Fetch Environment Data” but does not include it).

View

Optimize maritime routes and disruption response with OpenAI and Slack

## Quick Overview This workflow runs every 15 minutes to pull vessel telemetry/AIS data, enrich it with port and weather context, and use OpenAI to detect disruptions, simulate route alternatives, and generate an executive briefing that requires human approval before notifying teams in Slack. ## How it works 1. Runs every 15 minutes on a schedule. 2. Fetches fleet vessel telemetry and AIS data from a configured HTTP API. 3. Retrieves weather forecast and port congestion context for each vessel/route from a second HTTP API. 4. Uses OpenAI to analyze telemetry against historical baselines and classify any operational anomalies with severity and confidence. 5. Uses OpenAI to aggregate anomaly, weather, and port context into risk factors, urgency, and an action category. 6. Uses OpenAI to simulate 2–3 routing and speed options, estimating cost, emissions, fuel, duration, and weather risk, and selects a recommended route. 7. Generates an executive briefing with compliance and master-authority notes, pauses for human approval via an n8n form, and then posts the decision and recommendation to a Slack channel. ## Setup 1. Add OpenAI API credentials for the three OpenAI chat model steps. 2. Configure HTTP Header Auth credentials and replace the placeholder URLs and query parameters for your AIS/telemetry API and your weather/port API. 3. Ensure the upstream APIs return the fields referenced in the prompts (for example position, speed, fuel consumption, historical baselines, forecast, and port congestion). 4. Connect a Slack OAuth2 credential and select the target channel for posting the approved briefing. 5. Test the approval form step in n8n and confirm who will receive and complete approvals before enabling the workflow.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Build and operate n8n workflows from Claude with Gemini and MCP tools

Workflow preview

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Quick Overview

How it works

Setup

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Receive Build Request

Block 2 - Generate Workflow JSON

Block 3 - Normalize Workflow

Block 4 - Create Workflow

Block 5 - Build Result

Block 6 - Sticky Note 7999b84a

Block 7 - Sticky Note 32553e69

Block 8 - Sticky Note 5c5f0c62

Block 9 - Build Request

Block 10 - Call n8n API

Block 11 - Shape Response

Block 12 - Sticky Note e7a636c9

Block 13 - Sticky Note f7a7db8f

Block 14 - MCP Server: Concierge

Block 15 - List Workflows

Block 16 - Get Workflow

Block 17 - Activate Workflow

Block 18 - Deactivate Workflow

Block 19 - List Executions

Block 20 - Get Execution

Block 21 - Build Workflow

Block 22 - Sticky Note f2006dc0

Block 23 - Sticky Note 60687e1a

Block 24 - Sticky Note a7bdfa9a

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions