What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
To connect a self-hosted n8n instance to an MCP client, expose n8n over a stable HTTPS domain, enable Settings > Instance-level MCP, choose the workflows that may be called, copy the generated server URL, and add that URL to your client. The standard endpoint format is https://<your-n8n-domain>/mcp-server/http. Authenticate with OAuth when the client supports it; otherwise send an n8n MCP token as a Bearer token.
Antihost offers VPS plans with one-click n8n, NVMe storage and a 14-day free trial.
n8n offers two different designs: instance-level MCP, which centrally publishes selected workflows, and the MCP Server Trigger node, which creates a server limited to one workflow. The right choice depends on whether you need a reusable, centrally administered tool catalog or one tightly scoped workflow.
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
What n8n and MCP provide together
Model Context Protocol (MCP) gives compatible AI applications a standard way to discover and call tools. In n8n, those tools are workflows. A client can discover an exposed workflow, send its defined inputs, and receive the workflow’s output without you building a separate integration for every AI application.
n8n’s built-in MCP server is hosted by your n8n installation. Your data and workflow execution remain on that instance, while the client reaches a network endpoint that you control. The endpoint must be reachable by the client; a hostname that works only inside your private LAN or Docker network will not work for a remote desktop or cloud-based client.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
There are two supported patterns:
- Instance-level MCP: administrators enable MCP once, select which workflows are available, and manage access and connected clients from instance settings.
- MCP Server Trigger node: an individual workflow contains the MCP server trigger and the tools wired to it. The exposed surface is limited to that workflow.
Both patterns can be useful. Instance-level MCP is normally the easier starting point when several workflows should be discoverable by multiple clients. The trigger-node pattern is better when one workflow should define a narrowly controlled MCP behavior.
Choose the MCP pattern before configuring anything
| Decision axis | Instance-level MCP | MCP Server Trigger node |
|---|---|---|
| Scope | Select workflows across the n8n instance | Tools wired into one workflow |
| Administration | Central settings, access controls, and connected-client management | Workflow-level credentials and configuration |
| Reuse | Convenient when several workflows should be discoverable | Useful when one workflow defines a focused MCP behavior |
| Self-hosted controls | Settings UI plus environment-variable controls | Node credentials and workflow settings |
Use instance-level MCP when you need a shared tool catalog
Choose this option if an administrator should decide which workflows are visible to AI clients, if more than one client will connect, or if you want one place to revoke access. It avoids duplicating an MCP server configuration inside every workflow.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsUse the MCP Server Trigger node for a deliberately narrow interface
Choose the trigger node when a single workflow should own the complete MCP contract. Only the tools and actions connected in that workflow are part of the server, which can make review and permission boundaries easier. You give up the broader, instance-wide workflow selection screen.
Self-hosted prerequisites
Prepare these items before opening n8n’s MCP settings:
- A reachable n8n host: the machine running n8n must be reachable from the client you plan to use.
- A stable HTTPS domain: serve the n8n editor and MCP endpoint through a consistent public or otherwise client-reachable domain. The documented examples use the editor-serving domain as the base of the MCP URL.
- Administrative permission: enabling instance-level MCP requires the n8n instance owner or an administrator.
- An MCP-capable client: the examples below cover Claude Code, Codex CLI, Cursor, and VS Code. Gemini CLI also supports documented HTTP or streamable-HTTP MCP configuration, but its exact command and file labels can change between releases.
- A deliberately chosen workflow set: review every workflow before exposing it. A workflow that can alter records, send messages, or call external services should not be published merely because it is convenient.
Do not substitute a local-only name such as an internal container hostname in the client configuration. The URL must resolve and complete an HTTPS connection from the client environment.
Enable instance-level MCP in n8n
- Sign in with an owner or administrator account. Open the n8n editor on the HTTPS domain that clients will use.
- Open the MCP settings page. Go to Settings > Instance-level MCP.
- Enable access. Select Enable MCP access. n8n then displays connection details, access controls, and controls for connected clients.
- Review the available workflows. Select only the workflows intended for AI access. Treat this as an allow-list, not as a convenience switch for the entire instance.
- Choose authentication. Use OAuth when the client supports n8n’s documented OAuth flow. If the client requires a token, generate an n8n MCP token in the MCP settings and plan to send it as an HTTP Bearer credential.
- Open Connect a client. Use the connection-details view to copy the server URL rather than retyping it. For a self-hosted installation, the documented pattern is
https://<your-n8n-domain>/mcp-server/http. - Record the URL without changing its path. Keep the
/mcp-server/httpsuffix. Do not replace it with the editor root, a webhook path, or a local Docker service name. - Add the endpoint to your client. Use the client-specific examples in the next section, then complete the client’s OAuth sign-in or configure its Bearer-token mechanism.
The n8n interface is version-sensitive. n8n documents the newer connection-details layout and per-client setup from version 2.33.0; older installations may show a simpler MCP settings screen. If a label in this guide is missing, check the installed n8n version before assuming MCP is unavailable.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Configure common MCP clients
All of the examples below use the same endpoint. Replace <your-n8n-domain> with the HTTPS domain that serves your self-hosted n8n editor. Keep authentication separate from the URL: do not append a token as a query parameter.
Claude Code
Run the documented HTTP transport command in a shell:
claude mcp add --transport http n8n https://<your-n8n-domain>/mcp-server/httpWhen prompted by the client, complete OAuth if enabled. If you use token authentication instead, configure the client to send Authorization: Bearer <YOUR_N8N_MCP_TOKEN>.
Codex CLI
Add the server with the URL option:
codex mcp add n8n --url "https://<your-n8n-domain>/mcp-server/http"Use the CLI’s authentication flow for OAuth, or its documented header/credential mechanism for the Bearer token. Keep the token in the client’s secret store or environment management rather than in a checked-in shell script.
Cursor
Cursor uses an mcp.json entry whose transport is streamable-http. A minimal URL-only entry has this shape:
{"mcpServers":{"n8n":{"type":"streamable-http","url":"https://<your-n8n-domain>/mcp-server/http"}}}Use Cursor’s current authentication controls to complete OAuth or supply the Bearer credential. Do not commit a file containing a live token to a project repository.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Visual Studio Code
VS Code’s MCP configuration uses an HTTP server entry. A minimal .vscode/mcp.json example is:
{"servers":{"n8n":{"type":"http","url":"https://<your-n8n-domain>/mcp-server/http"}}}Finish authentication through the MCP support included in your VS Code version. The transport type is http here, while Cursor’s documented entry uses streamable-http.
Gemini CLI and other clients
Use the client’s current MCP documentation to select HTTP or streamable HTTP and paste the same n8n server URL. The n8n side does not change: the endpoint remains HTTPS, the exposed workflow list remains the authority, and authentication is either the supported OAuth flow or the Bearer token header.
Authentication: OAuth or an MCP token
OAuth
OAuth is the recommended path in n8n’s setup examples when the client supports it. It lets the client complete an authorization flow instead of placing a long-lived token in a configuration file. Follow the sign-in and consent screens presented by the client after you add the server.
Bearer-token authentication
When OAuth is not available, n8n’s token mode expects this HTTP header:
Authorization: Bearer <YOUR_N8N_MCP_TOKEN>Generate the token through n8n’s MCP settings, copy it only into the client’s protected credential mechanism, and treat it exactly like a password. A token can grant access to every workflow you selected for MCP, so narrowing the workflow allow-list is as important as protecting the token itself.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
- Never place a live token in workflow descriptions, prompts, screenshots, issue tickets, or public repositories.
- Do not put the token in the endpoint URL or in a query string.
- When you suspect exposure, revoke or replace the token using n8n’s access controls and update the client.
- Keep separate credentials for separate clients when your operating process requires independent revocation.
Expose workflows without overexposing your instance
MCP makes a workflow callable by an AI client, not merely visible. Before selecting one, inspect its triggers, credentials, side effects, and output. A read-only lookup workflow is a safer first connection than one that deletes data, sends external messages, or changes billing and account records.
Define a small, explicit input contract
Give the workflow clear required inputs and predictable output fields. Avoid accepting arbitrary expressions, credential values, or unrestricted URLs from the model. Validate identifiers and permitted actions inside the workflow before any write operation.
Separate read and write capabilities
Publish read-only tools first. If a write action is necessary, put it in a separate workflow and expose it only to clients and users that need it. This keeps the instance-level selection understandable and makes a mistaken tool call easier to detect.
Review connected clients
The instance-level MCP page includes connected-client management. Periodically remove clients that are no longer used and verify that the remaining clients still need the workflows they can discover.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Using the MCP Server Trigger node instead
The trigger-node pattern keeps the MCP server inside one workflow rather than selecting workflows globally. Add the MCP Server Trigger node to the workflow, configure the node’s credentials and settings, and wire only the operations that should become tools. The resulting tool surface is the set of tools defined in that workflow.
This design is useful for a focused automation with a stable contract. It also places responsibility for authentication and workflow configuration at the workflow level, so document those settings with the workflow and review them whenever the workflow changes. Because the endpoint and labels can vary with the installed n8n release, use the node’s own connection details and current editor help instead of assuming that the instance-level URL or settings screen applies unchanged.
HTTPS, networking, and deployment considerations
Use a stable HTTPS origin
Terminate TLS at the reverse proxy or hosting layer in front of n8n and forward requests to the n8n service. The client should see a valid certificate for the domain in the URL. Keep that domain stable; changing it requires updating every client configuration.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Make the endpoint reachable from the actual client
Test from the machine or environment running the client, not only from the n8n server. A browser test from the server can succeed while a desktop client, remote development environment, or cloud-hosted CLI cannot resolve the hostname or pass the firewall.
Choose hosting appropriate to the exposure
A self-hosted VPS or managed Docker host can provide the public HTTPS endpoint, but you remain responsible for n8n updates, TLS, firewall policy, backups, and credential handling. The MCP feature does not remove those operational duties.
Safe validation procedure
n8n’s documentation describes configuration and permissions, not a universal performance benchmark or mandatory test script. Use these as operator checks and record the result for your own deployment:
- Check DNS and TLS. From the client environment, confirm that the n8n domain resolves and presents a certificate trusted by that client.
- Check the exact path. Verify that the configured URL ends in
/mcp-server/httpand useshttps://. - Start with one low-impact workflow. Expose a read-only or otherwise reversible workflow before adding write-capable tools.
- Confirm discovery. In the client, verify that the n8n server connects and that the expected workflow tool appears. If no tool is listed, recheck the instance-level selection or the tools wired to the trigger workflow.
- Exercise the input contract. Send a known-safe input and compare the returned fields with the workflow’s intended output.
- Inspect n8n execution history. Confirm that the expected workflow ran, with the expected credentials and no unexpected branches.
- Test failure handling. Try an invalid identifier or missing required field and verify that the workflow rejects it cleanly instead of performing a partial write.
Troubleshooting common failures
The client cannot connect or times out
- Confirm the client can resolve the public or private DNS name from its own network.
- Check that the firewall and reverse proxy allow HTTPS traffic to the n8n host.
- Replace a Docker service name,
localhost, or an internal hostname with the client-reachable domain. - Verify that the URL path is exactly
/mcp-server/http.
The client receives an authentication error
- Complete the OAuth flow again if the authorization session expired.
- For token mode, verify the header is exactly
Authorization: Bearer <YOUR_N8N_MCP_TOKEN>, with one space afterBearer. - Check that the token was not truncated, copied with quotation marks, or revoked.
- Confirm that the client is sending the credential to the same HTTPS origin shown in n8n’s connection details.
The server connects but no tools appear
- In instance-level MCP, confirm that at least one workflow is selected for access.
- In the trigger-node design, confirm that the workflow actually contains the MCP Server Trigger and its tool wiring.
- Check that the workflow is available according to its configuration and that the client has refreshed its MCP connection.
- Review the n8n version: older releases may use a simpler settings screen and different labels.
The MCP settings page or endpoint is missing
On self-hosted n8n, an administrator can disable MCP with the environment variable N8N_DISABLED_MODULES=mcp. That setting removes MCP endpoints and the related UI. If you expect MCP to be available, inspect the deployed environment for that variable and verify that the running instance is the version and configuration you intended.
Recommended Free Tools
The workflow runs but produces an unsafe result
Remove the workflow from the MCP allow-list, narrow its inputs, and separate read and write operations. MCP access should be restored only after the workflow validates inputs and limits side effects.
Administration and ongoing maintenance
- Keep the endpoint documented: record the canonical HTTPS URL and the transport expected by each client.
- Review workflow exposure after edits: adding a node or credential to a workflow can change the impact of an already published tool.
- Rotate credentials deliberately: replace tokens when staff, machines, or client projects change ownership.
- Monitor executions: use n8n’s execution history and your host’s logs to investigate unexpected calls.
- Patch the self-hosted stack: maintain n8n, the reverse proxy, TLS certificates, and the underlying host as separate operational responsibilities.
- Disable MCP when it is not needed: set
N8N_DISABLED_MODULES=mcpin the self-hosted environment to remove the MCP endpoints and related UI.
A practical rollout plan
- Put n8n behind a stable HTTPS domain and verify reachability from the intended client network.
- Enable instance-level MCP with an owner or administrator account.
- Select one read-only workflow with a narrow input and output contract.
- Connect one client using OAuth, or a protected Bearer token if OAuth is unavailable.
- Run the safe validation checks and inspect the resulting n8n execution.
- Add additional workflows one at a time, documenting each workflow’s permitted actions.
- Use the MCP Server Trigger node instead when a workflow-specific server gives you a clearer boundary than instance-level selection.
The essential configuration is small—the HTTPS URL, an authentication method, and an explicit workflow allow-list—but the security boundary is the workflow set you publish. Keep that set narrow, test from the real client network, and treat every MCP credential as production access.
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.
