Skip to main content
Glama
ifmelate

n8n-workflow-builder-mcp

by ifmelate

Related Servers

Alternatives to n8n-workflow-builder-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      🪄 MCP server for programmatic creation and management of n8n workflows. Enables AI assistants to build, modify, and manage workflows without direct user intervention through a comprehensive set of tools and resources for interacting with n8n's REST API.
      10
      91 npm
      86
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for integrating with n8n, enabling workflow automation and management through natural language.
      365 npm
      1
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      An MCP server enabling secure interaction with n8n workflows, executions, and settings via the Model Context Protocol, designed for integration with Large Language Models (LLMs).
      33
      58 npm
      119
      MIT
    • F
      license
      B
      quality
      C
      maintenance
      A full-power MCP server for n8n that enables AI agents to create, read, update, delete, and test workflows and credentials, including webhook testing, validation, and backup/versioning.
      31
      9
      -

    TDQS

    C2/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting different aspects of n8n workflow management (e.g., create_workflow vs. list_workflows, add_node vs. edit_node vs. delete_node). However, add_ai_connections and add_connection could potentially be confused without descriptions, as their relationship is unclear—they might overlap in handling connections.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case throughout (e.g., add_connection, create_workflow, get_workflow_details). There are no deviations in naming conventions, making the set predictable and readable.

    Tool Count5/5

    With 10 tools, the count is well-scoped for a workflow builder server, covering core operations like creating, listing, and managing workflows and nodes. Each tool appears to earn its place without being excessive or insufficient for the domain.

    Completeness3/5

    The tools cover basic CRUD operations for workflows and nodes (create, list, get, edit, delete), but there are notable gaps. For example, there's no update_workflow or delete_workflow tool, and the absence of descriptions makes it hard to assess if AI connections and general connections are fully covered, potentially leaving dead ends in workflow management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues