Skip to main content
Glama
verzth

n8n MCP Server

by verzth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to n8n MCP Server

No user-submitted related servers found.

    Related Servers

    • n8n MCP Server

      mastrangi
      A
      license
      A
      quality
      C
      maintenance
      Manages workflows, executions, and folders on a self-hosted n8n instance through its public REST API, enabling MCP clients to create, update, activate, list, and trigger workflows via natural language.
      12
      3
      MIT

    • n8n-pro-mcp

      helbertparanhos
      A
      license
      A
      quality
      B
      maintenance
      Full-instance management for self-hosted n8n — including queue mode — through the Model Context Protocol. 51 tools covering workflows, executions, tags, credentials, variables, projects, users, security audit, source control and health monitoring. n8n-pro-mcp connects Claude Code, Claude Desktop, Cursor or any MCP client to your n8n instance via the official n8n public API v1
      51
      45 npm
      3
      MIT

    • n8n-mcp-server

      eric050828
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to programmatically control n8n via natural language for automated workflow creation, modification, and execution management.
      1
      -

    • n8n MCP Server

      andhit-r
      A
      license
      A
      quality
      C
      maintenance
      Enables management of n8n workflows, executions, credentials, tags, and variables via MCP tools. Supports stdio, Claude Code, and Claude Web with optional Authentik OAuth.
      22
      MIT

    • n8n MCP Server

      JRGPdev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude to query and manage workflows in an n8n instance, including listing workflows, checking active status, triggering executions, and reviewing execution history and details.
      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.9/5.0

    Scored across 39 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action pair (workflow, execution, credential, tag, variable, project, user, package). Similar operations like delete vs archive are explicitly distinguished in descriptions, leaving no ambiguity.

    Naming Consistency4/5

    All tools consistently use the n8n_ prefix with a verb_noun pattern. Minor deviations include plural nouns for lists (list_workflows) versus singular for single items (get_workflow), and a few non-verb-first names like n8n_discover and n8n_get_credential_schema, but the overall pattern remains predictable.

    Tool Count4/5

    With 39 tools, this is a large set, but it spans the full n8n API surface across workflows, executions, credentials, tags, variables, projects, users, and community packages. Each tool serves a clear purpose, so the count is justified by the broad domain.

    Completeness4/5

    Core workflows have full lifecycle coverage (CRUD, activate, archive, tags), and executions/credentials also have comprehensive operations. Minor gaps exist for projects (only list/create) and users (only list), but these do not block primary workflow management workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources