n8n
Who is this for?
- For n8n users (Cloud or self-hosted) who want to query their Leexi calls and documentation from a workflow or an AI agent.
Permissions and licenses
- A recent n8n instance, reachable over HTTPS (or locally on
localhost), with the MCP Client Tool node and MCP OAuth2 authentication. - An active Leexi account with at least one processed call.
How to use it
MCP server URL: https://api.leexi.ai/mcp
Leexi is not yet listed in n8n's MCP servers registry: add it as a custom MCP server by following the steps below.
Add an MCP Client Tool node to your AI agent
In your workflow, add an AI Agent node (or open an existing one), click the + on its Tool output, then choose MCP Client Tool.
Configure the endpoint
In the MCP Client Tool node, fill in:
- Endpoint:
https://api.leexi.ai/mcp - Server Transport: HTTP Streamable
- Authentication: MCP OAuth2
Create the MCP OAuth2 credential
In Credential to connect with, choose Create new credential. n8n opens a credential of type MCP OAuth2 API:
- leave Use Dynamic Client Registration enabled: Leexi supports DCR, no Client ID or secret is required;
- Server URL:
https://api.leexi.ai/mcp; - leave Resource URL empty.
Click Connect my account.
Authorize access
A Leexi window opens: sign in with your Leexi account and click Authorize. Back in n8n, the credential is marked as connected: save it.
Choose the tools exposed to the agent
Back in the MCP Client Tool node, n8n loads the list of Leexi tools. In Tools to Include, keep All to expose all four tools, or choose Selected to expose only some of them.
Give the agent an input and test
An n8n AI agent needs an instruction to trigger a tool: connect a When chat message received trigger (or set the Prompt of the AI Agent node) and a chat model (OpenAI Chat Model, Anthropic Chat Model…). Open the chat and ask a question, for example "Summarize my last 5 calls with TechCorp": the MCP Client Tool node shows up in the execution logs.
Going further
What you can do once connected
| Tool | What it does |
|---|---|
query_calls | Searches your calls by date, participant, team, client, and more |
fetch_call_details | Retrieves the full summaries, follow-up tasks, and metadata of specific calls |
query_resources | Searches Leexi's product documentation |
fetch_resource_details | Retrieves the full content of documentation articles |
Call a Leexi tool without an AI agent
The MCP Client node (a regular node, not to be confused with the MCP Client Tool sub-node) runs a Leexi tool as an ordinary workflow step: pick the tool in Tool, then fill in its parameters. It is configured with the same endpoint, the same transport and the same MCP OAuth2 API credential.
Self-hosted n8n instance
During dynamic registration, n8n declares its OAuth callback URL to Leexi, built from your instance's public URL. Leexi only accepts HTTPS callback URLs, or HTTP on localhost only. An instance served over HTTP on another domain name or an IP address will be rejected: expose it over HTTPS before connecting Leexi.
Frequently asked questions
localhost) and that its public URL is configured correctly. Also update n8n: older versions of the MCP Client Tool node did not support PKCE, which Leexi requires, and failed with the message "Insufficient parameters for OAuth2 callback".Make sure your account contains processed calls with completed transcriptions, and try broadening your search by removing filters.
If the issue persists, contact Leexi support at support@leexi.ai or via the support assistant in Ask Leexi on app.leexi.ai.
Things to watch out for
- The MCP OAuth2 API credential is tied to the Leexi account that authorized it: any workflow using it queries Leexi with that user's permissions, even when it is run or shared by other members of your n8n workspace.
- Data retrieved from Leexi is sent to the chat model configured in your agent and processed under that AI provider's terms.
- Access is strictly read-only: nothing can be created, modified or deleted through the MCP server.