Home / News

MCP shifts integration work to vendors: what changes for n8n users

n8n is a workflow automation tool, and for a small business its main job is shifting from wiring APIs together to controlling what an AI agent may do inside your systems. When choosing between n8n and Make today, the count of ready-made connectors matters less than how well the tool handles agents, approvals and logs.

That is the core of a piece on the n8n Blog. As vendors publish MCP servers, the integration burden moves to the provider. The vendor maintains tools, schemas and access, and your agent just authenticates. The author adds two corrections. A valid tool definition does not teach an agent the workflow, so you still need "skills", markdown instructions loaded into the model's context. And MCP is still a wrapper over regular APIs with OAuth 2.1.

What changes for a small business

Take a lead pipeline. A Claude agent reads a Telegram request, checks the CRM and books a slot. Field mapping and retries used to eat most of the build. With the CRM vendor's MCP server that part shrinks. The real work becomes instructions: which tool to call first, what to do with a duplicate contact, when to stop and hand off to a person. Hooks, scripts that run before a tool call and return yes or no, are a natural place for that check.

One catch: the spec moves fast, features get deprecated between versions, and APIs are adding rate limits aimed at agents. Before you build on a vendor's MCP server, confirm that one exists for your CRM or accounting system and that someone keeps it updated.

Why it matters: fewer hours go into connectors and more into describing your process precisely. That description is the part of the automation you actually own.

Source: n8n Blog