Provide and use Model Context Protocol

@nerding-io Thanks so much for your efforts in creating this module. It’s an exciting topic!

For anyone interested, I published a YouTube video on how to install and use it here.

11 Likes

awesome video @Daniel_Walsh :+1: and thanks for your help guys!

@nerding-io yeah as I researched more and more I realised it might need a combined approach with passing credentials dynamically → huge potential though as it’d mean one node to list all tools, one to execute tools with just a base prompt + additional prompt context from listPrompts. Thanks so much again!

2 Likes

Posted a video on it also - step-by-step setup, MCP explained in full with reference to how powerful a combo MCP + N8N could be if it becomes the industry standard!

Thanks again for creating this awesome node @nerding-io

8 Likes

Ha also created a video. https://youtu.be/1t8DQL-jUJk

@Daniel_Walsh @Simon_Coton these are great! Thanks for the interest and contribution.

Would you mind if I include these in the repo docs?

3 Likes

Of course! Go for it :grinning:

Absolutely!

Hi guys, need some help.
Using Hostinger VPS
Got the error
“Unrecognized node type: n8n-nodes-mcp.mcpClientTool”
I’ve followed all the steps for the bash (which is what Hostinger told me it was using).
Still not working, any idea?

Simple noob trying to figure out things :)))

2 Likes

Preformatted textNodeOperationError: Failed to execute operation: The file or directory does not exist at ExecuteContext.execute (C:\Users\Risin.n8n\nodes\node_modules\n8n-nodes-mcp\nodes\McpClient\McpClient.node.ts:561:10) at processTicksAndRejections (node:internal/process/task_queues:105:5) at Workflow.runNode (C:\Users\Risin\AppData\Roaming\npm\node_modules\n8n-workflow\src\Workflow.ts:1394:8) at C:\Users\Risin\AppData\Roaming\npm\node_modules\n8n-core\src\WorkflowExecute.ts:1173:27 at C:\Users\Risin\AppData\Roaming\npm\node_modules\n8n-core\src\WorkflowExecute.ts:1894:11Preformatted text

I am getting this error in using n8n-nodes-mcp

I’m trying to run Puppeteer MCP on the N8N, it works normally up to the MCP node with operation List Tools, but on the next MCP node with operation Execute Tool it gives this error. Can anyone help me solve it? I’ve tried a lot of things and it still gives this error.

In this case, I asked it to access google, then the AI Agent node executes the first tool that has the operation list tools, but when it executes the tool that has the operation execute tool, it gives the error.

Failed to execute operation: Operation not permitted, make sure you have the right permissions

Error details

n8n version: 1.82.3 (Self Hosted)

Time: 16/03/2025, 14:53:35

Error cause: { “message”: “Failed to execute operation: Operation not permitted, make sure you have the right permissions”, “timestamp”: 1742147615047, “name”: “NodeOperationError”, “context”: {}, “cause”: { “level”: “error”, “tags”: {} } }

Hi Jordan you have to set an ENV

  • N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true

Hi, I’ve set the variable to true, i can see it and I restarted my server but I still have the same error message. Can you help me resolve this please ?

1 Like

It was referred to by this github by @nerding-io

It might be helpfull

1 Like

Thanks @nerding-io for the development of the node, amazing!!
I have also published a video (in portuguese).

VIDEO

3 Likes

Question for the experts:
How is it possible to use MCP servers that are not available as an NPM package but only on GitHub?

Similarly, for MCP servers written in Python, is it possible to use them directly, or do I need to deploy them in the cloud and use them via SSE?

Thanks!

2 Likes

Thanks but I’ve been threw this documentation and I really don’t understand what’s happening I’m still trying to fix this issue after hours of research…

I have the exact same issue. The MCP node in itself is working as intended when used on its own, meaning that the env variable is correctly set. But as soon as I connect the node to the AI agent in the tool section, I have the same error “Unrecognized node type: n8n-nodes-mcp.mcpClientTool”.

I don’t really understand what is going on

Hi,

I installed N8N on my local machine and follow all the steps when connect MCP client tool and setup fireCrawl and run it through me error

I am getting the error Unrecognized node type:n9n-nodes-mcp.mcpClientTool

I am using updated mcp node

Above are my settings, can any one help me to resolve this please.

Still have the trouble? I was able to easily integrate it just by following the instructions here: n8n-nodes-mcp - npm
And that in the Hostinger’s terminal you just configure your docker-compose.yml thru: nano …/root/docker-compose.yml
And you just add this environment: - N8N_COMMUNITY_PACKAGES_ALLOW_TOOL_USAGE=true
And you may refresh your n8n and wait till MCP Client appears in the list.

I get the same error on testing the MCP Client tool in the self hosted in Windows. I have tried same in self hosted docker instance, hope it is linux version, hence it worked without any issue. I believe the issue is with the windows n8n installation. I see the installed directory structure is different.

Would appreciate if the development team or others using windows confirms it is successfully configured in windows. Thanks

3 Likes

Got this resolved? Please let me know any fix found. Thanks

1 Like