n8n Extending MCP

Any n8n workflow with MCP access enabled becomes a tool the coding agent can call by name. Two common cases:

1. Wrap n8n capabilities the MCP doesn't expose. The MCP covers workflow CRUD, validation, execution, data tables, credential listing, execution search, folder/project listing. Still missing: folder CRUD, tag CRUD, instance metadata, credential creation. Build a workflow that hits the n8n API and exposes the result as an agent tool.
2. Expose a general-purpose workflow as a tool. A workflow that has nothing to do with n8n itself (calls a third-party API, runs internal business logic, looks something up in a private system) can be MCP-callable. Lets the agent invoke real operations during a coding session.

The MCP calls your workflow as if it were a native tool: input from the Execute Workflow Trigger, output from the workflow's last node.

When to reach for this

Case 1 (wrap n8n capability):

• Folder CRUD (create, rename, move, delete): REST API exists, no MCP tool yet.
• Tag CRUD (create, list, get, delete): REST API exists, no MCP tool yet.
• Instance metadata (limits, plan info, configured integrations): no MCP tool.
• Credential creation: REST API exists (POST /credentials), no MCP tool yet.
• Any n8n API operation the MCP doesn't natively expose.