Skip to main content
Glama
mastrangi

n8n MCP Server

by mastrangi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to n8n MCP Server

No user-submitted related servers found.

    Related Servers

    • n8n MCP Server

      verzth
      A
      license
      A
      quality
      D
      maintenance
      Wraps the n8n self-hosted REST API to let Claude and MCP-compatible LLMs manage workflows, executions, credentials, and more via natural language.
      39
      54 npm
      MIT

    • n8n MCP

      jimsimoy
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to inspect and control an n8n instance's workflows and executions via an HTTPS MCP endpoint, including listing, activating/deactivating workflows, and reading execution history.
      MIT

    • n8n MCP Server

      JBrightmanAI
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage n8n workflows and executions, including creating, updating, deleting, activating, deactivating, and executing workflows, as well as listing and retrieving execution details.
      54 npm
      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

    A4/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action pair: workflow CRUD/lifecycle, execution retrieval/triggering, and folder listing/creation are clearly separated. Even execute_workflow and activate_workflow are unambiguous because their descriptions clarify webhook triggering versus status changes.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern, such as list_workflows, create_folder, and deactivate_workflow. The naming is predictable and makes the action and resource immediately clear.

    Tool Count5/5

    With 12 tools, the server is well-scoped for managing n8n workflows, executions, and folders. Each tool covers a meaningful operation without redundancy or excessive granularity.

    Completeness4/5

    Workflow lifecycle coverage is strong: create, read, update, delete, activate, deactivate, and list are all present. Minor gaps exist for folders (no update or delete operations) and executions (no cancel or delete), but core workflows are fully covered and workarounds are available.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources