Skip to main content
Glama
Siddharth0903

n8n-mcp

by Siddharth0903
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

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

    • 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

      Mutahar456
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that empowers AI assistants to build, validate, and manage n8n workflows by providing structured access to documentation for over 1,200 nodes and thousands of templates. It enables deep integration with n8n instances for automated workflow orchestration and management through natural language.
      46,471 npm
      1
      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.
      306 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.
      46,471 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

    B3.2/5.0

    Scored across 43 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific resources like workflows, credentials, executions, tags, variables, and data tables, with clear CRUD operations. However, some potential overlap exists between execute_workflow and trigger_webhook_test (both involve running workflows), and stop_execution vs stop_many_executions could be confusing if not carefully read. Overall, descriptions help clarify boundaries, but minor ambiguity remains.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, such as create_workflow, get_workflow, update_workflow, delete_workflow, and similarly for credentials, tags, variables, executions, and data tables. All names use snake_case uniformly, with clear action verbs (list, get, create, update, delete, execute, stop, etc.), making the set predictable and easy to navigate.

    Tool Count2/5

    With 43 tools, the count is excessive for typical MCP server scopes, which are best kept focused with 3-15 tools. While n8n is a complex workflow automation platform, this many tools can overwhelm agents and increase cognitive load. A more streamlined set grouping related operations or using parameters could reduce the count without losing functionality, making it borderline heavy for effective agent use.

    Completeness5/5

    The tool surface provides comprehensive coverage for managing n8n workflows and related resources, including full CRUD operations for workflows, credentials, tags, variables, data tables, and executions, plus advanced features like execution control, auditing, versioning, and source control. There are no obvious gaps; agents can perform end-to-end lifecycle management, validation, and monitoring within this domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources