Connect your account, then chat with AI to run tools.
Search real n8n templates and node settings, draft workflows in chat, check the structure before deploy, and push to your self-hosted instance — without copying JSON from forum posts.
Try this workflow
Find a Slack alert template
Search the n8n template library for a Slack notification workflow with high view counts, show the node list, and summarize how it triggers.
Opens MCPBundles Studio with this server selected. After sign-in, chat and run tools from the same thread.
Browse all toolsBuilt for
Automation Leads, RevOps Builders, Integration Consultants, AI-First Operations Teams
Find a Slack alert template
Starts from real community templates instead of inventing node names.
Search the n8n template library for a Slack notification workflow with high view counts, show the node list, and summarize how it triggers.
Draft a trigger workflow
Covers discover → validate → deploy in one ops-style ask.
Build a simple form-to-email workflow for Harbor Legal: validate the draft offline, then deploy to our n8n instance when the structure looks clean.
Fix a broken branch
Surfaces offline repair for the branching mistakes agents make often.
This IF node workflow sends everything down the wrong branch. Inspect the draft, suggest wiring fixes from the pattern library, and redeploy.
Import a popular template
Template import plus instance deploy without manual JSON paste.
Import template 5338 into n8n as 'Bright Smile weekly digest', rename it for our team, and leave it inactive until we review credentials.
Do I need my own n8n instance?
Searching templates and checking drafts works without your instance. Deploying, running, and inspecting live workflows requires a connected n8n server with an access key from n8n Settings.
Where do the templates and node settings come from?
MCPBundles maintains a searchable index built from the public n8n template library and node catalog, refreshed on a schedule so agents query local evidence instead of hammering the public site on every turn.
Can it catch mistakes before a workflow goes live?
Yes. Drafts can be checked offline for missing node names, bad wiring, and common expression mistakes. After deploy, live checks and run inspection help repair failures without rebuilding from scratch.
Related editorial
n8n Workflow Builder with AI
Search real n8n templates and node settings, draft workflows in chat, check structure before deploy, and push to your self-hosted instance.
Domain knowledge for n8n Workflow Builder — workflow patterns, data models, and gotchas for your AI agent.
Use the materialized node and template catalog to draft workflow JSON, then push changes to the user's connected n8n instance.
When building or repairing a workflow, follow this loop. Retry at most three times before stopping and reporting blockers.
Before a retry after a failed run, inject pin data on trigger or credential nodes when you need to simulate upstream payloads without calling external services.
Apply these during draft, validation, and autofix — they cause silent failures when wrong.
Fetch any n8n resource by colon-routed ID. Supports execution, workflow, tag, variable, and project resources. Use 'n8n:execution:{id}', 'n8n:workflow...
Activate a workflow in your n8n instance. This enables the workflow triggers so it can run automatically.
Validate workflow structure offline and run live instance checks for saved workflows (activation readiness, credential references, trigger presence).
Inspect credential schemas, create credentials, list accessible credentials when supported, and check workflow nodes for missing credential references...
Deactivate a workflow in your n8n instance. This disables the workflow triggers so it will not run automatically.
Delete an execution from your n8n instance. This permanently removes the execution record.
Delete a project from your n8n instance.
Delete a tag from your n8n instance.
Delete a variable from your n8n instance. Requires an n8n plan with the Variables feature enabled.
Delete a workflow from your n8n instance. CAUTION: This permanently removes the workflow, all its execution history, and all associated data. This act...
Execute a workflow by ID via its webhook trigger. Only workflows with webhook triggers can be executed via API. Before executing, use get_workflow_det...
List, fetch, or delete workflow executions. Cancel is not supported on the public REST API.
Search inside a workflow by node, connection, flow path, or parameter text. Supports substring, regex, and flow patterns like Webhook->Code->Slack.
Retrieve a list of workflow executions from your n8n instance. Use it to monitor and analyze the performance and outcomes of automated workflows. Retu...
Inspect per-node execution input/output with optional workflowId shortcut, IF/Switch outputIndex filter, source lineage, and schema-style compact shap...
Retrieve a specific project by ID. The n8n public API exposes list/create/update/delete for projects but not GET /projects/{id}; this tool resolves th...
Retrieve all projects from your n8n instance. Projects help organize workflows and resources.
Retrieve a specific tag by ID.
Retrieve all tags from your n8n instance. Use tags to organize and categorize workflows.
Retrieve a specific variable by ID. Variable values are typically masked for security. Requires an n8n plan with the Variables feature enabled.
Retrieve all variables from your n8n instance. Variables store configuration values and secrets. Requires an n8n plan with the Variables feature enabl...
Get detailed information about a specific workflow including trigger details. Use this to understand how a workflow works and what inputs it expects b...
Get workflows from your n8n instance with optional active/tag/name/project filters. Use this for a full inventory or when filtering by active status o...
Get all tags associated with a specific workflow. Returns an empty list when the workflow has no tags — that is a successful result, not missing data.
Retrieve a specific version of a workflow from workflow history.
Deploy a public n8n template from the knowledge index onto the connected instance as a new workflow.
List or inspect frequent workflow node-type patterns mined from indexed templates. Use mode=list first, then mode=detail with patternId for node seque...
Browse or fetch workflow-building guides. Use mode=list first, then mode=detail with topic or technique for expressions, branching, batching, credenti...
Get schema and optional config exemplars for one or more n8n node types. Use requests[] for batch lookup with resource/operation/mode filters, or node...
List curated n8n template collections and learning-path patterns from the knowledge index.
Fetch an n8n template from the local index. Use mode=structure for a compact graph summary without full parameter payloads, or mode=full for complete ...
Detect and optionally fix common workflow issues: expression wrapping, typeVersion mismatches, Split In Batches connection rewires, IF wiring hints, w...
Search expression syntax notes and common workflow gotchas such as IF and Split In Batches wiring.
Search the materialized n8n node catalog (~1,500 core and community nodes). Use includeOperations=true to see resource/operation/mode discriminators b...
Search n8n workflow templates from the materialized catalog (~10k templates). Returns metadata and node-type coverage; use n8n_index_get_template for ...
Get node recommendations for workflow techniques mined from indexed templates. Technique slugs come from the refresh pipeline (node groups, credential...
Offline workflow validation against the materialized node catalog. Checks node shape, connection targets, and known node types before live deployment.
Apply targeted partial updates to an existing workflow without replacing the full graph. Supports add/remove/rename nodes, parameter patches, connecti...
Get, set, or clear workflow pin data used to mock node outputs during testing.
Retry a failed execution from your n8n instance. Use this to re-run workflows that failed due to errors or timeouts.
Execute a workflow on the connected instance via webhook or form trigger, wait for the matching execution, and repair failures using offline autofix p...
Test a workflow by optionally applying pin data, then executing through the existing execute path. Best for webhook-triggered workflows that are alrea...
Search workflows by name keyword or projectId filter. Pass query to match workflow names (maps to the upstream name filter). Do NOT use this for a ful...
Create a new team project or update an existing project by ID. Omit projectId to create. Personal projects appear in list_projects but cannot be updat...
Create a new tag or update an existing tag. If tagId is provided, updates the tag. Otherwise creates a new tag; when a tag with the same name already ...
Create a new variable or update an existing variable. If variableId is provided, updates the variable; otherwise creates a new one. Requires an n8n pl...
Create a new workflow or update an existing workflow. For updates: if workflowId is provided, updates the workflow. The API requires name, nodes, conn...
Build n8n workflows with a materialized node and template knowledge index plus live workflow CRUD, execution, and management tools on the user's n8n instance. It provides 47 tools that AI agents can use through the Model Context Protocol (MCP).
Add the MCPBundles server URL to your MCP client configuration (Claude Desktop, Cursor, VS Code, etc.). The URL format is: https://mcp.mcpbundles.com/bundle/n8n-workflow-builder. Authentication is handled automatically.
n8n Workflow Builder provides 47 tools that can be called by AI agents, along with a SKILL.md that gives your AI agent domain knowledge about when and how to use them.
n8n Workflow Builder uses API Key or No auth required. n8n requires credentials. Connect via MCPBundles and authentication is handled automatically.
Searching templates and checking drafts works without your instance. Deploying, running, and inspecting live workflows requires a connected n8n server with an access key from n8n Settings.
MCPBundles maintains a searchable index built from the public n8n template library and node catalog, refreshed on a schedule so agents query local evidence instead of hammering the public site on every turn.
Yes. Drafts can be checked offline for missing node names, bad wiring, and common expression mistakes. After deploy, live checks and run inspection help repair failures without rebuilding from scratch.
Ops and automation leads who already use n8n but want agents to search real examples, assemble drafts, and push to a self-hosted instance — not developers wiring custom integrations from memory.
Enable the n8n Workflow Builder on MCPBundles, add your instance URL and access key from n8n Settings, then ask in chat. Knowledge search works immediately; deploy steps use the saved connection.
Connect n8n Workflow Builder to any MCP client in minutes
https://mcp.mcpbundles.com/bundle/n8n-workflow-builderThe link prefills the Add custom connector dialog — you still review the values and click Add, then Connect to complete OAuth.
n8n Workflow Builder and paste the MCP URL into Remote MCP server URL.Custom connectors at claude.ai require a paid Claude plan (Pro, Max, Team, or Enterprise).
Same data, different audiences.
More developer tools integrations you might like
Split_io provides a feature flagging and experimentation platform, enabling developers to implement ...
Analyze CIDR networks, calculate subnet details, and check IP membership. Supports IPv4 and IPv6. Pu...
The Recreation API provides access to information about recreational areas, facilities, and activiti...
UpPromote is an affiliate management software that provides a platform for businesses to create, man...
Aviationstack is an API service that provides real-time and historical flight data, including flight...
Use the Ticketmaster Commerce API to look up available offers and products on various Ticketmaster p...