Skip to main content
Glama
helbertparanhos

n8n-pro-mcp

by helbertparanhos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to n8n-pro-mcp

No user-submitted related servers found.

    Related Servers

    • n8n MCP Server

      Shravan1610
      A
      license
      B
      quality
      D
      maintenance
      Enables users to manage workflows, monitor executions, and perform administrative tasks in n8n through natural language conversations with Claude. It provides over 40 tools to control self-hosted or cloud n8n instances via the Model Context Protocol.
      42
      54 npm
      MIT

    • n8n MCP Server

      verzth
      A
      license
      A
      quality
      D
      maintenance
      Wraps the n8n self-hosted REST API to let Claude and MCP-compatible LLMs manage workflows, executions, credentials, and more via natural language.
      39
      54 npm
      MIT

    • 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-free-mcp

      justineserna1z
      A
      license
      A
      quality
      D
      maintenance
      Free & open-source MCP server for n8n. Manage your workflows, debug executions and control your self-hosted n8n instance directly from any Model Context Protocol client.
      12
      MIT

    • N8N MCP Server

      chinmaybhatk
      A
      license
      Not graded
      quality
      D
      maintenance
      Model Context Protocol (MCP) server for managing n8n workflows, allowing Claude and other MCP-compatible tools to create, read, update, delete, and execute workflows in your n8n instance.
      54 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

    A3.7/5.0

    Scored across 51 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, with detailed descriptions that prevent ambiguity. Even with 51 tools, operations are well-separated across different resources (workflows, credentials, users, projects, etc.) and actions.

    Naming Consistency5/5

    All tool names use lowercase snake_case with a verb_noun pattern (e.g., activate_workflow, list_users). The naming is highly consistent with no mixing of conventions.

    Tool Count4/5

    The 51 tools cover a broad domain (n8n instance management), and each tool appears justified. However, the count is high; a slightly more consolidated set could be conceivable, but the current scope earns a 4.

    Completeness5/5

    The tool set covers the full lifecycle of workflows, credentials, users, projects, tags, variables, and executions, including advanced operations like cloning, validation, bulk actions, and health monitoring. No obvious gaps are present.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources