Skip to main content
Glama
lidless-labs

n8n-ops-mcp

by lidless-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to n8n-ops-mcp

No user-submitted related servers found.

    Related Servers

    • n8n MCP Server

      andhit-r
      A
      license
      A
      quality
      C
      maintenance
      Enables management of n8n workflows, executions, credentials, tags, and variables via MCP tools. Supports stdio, Claude Code, and Claude Web with optional Authentik OAuth.
      22
      MIT

    • n8n Automation MCP Server

      SohailShabbir867
      F
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to fully automate n8n instances via 34 MCP tools, covering workflow creation, execution debugging, credential management, environment variables, tags, and user administration through natural language.
      34
      1
      -

    • n8n-mcp-guard

      FarazHayder
      A
      license
      A
      quality
      B
      maintenance
      Lets AI agents read, create, and update n8n workflows with a guarded two-phase plan-and-apply flow that backs up every change, refuses writes when the live workflow has moved, and verifies results by readback. Also supports rehearsing changes on trigger- and outbound-disabled test clones, so mutations to a live instance stay reviewable and reversible.
      5
      28 npm
      6
      MIT

    • Hermes n8n MCP

      csenguttuvan
      A
      license
      Not graded
      quality
      B
      maintenance
      A local stdio MCP bridge for managing n8n from Hermes Agent, exposing tools to check health, list/inspect workflows, view executions, and activate/deactivate workflows securely without exposing n8n over the network.
      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.1/5.0

    Scored across 20 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose. For example, execution-related tools (n8n_execution_stats, n8n_get_execution, n8n_list_executions, n8n_search_executions) each focus on different aspects: aggregated stats, single execution detail, listing, and text search. Similarly, workflow scanning tools target different signals (disabled nodes, credential usage, node type usage). No two tools overlap in function.

    Naming Consistency5/5

    All tool names follow the consistent pattern `n8n_<verb>_<resource>` using snake_case and imperative verbs (e.g., list, get, check, diff, find, run, scaffold, validate). The convention is uniform and predictable, making it easy for an agent to infer purpose from the name.

    Tool Count4/5

    With 20 tools, the server is on the higher end but still appropriate for the broad domain of n8n operations (workflows, executions, credentials, tags, schedules, webhooks, auditing, node generation). Each tool provides distinct value, and the count reflects the complexity of the platform without being excessive.

    Completeness3/5

    The tool set covers inspection, auditing, validation, and comparison well, but lacks mutation tools for creating, updating, or deleting workflows and credentials. While the server's focus appears to be ops/inspection, the absence of basic CRUD operations for key resources creates notable gaps that may require agents to fall back to other means.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources