Are all n8n connectors going to be MCP-ified?

If AI agents are the new killer feature for n8n workflows, should we expect all the n8n connectors to be wrapped as MCP servers to make it seamless for LLMs to interact with them?

As AI evolves, n8n evolves with it.
The team has made it clear that AI is currently the focus of the development efforts.

I believe MCP is the next step for tools. Instead of tools, we’ll have MCP servers connected to our AI agents.

But since tools are still very useful for custom solutions, I don’t think they’ll go away.

When third-party tools like Google Sheets, Calendar, Notion etc. release their official MCP servers, we’ll rarely need custom tools to use their services.

I think we’ll be using tools for custom HTTP requests, subworkflows etc. More customized stuff.

1 Like

zapier make a smart way to use mcp

1 Like

Linking n8n to Zapier mcp is another level lol :joy::brain:

1 Like

ActivePieces; which I always thought it was a n8n fork; developped is own MCP
which allow users to call their automation directly via Claude Desktop, Windsurf, or Clide.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.