Free tools Windows power users keep installed
One-click scans. No signup required.
There are two ways to connect MCP and n8n: make an n8n workflow call tools on an external MCP server, or expose n8n workflow tools so an external MCP client can call them. Choose the direction first. Then choose the right n8n node or instance-level connection for the scope and invocation style you need.
Choose the direction of the connection
MCP (Model Context Protocol) connects clients with tools provided by servers. In an n8n integration, either side can initiate the tool call:
- n8n calls an external MCP server: use MCP Client for tools that run as ordinary workflow steps, or MCP Client Tool when an n8n AI Agent should decide when to call them.
- An external MCP client calls n8n: use MCP Server Trigger to expose tools from one workflow, or instance-level MCP access to make selected workflows available across an n8n instance.
These are different connection patterns, not interchangeable node choices. The n8n documentation describes the MCP Client as a way to use MCP tools as regular workflow steps (MCP Client documentation).
Have n8n call an external MCP server
Use MCP Client for fixed workflow steps
Choose the MCP Client node when the workflow itself should call a remote tool at a particular point in its execution. Configure the server transport and MCP endpoint URL, choose the required authentication method, select an available tool, and supply its inputs. The node retrieves the remote server’s available tools, so select the one that fits the task and provide its parameters manually or as JSON.
#1 Best Overall
- Add an MCP Client node to the workflow.
- Set the transport and endpoint URL required by the remote server.
- Configure authentication according to that server’s requirements.
- Select the tool the workflow should run and provide its inputs.
- Run the workflow and inspect the node output; if connection or authorization fails, check the server’s endpoint, transport, and credential requirements.
Use this pattern when the tool call is part of the workflow’s defined sequence—for example, after a trigger and before a later processing step.
Use MCP Client Tool when an n8n AI Agent chooses tools
Choose MCP Client Tool when the MCP tools should be available to an n8n AI Agent rather than invoked as a fixed step. Configure which tools the agent may use: all remote tools, selected tools, or all tools except those you exclude. The node documentation lists bearer, generic header, multiple-header, and OAuth2 credentials; which one is appropriate depends on the server.
- Add an AI Agent and connect an MCP Client Tool to its tool input.
- Set the remote MCP connection and choose the tool-access scope.
- Configure the credential type the remote server expects.
- Test with a request that should require the tool, then verify the agent’s result and the tool call’s inputs.
For node-specific fields and supported credential choices, consult the MCP Client Tool documentation. Do not assume one authentication mode works for every MCP server.
Expose n8n tools to an external MCP client
Use MCP Server Trigger for one workflow
MCP Server Trigger is the workflow-level option: it provides an MCP entry point for tools in that workflow, including workflows exposed through Custom n8n Workflow Tool. The documented transports are Server-Sent Events (SSE) and Streamable HTTP. The trigger does not currently support standard input/output (stdio), so a client that can connect only through stdio cannot use this trigger directly.
Recommended Free Tools
- Open the workflow that should provide tools and add an MCP Server Trigger.
- Configure the trigger and the tools the workflow should expose.
- Choose a supported transport and configure the connection and authentication details for the client.
- Activate or otherwise make the workflow available according to your n8n deployment, then configure the external MCP client with the server connection details shown by n8n.
- Call a tool from the client and confirm that the expected workflow tool runs.
Exact fields and available options can vary with the installed n8n version; use the current MCP Server Trigger documentation when configuring the node.
Use instance-level MCP for selected workflows across the instance
Instance-level MCP is the better fit when a client should connect to the n8n instance and access a selection of workflows rather than one workflow’s trigger. n8n documents centralized authentication and workflow selection for this option. The setup page directs administrators to enable MCP access, then copy the Server URL from Settings > Instance-level MCP > Connect a client. The documented URL ends in /mcp-server/http.
Rank #3
- Enable instance-level MCP access in n8n.
- Select which workflows are available through that access.
- Open Settings > Instance-level MCP > Connect a client and copy the Server URL.
- Enter that URL and the required authentication in the MCP client, following the client-specific instructions.
- Test a tool call against a workflow that has been selected for access.
Follow the current instance-level MCP setup guide and its client examples for exact client configuration. The interactive “Connect a client” dialog is documented in those examples for n8n 2.33.0 and later; do not assume that UI is present in older versions.
Pick the right n8n MCP pattern
| What you want | Use | Scope and behavior |
|---|---|---|
| Run a remote MCP tool at a defined point in a workflow | MCP Client | External server tools used as regular workflow steps |
| Let an n8n AI Agent decide whether to call remote tools | MCP Client Tool | Agent-accessible remote tools, with all, selected, or excluded tools configured |
| Let a client call tools from one n8n workflow | MCP Server Trigger | Workflow-level MCP entry point; SSE and Streamable HTTP, not stdio |
| Let a client access selected workflows across an n8n instance | Instance-level MCP | Instance connection with centralized authentication and workflow selection |
Before building, answer four questions: which side initiates the call, whether the tools belong to one workflow or selected workflows across an instance, whether calls are fixed steps or agent-selected, and which transport and authentication methods both ends support.
Check compatibility, transport, and authentication
Do not infer transport support from the phrase “MCP support.” In particular, n8n documents SSE and Streamable HTTP for MCP Server Trigger and explicitly excludes stdio. For client nodes, verify the configured transport against both the n8n node’s documentation and the remote server’s requirements.
Protocol guidance also changes over time. The MCP project’s release article dated 2026-07-28 discusses changes to transport, session behavior, authorization, and deprecation policy (MCP specification release notes). That release is context, not an n8n compatibility matrix. Check your installed n8n version and the remote implementation’s documentation before relying on a protocol capability. For n8n’s product-level distinction between the trigger and instance approach, see its MCP overview.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If the MCP tools you need are website screenshots rather than browser automation generally, ScreenshotNeo offers an MCP server for AI agents and a screenshot API. Its tools include take_screenshot, get_page_info, and capture_pdf. That is a separate option from wiring a generic external MCP server into an n8n workflow.
For a direct screenshot API call, use this cURL example; replace the target URL and your API key. See the ScreenshotNeo documentation for request options.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Best Value
- Book - powershell for sysadmins: workflow automation made easy
- Language: english
- Binding: paperback
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp- Cookie/consent banners, newsletter popups, and chat widgets are removed before capture; each step can be turned off.
- Bot checks/CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed; responses identify the page verdict and billing status in headers.
- The MCP server lets AI agents, including Claude and Cursor, use screenshot and page-information tools.
- The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 shots.
Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month without a card.
Troubleshoot common connection failures
The client cannot connect
- Check the endpoint: confirm that the URL belongs to the selected server or n8n connection. For instance-level access, copy the URL from the documented settings page rather than typing it from memory.
- Check transport compatibility: a client configured for stdio will not connect through MCP Server Trigger, which documents SSE and Streamable HTTP instead.
- Check availability: confirm that the workflow or instance-level access is enabled and reachable from the client.
Authentication fails
Verify the server’s required authorization method and configure the matching credential in n8n or the MCP client. With MCP Client Tool, the documented choices include bearer, generic header, multiple headers, and OAuth2; that list does not mean each remote server accepts every method. For instance-level setup, follow the authentication instructions in n8n’s connection guide and the client-specific example.
The tool is missing or cannot be called
- For MCP Client, confirm the remote server exposes the expected tool and refresh or recheck the available tool list.
- For MCP Client Tool, check whether the tool is excluded by the configured all/selected/excluded access scope.
- For MCP Server Trigger, confirm the intended tool belongs to the workflow exposed by that trigger.
- For instance-level MCP, confirm the workflow is among those selected for access.
A feature works on one side but not the other
Compare the installed n8n node’s documented behavior with the remote implementation and client. A protocol release or a general MCP feature does not establish support in every n8n version, transport, or server. Check both ends’ current documentation before changing workflow logic.
FAQ
Can n8n both call and expose MCP tools?
Yes. Use client-side nodes for outbound calls and a Server Trigger or instance-level access for inbound client calls; they address separate directions.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsDo I need to buy hardware to connect MCP and n8n?
No specific physical purchase is established as necessary for this software configuration. n8n documents both Cloud and self-hosted deployment choices; the appropriate deployment depends on your existing setup.
Where should I check for current configuration details?
Use the linked documentation for the specific node or instance-level setup you chose, plus the remote server’s own instructions for its endpoint, transport, and authorization requirements.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
