N8n Workflow Builder

Created By
ifmelatea year ago
Overview

What is N8n Workflow Builder?

N8n Workflow Builder is a tool that provides a Model Context Protocol (MCP) server for building and manipulating n8n workflows in JSON format using AI prompts in the Cursor IDE.

How to use N8n Workflow Builder?

To use the N8n Workflow Builder, clone the repository, install the dependencies, build the TypeScript project, and start the MCP server. You can then integrate it with Cursor IDE to create and manage workflows.

Key features of N8n Workflow Builder?

  • Workflow Management: Create, update, and execute n8n workflows programmatically.
  • Node Discovery: Explore available n8n nodes and their capabilities.
  • Connection Management: Create connections between workflow nodes.
  • AI Integration: Tools for connecting AI components in workflows.
  • AI-Friendly Interface: Designed for interaction with AI agents.

Use cases of N8n Workflow Builder?

  1. Automating data workflows using AI.
  2. Creating complex workflows with minimal coding.
  3. Integrating various services and APIs seamlessly.

FAQ from N8n Workflow Builder?

  • What are the prerequisites for using N8n Workflow Builder?

You need Node.js (v14 or higher), Cursor IDE (v0.48 or newer), npm or yarn, and a TypeScript compiler.

  • Is there a demo available?

Yes! A demo video is available on the project's GitHub page.

  • How can I contribute to the project?

Contributions are welcome! You can fork the repository and submit a Pull Request.

Server Config

{
  "mcpServers": {
    "n8n-workflow-builder": {
      "command": "node",
      "args": [
        "/absolute/path/to/n8n-workflow-builder-mcp/dist/index.js"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ifmelate
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago