Expose workflow management tools over an MCP server using the n8n Public API
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This AI workflow has 67 nodes and runs when an MCP client calls one of its tools (plus 1 other trigger). It uses only n8n's built-in nodes.
How it runs
Trigger: When an MCP client calls one of its tools (plus 1 other trigger).
- Config (Edit Fields (Set)): sets 2 fields: host, api_key
- Parse Payload (Code): runs custom JavaScript code
- Execution Data: uses Execution Data
- Operation (Switch): routes items into 16 branches
- GET Workflows List (HTTP Request): calls an HTTP API
- Build Search Queries (Code): runs custom JavaScript code
- GET Workflow By Id (HTTP Request): calls an HTTP API
- GET Workflow For Node Lookup (HTTP Request): calls an HTTP API
- Sanitize Create Payload (Code): runs custom JavaScript code
- Fetch Executions (HTTP Request): calls an HTTP API
…plus 39 more steps. See the full node list below.
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (10)
- Execute Workflow Trigger
n8n-nodes-base.executeWorkflowTrigger - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - Execution Data
n8n-nodes-base.executionData - Switch
n8n-nodes-base.switch - Stop and Error
n8n-nodes-base.stopAndError - Split Out
n8n-nodes-base.splitOut - HTTP Request
n8n-nodes-base.httpRequest - MCP Server Trigger
@n8n/n8n-nodes-langchain.mcpTrigger - Call n8n Workflow Tool
@n8n/n8n-nodes-langchain.toolWorkflow
From the author
Quick overview This workflow exposes an MCP (Model Context Protocol) server endpoint that lets an MCP client manage workflows and executions in an n8n instance via the n8n Public API, including searching, reading, creating, updating, activating/deactivating,…