Skip to main content
Glama
NestorPVsf

n8n-workflows-mcp

by NestorPVsf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to n8n-workflows-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
      -

    • 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.
      77,070 npm
      MIT

    • automatelab-n8n-mcp

      AutomateLab-tech
      A
      license
      A
      quality
      C
      maintenance
      An MCP server for n8n that gives Claude, Cursor, and other AI agents tools for generating workflows, linting, diagnosing failed executions, and driving live n8n instances.
      12
      47 npm
      12
      MIT

    • mcp-n8n

      pauleandersonn
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for N8N that allows users to build, manage, and execute workflows through natural language, with 18 tools covering CRUD, execution, and intelligent workflow construction using templates, scaffolds, or LLM-based generation.
      64 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.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: listing workflows, retrieving schema, executing a workflow, and checking execution status. No overlap or ambiguity exists between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (list_workflows, get_workflow_schema, execute_workflow, get_execution_status), making the naming predictable and uniform.

    Tool Count5/5

    With only 4 tools, the server is well-scoped for its purpose. Each tool is essential and earns its place without unnecessary bloat or missing core functionality.

    Completeness5/5

    The tool set covers the full execution lifecycle: discover workflows, understand their input schema, execute them, and check execution status. No obvious dead ends or missing operations for the stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources