Skip to main content
Glama
AutomateLab-tech

automatelab-n8n-mcp

by AutomateLab-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to automatelab-n8n-mcp

No user-submitted related servers found.

    Related Servers

    • n8n-custom-mcp

      duynghien
      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
      -

    • Caipher MCP

      theblockchainbaby
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that provides AI assistants with comprehensive access to n8n workflow automation nodes, properties, and documentation. It enables models like Claude to search for nodes, access configuration templates, and manage workflows through natural language.
      MIT

    • n8n-workflows-mcp

      NestorPVsf
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that turns deployed n8n workflows into callable tools for AI agents, enabling discovery and execution of tagged workflows via a standard interface without rewriting integrations.
      4
      5 npm
      MIT

    • n8n-MCP

      mohsin-zaheer
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides AI assistants with access to documentation, schemas, and operations for over 535 n8n workflow automation nodes. It enables models to understand, create, and manage n8n workflows through natural language by connecting to the n8n API.
      141,724 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.4/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a distinct purpose within the n8n ecosystem: execution tools focus on debugging and replaying executions, node.scaffold generates custom nodes, and workflow tools cover lifecycle management (create, get, activate, list), generation, diffing, and linting. There is no overlap or ambiguity between the tools.

    Naming Consistency5/5

    All tools follow a consistent dot-separated convention of 'domain.action' (e.g., execution.explain, workflow.create). The naming pattern is uniform and predictable, making it easy for an agent to understand the scope of each tool.

    Tool Count5/5

    With 12 tools, the server is well-scoped for n8n automation workflows. It covers execution diagnostics, workflow CRUD (except delete), code generation, and linting—each tool earns its place without unnecessary bloat.

    Completeness3/5

    The toolset covers most core workflows (execution debugging, workflow creation/get/activate/list, generation, linting, node scaffolding) but lacks a delete or update workflow tool. This omission could require agents to implement workarounds for full lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessWithin a week

    Resources