Set up n8n MCP: instance access, Server Trigger and Client
n8n offers several MCP paths. First decide whether an external client should call n8n or n8n should use another server.
Searching for n8n MCP leads to several different setups. Start by drawing an arrow from the calling program to the tool it needs. The integration selector first helps you decide whether the task calls for MCP, a webhook or an API request. This guide explains the documented n8n access paths. It does not confirm a working connection to your instance; check its version, reachability and permissions in your own test.
Three paths with different directions
| Path | Direction | Purpose |
|---|---|---|
| Instance access | External client → n8n | Enabled workflows through the instance endpoint |
| MCP Server Trigger | External client → workflow | Selected tools exposed by one workflow |
| MCP Client Tool | n8n → external server | Tools provided by another MCP server |
Do not confuse the client role with the server role. With the MCP Client Tool, n8n calls another service. A Server Trigger exposes operations to an outside caller. These roles determine where to look for the endpoint, authentication and error log. Record the direction alongside the configuration. Another person should be able to identify which program calls which operation without trying to infer the whole integration from a node name.
Limit instance access deliberately
The documented instance connection is enabled under Settings > Instance-level MCP. Copy the server address shown there; its documented path ends in /mcp-server/http. Review individual workflow exposure and the permissions of the account being used. The provider distinguishes searching, executing and editing. Visible search previews therefore do not automatically mean a workflow can be executed. The interface depends on your n8n version, so compare the steps with the linked current documentation.
Expose selected tools through the Server Trigger
The MCP Server Trigger exposes the attached tool nodes of a workflow. Its documentation distinguishes test and production URLs and lists Streamable HTTP and SSE, but no stdio access. Copy the appropriate URL from the node instead of constructing a path yourself. For the first test, one tool returning a fixed result from a test identifier is enough. Leave external changes out initially. This separates a working connection from correct credentials for additional apps.
Call external tools from n8n
For the MCP Client Tool, focus on the external server address. Check its documented authentication and limit included tools using the available selection. A filter in the interface does not establish the permissions of the underlying credentials at the destination. The authentication guide explains these layers. When a connection fails, first find the test operation on the calling side, then locate the corresponding request at the destination.
Record the version, connection direction and selected access path. Define a test identifier and its expected result.
Connect exactly one tool first and list it from the calling client. Check its name and input schema.
Call the tool once. Compare the input, returned result and corresponding n8n execution record.
Repeat the test using the intended operating URL. Separately check what happens when access is revoked and when an input is invalid.
Record more than “connection successful”: include the tool that was actually visible and the effect it produced. For a later handover, keep the endpoint without secrets, version and test result together. Use the troubleshooting tool for HTTP errors. If an event should start processing automatically, also read the MCP, API and webhook comparison. A reachable server alone does not establish an event trigger or a recurring schedule for your workflow.
- Is the instance URL the same as the Trigger URL?
- No. Copy the endpoint from the setup of the specific access path you have chosen.
- Do I need a Server Trigger to call an external server?
- When calling an external server, n8n is the client. Check the MCP Client Tool for that direction.
- Does a tool list prove a workflow works?
- No. It shows available functions. A controlled call is needed to check the actual effect.
- Why does the test URL stop working later?
- Test and production are separate access paths. Check the active test state or publication and use the appropriate URL.
- n8n instance-level MCP
Show retrieval command
curl -s https://docs.n8n.io/connect/connect-to-n8n-mcp-server - n8n MCP Server Trigger
Show retrieval command
curl -s https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-langchain.mcptrigger/ - n8n MCP Client Tool
Show retrieval command
curl -s https://docs.n8n.io/integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.toolmcp/