Skip to main content
Glama
hifede1

n8n-mcp-server

by hifede1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to n8n-mcp-server

No user-submitted related servers found.

    Related Servers

    • mcp-n8n

      lyzetam
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for n8n workflow automation, enabling management of workflows, executions, credentials, tags, users, and webhooks via an MCP-compatible client.
      MIT

    • n8n MCP Server

      allanbchancery
      A
      license
      B
      quality
      D
      maintenance
      MCP server for managing n8n workflows and executions. Enables listing, activating, deactivating, and executing workflows, as well as monitoring executions and instance health.
      9
      MIT

    • n8n-free-mcp

      jserna0001
      A
      license
      A
      quality
      D
      maintenance
      Free and open-source MCP server for managing n8n workflows, executions, and tags via n8n's API. Enables workflow creation, activation, debugging, and deletion from any MCP client.
      12
      2
      MIT

    • mcp-n8n-builder

      spences10
      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
      23 npm
      86
      MIT

    • n8n MCP Server

      illuminaresolutions
      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
      50 npm
      118
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: lifecycle commands for the n8n installation (install/start/stop/status), workflow operations (list/get/create/activate/deactivate), and execution queries (list/get). No two tools overlap.

    Naming Consistency4/5

    All tools follow the n8n_ prefix with a clear action-resource pattern (e.g., n8n_list_workflows, n8n_get_execution). The only minor deviation is n8n_status, which is a noun rather than verb+noun, but it still fits the overall scheme.

    Tool Count5/5

    Eleven tools provide a well-scoped set covering server lifecycle, workflow management, and execution inspection without redundancy. This is within the ideal range.

    Completeness3/5

    The set lacks update and delete operations for workflows, which are part of typical workflow lifecycle management. While creation, activation, and deactivation are covered, users cannot modify or remove existing workflows, leaving a notable gap.

    Maintenance

    ActivityStale
    ResponsivenessResponsive

    Resources