AI Assistant which answers questions with a RAG MCP and a Search Engine MCP
Build an AI Agent which accesses two MCP Servers: a RAG MCP Server and a Search Engine API MCP Server.
This workflow contains community nodes that are only compatible with the self-hosted version of n8n.
Tutorial
Click here to watch the full tutorial on YouTube!
How it works
We build an AI Agent which has access to two MCP servers:
- An MCP Server with a RAG database (click here for the RAG MCP Server
- An MCP Server which can access a Search Engine, so the AI Agent also has access to data about more current events
Installation
-
In order to use the MCP Client, you also have to use MCP Server Template.
-
Open the MCP Client "MCP Client: RAG" node and update the SSE Endpoint to the MCP Server workflow
-
Install the "n8n-nodes-mcp" community node via settings > community nodes
-
ONLY FOR SELF-HOSTING: In Docker, click on your n8n container. Navigate to "Exec" and execute the below command to allow community nodes:
N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true
-
Navigate to Bright Data and create a new "Web Unlocker API" with the name "mcp_unlocker".
-
Open the "MCP Client" and add the following credentials:
How to use it
- Run the Chat node and start asking questions
More detailed instructions
Missed a step? Find more detailed instructions here: Personal Newsfeed With Bright Data and n8n
What is Retrievel Augmented Generation (RAG)?
Large Language Models (LLM's) are trained on data until a specific cutoff date. Imagine a model is trained in December 2023 based data until September 2023. This means the model doesn't have any knowledge about events which happened in 2024. So if you ask the LLM who was the Formula 1 World Champion of 2024, it doesn't know the answer.
The solution? Retrieval Augmented Generation. When using Retrieval Augmented Generation, a user's question is being sent to a semantic database. The LLM will use the information retrieved from the semantic database to answer the user's question.
What is Model Context Protocol (MCP)?
MCP is a communication protocol which is used by AI agents to call tools hosted on external servers.
When an MCP client communicates with an MCP server, the server will provide an overview of all its tools, prompts and resources. The MCP server can then choose which tools to execute (based on the user's request) and execute the tools.
An MCP client can communicate with multiple MCP servers, which can all host multiple tools.
AI Assistant with RAG, MCP, and Search Engine Capabilities
This n8n workflow creates a powerful AI assistant that can answer questions using a combination of Retrieval-Augmented Generation (RAG) via the Model Context Protocol (MCP) and a search engine tool. It's designed to provide comprehensive and context-aware responses to user queries.
What it does
This workflow automates the process of answering user questions by:
- Listening for chat messages: It triggers whenever a new chat message is received, acting as the entry point for user queries.
- Maintaining conversational context: It uses a simple memory buffer to keep track of the conversation history, allowing the AI to understand the ongoing dialogue.
- Leveraging an AI Agent: An AI Agent orchestrates the process, deciding whether to use a search engine or the Model Context Protocol (MCP) based on the user's query and the available tools.
- Utilizing a Search Engine (via MCP Client Tool): When a search is needed, the AI Agent activates the MCP Client Tool, which can be configured to interact with a search engine to retrieve relevant information.
- Utilizing Retrieval-Augmented Generation (RAG) (via MCP Client Tool): For questions requiring knowledge from a specific context, the AI Agent uses the MCP Client Tool to perform RAG, fetching information from a defined knowledge base.
- Generating responses with an OpenAI Chat Model: The core of the AI's intelligence is powered by an OpenAI Chat Model, which processes the user's query, conversational context, and any retrieved information to formulate a coherent and helpful response.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance to host and execute the workflow.
- OpenAI API Key: For the "OpenAI Chat Model" node to generate AI responses.
- MCP Client Tool Configuration: The "MCP Client Tool" node requires configuration to connect to your Model Context Protocol (MCP) endpoint and potentially a search engine. This might involve setting up credentials or specific API endpoints within the node's settings.
- Chat Service Integration: The "When chat message received" trigger needs to be connected to a chat service (e.g., Slack, Telegram, Discord, custom chat UI) to receive user messages.
Setup/Usage
- Import the workflow: Download the JSON provided and import it into your n8n instance.
- Configure Credentials:
- OpenAI Chat Model: Provide your OpenAI API Key in the credentials section for this node.
- MCP Client Tool: Configure the MCP Client Tool with the necessary API keys, endpoints, or other details to connect to your MCP instance and any integrated search engine.
- Configure Chat Trigger: Set up the "When chat message received" trigger to listen for messages from your desired chat platform.
- Activate the workflow: Once configured, activate the workflow to start processing chat messages and answering questions.
Related Templates
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
AI-powered code review with linting, red-marked corrections in Google Sheets & Slack
Advanced Code Review Automation (AI + Lint + Slack) Who’s it for For software engineers, QA teams, and tech leads who want to automate intelligent code reviews with both AI-driven suggestions and rule-based linting — all managed in Google Sheets with instant Slack summaries. How it works This workflow performs a two-layer review system: Lint Check: Runs a lightweight static analysis to find common issues (e.g., use of var, console.log, unbalanced braces). AI Review: Sends valid code to Gemini AI, which provides human-like review feedback with severity classification (Critical, Major, Minor) and visual highlights (red/orange tags). Formatter: Combines lint and AI results, calculating an overall score (0–10). Aggregator: Summarizes results for quick comparison. Google Sheets Writer: Appends results to your review log. Slack Notification: Posts a concise summary (e.g., number of issues and average score) to your team’s channel. How to set up Connect Google Sheets and Slack credentials in n8n. Replace placeholders (<YOURSPREADSHEETID>, <YOURSHEETGIDORNAME>, <YOURSLACKCHANNEL_ID>). Adjust the AI review prompt or lint rules as needed. Activate the workflow — reviews will start automatically whenever new code is added to the sheet. Requirements Google Sheets and Slack integrations enabled A configured AI node (Gemini, OpenAI, or compatible) Proper permissions to write to your target Google Sheet How to customize Add more linting rules (naming conventions, spacing, forbidden APIs) Extend the AI prompt for project-specific guidelines Customize the Slack message formatting Export analytics to a dashboard (e.g., Notion or Data Studio) Why it’s valuable This workflow brings realistic, team-oriented AI-assisted code review to n8n — combining the speed of automated linting with the nuance of human-style feedback. It saves time, improves code quality, and keeps your team’s review history transparent and centralized.
Auto-reply & create Linear tickets from Gmail with GPT-5, gotoHuman & human review
This workflow automatically classifies every new email from your linked mailbox, drafts a personalized reply, and creates Linear tickets for bugs or feature requests. It uses a human-in-the-loop with gotoHuman and continuously improves itself by learning from approved examples. How it works The workflow triggers on every new email from your linked mailbox. Self-learning Email Classifier: an AI model categorizes the email into defined categories (e.g., Bug Report, Feature Request, Sales Opportunity, etc.). It fetches previously approved classification examples from gotoHuman to refine decisions. Self-learning Email Writer: the AI drafts a reply to the email. It learns over time by using previously approved replies from gotoHuman, with per-classification context to tailor tone and style (e.g., different style for sales vs. bug reports). Human Review in gotoHuman: review the classification and the drafted reply. Drafts can be edited or retried. Approved values are used to train the self-learning agents. Send approved Reply: the approved response is sent as a reply to the email thread. Create ticket: if the classification is Bug or Feature Request, a ticket is created by another AI agent in Linear. Human Review in gotoHuman: How to set up Most importantly, install the gotoHuman node before importing this template! (Just add the node to a blank canvas before importing) Set up credentials for gotoHuman, OpenAI, your email provider (e.g. Gmail), and Linear. In gotoHuman, select and create the pre-built review template "Support email agent" or import the ID: 6fzuCJlFYJtlu9mGYcVT. Select this template in the gotoHuman node. In the "gotoHuman: Fetch approved examples" http nodes you need to add your formId. It is the ID of the review template that you just created/imported in gotoHuman. Requirements gotoHuman (human supervision, memory for self-learning) OpenAI (classification, drafting) Gmail or your preferred email provider (for email trigger+replies) Linear (ticketing) How to customize Expand or refine the categories used by the classifier. Update the prompt to reflect your own taxonomy. Filter fetched training data from gotoHuman by reviewer so the writer adapts to their personalized tone and preferences. Add more context to the AI email writer (calendar events, FAQs, product docs) to improve reply quality.