Skip to main content
n8n is supported in Connect AI Embed when the ISV runs it server-side as part of its own backend automation, not when end-users of the ISV’s application run n8n themselves. In this model, the ISV mints and rotates the OAuth JWT bearer tokens that n8n uses to call the MCP service, the same way the ISV manages credentials for any other backend integration. If you are looking for a way to surface Connect AI data inside the application that your end-users interact with, n8n is not the right tool. Embed an MCP-capable agent or framework (such as LangChain or LlamaIndex) into your application directly.

​
Prerequisites

This page assumes:
  • You are an ISV, or an operator working on behalf of an ISV, building backend automation against Connect AI Embed.
  • The n8n instance is hosted and operated by the ISV (self-hosted or n8n Cloud), not by end-users of your application.
  • You have a process for generating and rotating OAuth JWT bearer tokens signed by the parent (OEM) account. The same token issuance and rotation discipline you use for other Embed integrations applies here.
Generate a JWT before configuring n8n. Copy it down—it acts as the password during authentication.

​
Connect to Connect AI

Follow these steps to connect to Connect AI Embed in n8n:
1
Sign in to your ISV-operated n8n instance: either n8n.io (n8n Cloud) or a self-hosted deployment. End-users of your application should never be issued credentials to this instance.
2
Create a workflow in n8n that uses the MCP client tool. The example below is an ISV-operated backend workflow that uses the MCP server as part of a larger automation. OpenAI is used as the Chat Model and Simple Memory as the Memory.
n8n Client Workflow
3
Configure the MCP Client node in the Workflow:
n8n Client MCP
4
Edit the Header Auth account. In the Connection tab, set the following properties to use Basic Authentication:
  • Name–enter Authorization.
  • Value–enter the value in the form Bearer OAUTH_JWT_TOKEN.
n8n Client Connection
5
(Optional) Give the AI Agent context. This establishes the AI Agent’s role and provides context for the conversation through the System Message parameter in the AI Agent node. By providing a system message that explicitly informs the agent about its role as an MCP Server expert and lists the available tools, you can enhance the agent’s understanding and response accuracy.The following is an example System Message:
You are an expert at using the MCP Client tool connected which is the Connect AI MCP Server. Always search thoroughly and use the most relevant MCP Client tool for each query. Below are the available tools and a description of each:
queryData: Execute SQL queries against connected data sources and retrieve results. When you use the queryData tool, ensure you use the following format for the table name: catalog.schema.tableName
execData: Execute stored procedures against connected data sources
getCatalogs: Retrieve a list of available connections from Connect AI. The connection names should be used as catalog names in other tools and in any queries to Connect AI. Use the `getSchemas` tool to get a list of available schemas for a specific catalog.
getColumns: Retrieve a list of available database columns from Connect AI for a specific catalog, schema, and table.
getExportedKeys: Retrieve a list of foreign key relationships from Connect AI for a specific catalog, schema, and table.
getImportedKeys: Retrieve a list of foreign key relationships from Connect AI for a specific catalog, schema, and table.
getIndexes: Retrieve a list of indexes from Connect AI for a specific catalog, schema, and table.
getPrimaryKeys: Retrieve a list of primary keys from Connect AI for a specific catalog, schema, and table.
getProcedures: Retrieve a list of stored procedures from Connect AI for a specific catalog and schema
getProcedureParameters: Retrieve a list of stored procedure parameters from Connect AI for a specific catalog, schema, and procedure.
getSchemas: Retrieve a list of available database schemas from Connect AI for a specific catalog. Use the `getTables` tool to get a list of available tables for a specific catalog and schema.
getTables: Retrieve a list of available database tables from Connect AI for a specific catalog and schema. Use the `getColumns` tool to get a list of available columns for a specific table.
6
Now that you created the Workflow in n8n and connected the MCP Client, you can interact with your data. The MCP Client node allows you to send queries and receive responses from the data source in real time.
7
Open the Workflow in n8n and execute it to start interacting with your data. You can ask questions, retrieve data, and perform actions on your data using the MCP Client node:
n8n Client Execute