Skip to main content
Glama
nikolausm

n8n MCP Server

by nikolausm

Related Servers

Alternatives to n8n MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage n8n workflows and executions, including creating, updating, deleting, activating, deactivating, and executing workflows, as well as listing and retrieving execution details.
      59
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to manage n8n workflow automation instances through tools for workflow CRUD operations, execution monitoring, and webhook triggering. It facilitates programmatic interaction with n8n instances via the n8n API with AI-optimized descriptions and error handling.
      62
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI models to manage n8n workflow automation through a standardized interface. Supports creating, reading, updating, and deleting workflows with comprehensive access to workflow nodes, connections, and configurations.
      9
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables management of n8n workflow automations through natural language, supporting creation, execution, updates, and deletion of workflows, along with node discovery and execution status monitoring.
      MIT

    TDQS

    B3.2/5.0

    Scored across 19 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose: workflow CRUD, activation, execution, and history; tag CRUD; credential listing; and webhook retrieval. No two tools overlap significantly.

    Naming Consistency5/5

    All tool names follow a consistent 'verb_noun' pattern in snake_case, such as 'create_workflow', 'get_executions', and 'update_tag'. No mixed conventions or vague verbs.

    Tool Count4/5

    With 19 tools, the set covers multiple domains (workflows, executions, tags, credentials, webhooks) and each tool seems necessary. Slightly on the higher end but still well-scoped for the server's purpose.

    Completeness4/5

    Workflows, executions, and tags have full CRUD/lifecycle coverage. Credentials are limited to listing names, which is a minor gap but likely intentional for security. No obvious dead ends for typical workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues