n8n-extending-mcp-official

n8n Extending MCP Any n8n workflow with MCP access enabled becomes a tool the coding agent can call by name. Two common cases: Wrap n8n capabilities the MCP doesn't expose. The MCP covers workflow CRUD, validation, execution, data tables, credential listing, execution search, folder create/rename/move and folder/project listing, tag listing and attach/detach. Still missing: folder deletion, project create/rename, tag rename/delete, instance metadata, credential creation. Build a workflow that hits the n8n API and exposes the result as an agent tool. 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 delete, and project create/rename: no MCP tool. Folder create/rename/move and moving workflows between folders now have MCP tools ( create_folder , update_folder , move_workflows_to_folder ), on a registered instance; delete still needs the REST API. Tag rename/delete: the MCP lists tags ( list_workflow_tags ) and attaches/detaches them ( update_workflow addTags / removeTags , auto-creating unknown names), but can't rename or delete tag entities. REST API exists for those. 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. Show more Installs 963 Repository n8n-io/skills GitHub Stars 464 First Seen Jul 8, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass