I’m still facing the same issue. I’ve been running n8n on a local Windows setup and have tried multiple things — uninstalling, clearing cache, making changes in package.json, adding environment variables, reinstalling n8n, and even completely deleting everything and starting fresh. Unfortunately, the problem persists.
I think you might be right; it could be something specific to Windows. I’ve been troubleshooting for almost two days now and tested several approaches, but still no luck.
I have a question: if I use Elest.io to host the server instead, do you think it will work without these issues?
Hi @Simon_Coton,
it maybe possible to do what you proposed using n8n-nodes-run-node-with-credentials-x community node in conjuctions with n8n node for MCP
You would use run-node-with-credentials-x node in place of MCP node and it basically “fills in the credentials”.
Credential ID - I use one from Edit Fields {{ $json.play }} or {{ $json.brave }}
I just use control-C (i use win11) on node MCP Client then control-V to Field - Node to execute in Run Node WIth Credentials X1 – this will paste the json of MCP node ther.
Then you can just run the workflow (the MCP node is ignored) and it produces list of tools of either {{ $json.play }} or {{ $json.brave }} MCP.
The credentials are defined as expression therefore you can do any number of things with it.
Naturally this works for Execute Tool also. And therefore allows usage of just one node to list tools and execute tools on MCP server chosen as expression.
The only thing that is missing is Tool node with Run Node With Credentials X.
But I guest this can be circumvented using Workflow Tool?
I installed this without the right environment vars and now I get the error trying to uninstall it:
Problem uninstalling package
Error removing package “n8n-nodes-mcp”:async function setType(requestOptions) { const operation = this.getNodeParameter(‘operation’); const me… } could not be cloned.
To everyone posting here: Please note that this is a feature request for native MCP support. There are alternate posts for discussing the community tool.
If you aren’t able to use any community node as tool, please wait until the next release, when this feature will actually be enabled.
While I appreciate everyone who made videos about the MCP tool, and the tool’s readme documenting everything so well, considering how this has spiraled into a dozen threads and github issues, creating unnecessary work for support, I’m feeling a bit discouraged to share beta features like these in the future.
@nerding-io
subscribed and thank you so much, i just have a few comments:
it works if i explicitly provide the tool name to the execute tool, however if i set tool name = {{ $fromAI }} it doesnt always get the correct tool name as expected (even though i provided a separate “list-tools” tool to the agent.
The reason i want to do this is because
a. some things require a combination of tool executions to complete e.g. If i create an invoice in Xero (accounting app) it needs to call three tools sequentially to achieve this. If i use claude desktop with the same MCP Server its able to correctly achieve this by “figuring out” which tools to use however with n8n its not Always able to do this, sometimes it just repeatedly calls the “list-tools” tool and sometimes it calls the execute tool (with a made up tool name) without calling list-tools
b. i dont want to explicitly provide the tool names and i also dont want to make a workflow of mcp tool executions as it would defeat the purpose MCP
i think it might be because im using openAI as the model and not Anthropic/?? once i have Anthropic API set up i will test again
),