Connecting n8n Workflows via MCP to Chat Interfaces
The Model Context Protocol (MCP) provides a standardized protocol for exposing tools, workflows, and dynamic capabilities to LLM frontends. By exposing n8n workflows through an MCP Server trigger node, external AI clients can securely discover, trigger, and consume complex automation flows—such as vector store retrieval, deep research agents, or CRM record ingestions—directly from a conversational interface.
This guide details how to configure an n8n MCP Server setup and subsequently connecting it to two popular open-source AI user interfaces: LibreChat and OpenWebUI.
Prerequisites
Before starting, ensure you have the following components deployed and accessible:
n8n Environment: An active instance of n8n running within your secure GLBNXT workspace.
Target AI Clients:
An active LibreChat instance with admin access.
An active OpenWebUI instance with administrator access to Admin Settings.
Steps
Step 1: Setting up the n8n MCP Server Workflow
The starting point for this integration is a workflow configuration. This workflow acts as the central MCP host, listening for incoming tool calls from MCP clients and executing connected workflow tools.
Open your n8n instance and create a new workflow.
Add an
MCP Server Triggernode as your starting point.Select your preferred Authentication and Credentials, e.g. Header Auth (the rest of this guide uses Header Auth.
Choose a path, e.g.
glbnxt-n8n-mcp.You will need the
Production URLin later steps.If you already have workflows that you want to connect, take a look at the following steps:
Click on the '+' underneath your MCP Server Trigger node (look for
Tools).Select
Call n8n Workflow Tool.In the Workflow field change "From list" to "By ID".
Go to the workflow you want to connect to.
Look at the URL in your search bar.
The part after /workflow/...... is the ID you want to paste in the Workflow field.
Step 2: Connecting via MCP to AI User Interfaces (OpenWebUI / LibreChat)
[text]
Path A: Connecting via MCP to LibreChat
In your LibreChat application, select the MCP Settings icon on your side sidebar.

Click on the + icon, the Add MCP Server screen will pop up.

Configure your MCP in the pop up screen.
Enter your preferred
NameandDescription.Paste the
Production URLfrom Step 1 inMCP Server URL.Set
Transportto Streamable HTTPS.Set
Authenticationto API Key and choose Custom as Header Format.The Authentication Credential Name you chose in Step 1 is your Custom Header Name.
Select
I trust this applicationand clickCreate
Press the Connect icon. In the top of your screen, the message
MCP server 'your-name' initialized successfullywill appear.You are now able to connect and disconnect your MCP in the chat environment.

Path B: Connecting via MCP to OpenWebUI
In your OpenWebUI application, click on your User Icon.
Select Admin Panel and go to Settings.

Go to Integrations, here you will find Manage Tool Servers.

Click on the + icon, the Add Connection screen will pop up.

Press the OpenAPI button at the right upper corner, your screen will look like this.

Now you are ready to set up your MCP server.
Set your
Typeto MCP Streamable HTTP.Enter your preferred
Name,Description, andID.Paste the
Production URLfrom Step 1 intoURL.For
Authselect None.Then click on Advanced and under
Headerspaste the following json from you Authorization Credentials in n8n:Click on the Verify Connection button, if your connection is working you will see the message
Connection successfulin the right top corner of your screen.Click on Save, in the right top corner the message
Connection saved successfullywill appear.
Go to your chat environment and click on Integrations.

Select Tools and enable the MCP server.
You are now able to use your MCP server in the chat environment.
Troubleshooting & Verification
1. HTTP 401 / 403 Unauthorized Errors
Cause: Mismatch in header authentication credentials between the AI client and n8n.
Fix: Ensure the header key/value pair defined in LibreChat (
librechat.yaml) or OpenWebUI settings matches the Header Auth node connected to theMCP Server Triggerin n8n.
2. Workflow Active Status
Cause: n8n returns a
404 Webhook not registerederror.Fix: Ensure the
🟢 MCP n8nmain workflow is activated in n8n. Test URLs (/webhook-test/) only listen while the n8n node editor is actively execution-listening.
3. Tool Description Truncation / Verbatim Passing
Cause: LLM summarizes input instead of passing full verbatim text.
Fix: The tool descriptions inside
MCP n8n.jsonexplicitly require:"Pass the user's full message verbatim, preserving their original wording and phrasing. Do not summarize, shorten, or convert it into keywords."
Ensure this directive remains preserved inside the
descriptionfield of every@n8n/n8n-nodes-langchain.toolWorkflownode.
Need help? Contact the GLBNXT support team or ask a GLBNXT agent to walk you through the setup.
Last updated
Was this helpful?