Our grade: 4 checks
Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.
Community rating
- 5 0
- 4 4
- 3 5
- 2 8
- 1 1
Trust in production
- Trust it - 11%
- With caveats - 44%
- Wouldn't - 44%
44% would recommend this server
How reviewers scored it
- Setup & docs 2.7
- Auth experience 3.4
- Reliability 2.7
- Maintainer responsiveness 2.3
Why it got a D
A client node only: it lets n8n call other MCP servers. Exposing workflows as MCP tools is n8n's own built-in feature, which supports OAuth. Its stdio mode starts whatever command is configured, and HTTP auth is static headers only. Biggest deduction: no commit or release since January 2026, and n8n's own MCP nodes now cover most of what it does.
How to connect
n8n → Settings → Community Nodes → Install → n8n-nodes-mcp (agent use also needs N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true)Is n8n MCP client node safe?
Is n8n MCP client node safe to use?
n8n MCP client node grades D (notable weaknesses - review closely). Login is optional, so check that it is turned on in your setup. Updates are rare or unknown, so fixes may be slow to arrive. It shells out to helper programs or serves HTTP without enforced TLS, so keep it local and isolated.
Does n8n MCP client node have known vulnerabilities?
Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.
Does n8n MCP client node support authentication?
Optionally. It can run with a login, but it does not require one, so turn it on.
Alternatives in Workflow Automation
- A Make MCPOfficial hosted Make server that exposes your scenarios (and, on paid plans, management tools) to agents.
- A NeverApply MCP ServerOfficial hosted server to search and match jobs, tailor resumes, prep for interviews and apply to jobs you approve, with separate read, write and apply OAuth scopes.
- A Repostit MCP ServerOfficial hosted server to draft social posts and carousels, schedule or publish them to your connected accounts, set up cross-posting workflows and check delivery.
- A n8n MCP Server (instance-level)n8n's built-in MCP server. Lets an agent search, run, and (from 2.13) build workflows on your instance.
- B Zapier MCPOfficial hosted Zapier server that lets an agent run actions across thousands of connected apps.
Embed this badge
[](https://trustedmcp.io/servers/n8n-nodes-mcp)<a href="https://trustedmcp.io/servers/n8n-nodes-mcp"><img src="https://trustedmcp.io/badge/n8n-nodes-mcp.svg" alt="TrustedMCP grade D" height="80"></a>Community reviews
Useful, with a few rough edges
I like it, with reservations. The OAuth flow worked first time in Claude Code. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. Keep permissions tight and it is a good tool.
Used for Triggering workflows from chat
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Decent, not set-and-forget
Took longer to configure than I expected. Auth is optional, which is convenient locally. I turned it on before sharing it with the team. Fine in production if you sandbox it.
Used for Routing inbound requests
- Setup & docs 3/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 2/5
Fine for a demo, not for prod
It works in a demo, but things got shaky under real use. The OAuth flow worked first time in Claude Code. I run it with auth enabled. Without it I would not let it near anything shared.
Used for Ops tasks like provisioning accounts
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 2/5
- Maintainer responsiveness 1/5
Went back to calling the API directly
Setup was rough and the result was flaky. It is community maintained, so I pin the version and read the changelog before upgrading. Auth is optional, which is convenient locally. I turned it on before sharing it with the team. For anything real I would look elsewhere.
Used for Connecting the agent to existing automations
- Setup & docs 2/5
- Auth experience 3/5
- Reliability 2/5
- Maintainer responsiveness 1/5
Security story needs work
Setup was rough and the result was flaky. I run it with auth enabled. Without it I would not let it near anything shared. Open issues pile up without replies. Works today, but I am watching for a fork.
Used for Routing inbound requests
- Setup & docs 1/5
- Auth experience 1/5
- Reliability 1/5
- Maintainer responsiveness 3/5
Too many sharp edges
Not what I expected from the description. Auth is optional, which is convenient locally. I turned it on before sharing it with the team. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. Not something I would put in production yet.
Used for Glue between tools that have no direct integration
- Setup & docs 2/5
- Auth experience 3/5
- Reliability 2/5
- Maintainer responsiveness 1/5
Would not run this unattended
I wanted to like this one. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. I will check back in a few releases.
Used for Glue between tools that have no direct integration
- Setup & docs 2/5
- Auth experience 4/5
- Reliability 2/5
- Maintainer responsiveness 1/5
Works, just lock it down
Some tools are great, a couple feel half finished. Out of the box it runs without sign-in, so remember to enable auth before exposing it anywhere. Fine in production if you sandbox it.
Used for Glue between tools that have no direct integration
- Setup & docs 3/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 3/5
Recommended it to two teams already
Simple to set up in Cursor, simple to reason about. I run it with auth enabled. Without it I would not let it near anything shared. Recommended, with sensible guardrails.
Used for Scheduled reporting jobs
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Struggled to get it stable
Gave it a fair shot over two weeks. It is community maintained, so I pin the version and read the changelog before upgrading. Auth is optional, which is convenient locally. I turned it on before sharing it with the team. I would use it in prod, but only with a human approving writes.
Used for Connecting the agent to existing automations
- Setup & docs 1/5
- Auth experience 3/5
- Reliability 1/5
- Maintainer responsiveness 1/5
Too much access for my comfort
Ran into problems pretty quickly. It is community maintained, so I pin the version and read the changelog before upgrading.
Used for Scheduled reporting jobs
- Setup & docs 3/5
- Auth experience 4/5
- Reliability 2/5
- Maintainer responsiveness 1/5
Better than the DIY script it replaced
Installed it on a Friday, it was part of my workflow by Monday. Auth is optional, which is convenient locally. I turned it on before sharing it with the team.
Used for Connecting the agent to existing automations
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 3/5
Exactly what I needed from n8n client node
Tried it on a side project first, then rolled it out at work. Maintenance has gone quiet, so I would not build anything critical on it. I run it with auth enabled. Without it I would not let it near anything shared. Good choice if you need n8n client node in your agent.
Used for Scheduled reporting jobs
- Setup & docs 3/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 3/5
Promising, a bit raw
Useful tool, though I would not hand it to a junior unsupervised. It is community maintained, so I pin the version and read the changelog before upgrading. The last release is getting old, which makes me nervous long term. Out of the box it runs without sign-in, so remember to enable auth before exposing it anywhere.
Used for Ops tasks like provisioning accounts
- Setup & docs 2/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Not ready for anything that matters
I wanted to like this one. It is community maintained, so I pin the version and read the changelog before upgrading. I run it with auth enabled. Without it I would not let it near anything shared. Worth it, just do not skip the hardening steps.
Used for Routing inbound requests
- Setup & docs 2/5
- Auth experience 3/5
- Reliability 2/5
- Maintainer responsiveness 2/5
Good, but read the permissions first
Mostly reliable, with the odd timeout. Open issues pile up without replies. Works today, but I am watching for a fork. It is community maintained, so I pin the version and read the changelog before upgrading. I will check back in a few releases.
Used for Triggering workflows from chat
- Setup & docs 2/5
- Auth experience 3/5
- Reliability 2/5
- Maintainer responsiveness 3/5
Earned a permanent spot in my config
Hooked n8n MCP client node into Claude Code and it worked on the first try. I run it with auth enabled. Without it I would not let it near anything shared. The OAuth flow worked first time in Claude Code. Happy to run it in production.
Used for Triggering workflows from chat
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Needs more maintenance love
Ran into problems pretty quickly. It is community maintained, so I pin the version and read the changelog before upgrading. Out of the box it runs without sign-in, so remember to enable auth before exposing it anywhere. Keeping it to local experiments for now.
Used for Ops tasks like provisioning accounts
- Setup & docs 2/5
- Auth experience 4/5
- Reliability 2/5
- Maintainer responsiveness 2/5
Write a review
Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.