N8n community version - MCP client STDIO option?

Questions
1

Describe the problem/error/question

MCP STDIO config fields not showing

What is the error message (if any)?

Only SSE config fields showing.

Please share your workflow

Chat mesage > Ai Agent > Tools > MCP Client

Share the output returned by the last node

Information on your n8n setup

  • n8n version: = community v1.91.0
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker
  • Operating system: - Linux OS
3 Likes
2

Hi,

I have the same need.
IS there a way to add the option to set STDIO configuration tu execute locally some MCP servers like it is the case with the MCP Client node from this repo: GitHub - nerding-io/n8n-nodes-mcp: n8n custom node for MCP ?

Thank you

1 Like
3

Screenshot 2025-05-23 at 14.43.48
Screenshot 2025-05-23 at 14.43.482194×1292 150 KB

You can use the community node,

n8n-nodes-mcp

DOMAINNAME.COM/settings/community-nodes
add here, this allows for STDIO connections.

4

hi,

Yes this is what I am doing currently.

However it is a bit weird to have 2 MCP Client Nodes looking Similar but one is not supporting the STDIO.

Thanks for your prompt reply

5

Hi,

You could start your STDIO servers + SSE proxy alongside the n8n process. They will listen on several ports.

Example workflow:

Then, in your other workflows, you can use the MCP Client Tool, and point it to http://localhost:port/sse

The n8n instance boot event will trigger the workflow as soon as your instance starts.

Hope this helps!

A.