Skip to main content
Glama
AutomateLab-tech

automatelab-n8n-mcp

by AutomateLab-tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to automatelab-n8n-mcp

  • Content Distribution MCP

    AutomateLab-tech
    A
    license
    A
    quality
    D
    maintenance
    AutomateLab Content Distribution publishes content across DEV.to, Hashnode, GitHub Discussions, Reddit and Bluesky, with browser workflows for LinkedIn, Medium and X. Tracks publishing state and adapts content per platform. Product and documentation: https://automatelab.tech/products/mcp/content-distribution-mcp/
    8
    57 npm
    5
    MIT

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
    4 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.
    82,432 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.3/5.0

Scored across 12 tools

Disambiguation5/5

Each tool targets a distinct resource and action: generation, scaffolding, linting, diffing, live workflow CRUD, and execution analysis are clearly separated. The three execution tools (explain, replay, timeline) are complementary rather than overlapping, with descriptions explicitly distinguishing their purposes.

Naming Consistency5/5

All tool names follow a consistent resource_action snake_case pattern (workflow_generate, execution_explain, node_scaffold, etc.). The convention is applied uniformly across workflow, execution, and node domains.

Tool Count5/5

12 tools is well-scoped for an n8n automation server covering generation, validation, live instance management, and execution debugging. Each tool earns its place without redundancy.

Completeness3/5

The server covers creation, listing, fetching, and activation of workflows, plus execution diagnostics, but lacks workflow update and delete operations. This is a notable gap for full lifecycle management on a live n8n instance, though core generation and debugging workflows are supported.

Maintenance

ActivityInactive
ResponsivenessWithin a week

Resources