Skip to main content
Glama

n8n MCP 서버

모델 컨텍스트 프로토콜을 통해 n8n 워크플로, 실행, 자격 증명 등에 대한 액세스를 제공하는 MCP 서버입니다. 이를 통해 대규모 언어 모델(LLM)이 안전하고 표준화된 방식으로 n8n 인스턴스와 상호 작용할 수 있습니다.

설치

n8n API 키를 받으세요

  1. n8n 인스턴스에 로그인하세요

  2. 왼쪽 하단의 사용자 아이콘을 클릭하세요

  3. 설정으로 이동

  4. API 선택

  5. "API 키 생성"을 클릭하세요

  6. API 키를 복사하세요(다시는 볼 수 없습니다)

MCP 서버 설치

옵션 1: npm에서 설치(권장)

지엑스피1

옵션 2: 소스에서 설치

  1. 저장소를 복제합니다.

    git clone https://github.com/illuminaresolutions/n8n-mcp-server.git
    cd n8n-mcp-server
  2. 종속성을 설치하고 빌드합니다.

    npm install
    npm run build
  3. 백그라운드에서 서버를 시작합니다.

    nohup npm start > n8n-mcp.log 2>&1 &

    서버를 중지하려면:

    pkill -f "node build/index.js"

참고: npm에서 설치하는 경우 서버는 PATH에 n8n-mcp-server 로 표시됩니다.

Related MCP server: MCP Server for n8n Integration

구성

클로드 데스크탑

  1. Claude Desktop 구성을 엽니다.

    ~/Library/Application Support/Claude/claude_desktop_config.json
  2. n8n 구성을 추가합니다.

    {
      "mcpServers": {
         "n8n": {
          "command": "n8n-mcp-server",
          "env": {
            "N8N_HOST": "https://your-n8n-instance.com",
            "N8N_API_KEY": "your-api-key-here"
          }
        }
      }
    }

클라인(VS 코드)

  1. 서버를 설치하세요(위의 설치 단계를 따르세요)

  2. VS 코드 열기

  3. 왼쪽 사이드바에서 Cline 확장 프로그램을 엽니다.

  4. 창 상단의 'MCP 서버' 아이콘을 클릭하세요.

  5. 아래로 스크롤하여 'MCP 서버 구성'을 클릭하세요.

  6. 열린 설정 파일에 다음을 추가합니다.

    {
      "mcpServers": {
        "n8n": {
          "command": "n8n-mcp-server",
          "env": {
            "N8N_HOST": "https://your-n8n-instance.com",
            "N8N_API_KEY": "your-api-key-here"
          }
        }
      }
    }
  7. 파일을 저장하세요

  8. MCP 토글이 활성화되어 있고(녹색) 상태 표시기가 녹색인지 확인하세요.

  9. Cline에서 MCP 명령 사용 시작

세이지

곧 출시됩니다! n8n MCP 서버는 다음을 통해 이용 가능합니다.

  • Smithery.ai 마켓플레이스

  • Claude Desktop에서 가져오기

지금은 Claude Desktop이나 Cline을 사용하세요.

확인

구성 후:

  1. LLM 신청을 다시 시작하세요

  2. 질문: "내 n8n 워크플로 나열"

  3. 워크플로가 나열되어 있어야 합니다.

오류가 발생하는 경우:

  • n8n 인스턴스가 실행 중인지 확인하세요.

  • API 키에 올바른 권한이 있는지 확인하세요.

  • N8N_HOST에 끝에 슬래시가 없는지 확인하세요.

특징

핵심 기능

  • 워크플로 나열 및 관리

  • 워크플로 세부 정보 보기

  • 워크플로 실행

  • 자격 증명 관리

  • 태그 및 실행 처리

  • 보안 감사 생성

  • 워크플로 태그 관리

엔터프라이즈 기능

다음 기능을 사용하려면 n8n Enterprise 라이선스가 필요합니다.

  • 프로젝트 관리

  • 변수 관리

  • 고급 사용자 관리

문제 해결

일반적인 문제

  1. "클라이언트가 초기화되지 않았습니다"

    • N8N_HOST와 N8N_API_KEY가 올바르게 설정되었는지 확인하세요.

    • n8n 인스턴스에 액세스할 수 있는지 확인하세요.

    • API 키 권한 확인

  2. "면허 필요"

    • Enterprise 기능을 사용하려고 합니다.

    • n8n Enterprise로 업그레이드하거나 핵심 기능만 사용하세요.

  3. 연결 문제

    • n8n 인스턴스가 실행 중인지 확인하세요

    • URL 프로토콜(http/https) 확인

    • N8N_HOST에서 마지막 슬래시를 제거합니다.

보안 모범 사례

  1. API 키 관리

    • 필요한 최소한의 권한만 사용하세요

    • 키를 정기적으로 회전하세요

    • 버전 제어에 키를 커밋하지 마십시오.

  2. 인스턴스 액세스

    • 프로덕션에는 HTTPS를 사용하세요

    • n8n 인증 활성화

    • n8n을 최신 상태로 유지하세요

지원하다

특허

MIT 라이센스

Available Tools

33 tools
activate-workflowC

Activate a workflow by ID. This will enable the workflow to run. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

Inputs: clientId (required), id (required).

create-credentialB

Create a credential that can be used by nodes of the specified type. The credential type name can be found in the n8n UI when creating credentials (e.g., 'cloudflareApi', 'githubApi', 'slackOAuth2Api'). Use get-credential-schema first to see what fields are required for the credential type you want to create.

Inputs: clientId (required), name (required), type (required), data (required).

create-projectA

Create a new project in n8n. NOTE: Requires n8n Enterprise license with project management features enabled. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

Inputs: clientId (required), name (required).

create-tagC

Create a new tag in your instance.

Inputs: clientId (required), name (required).

create-usersC

Create one or more users in your instance.

Inputs: clientId (required), users (required).

create-variableA

Create a new variable in n8n. NOTE: Requires n8n Enterprise license with variable management features enabled. Variables can be used across workflows to store and share data. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

Inputs: clientId (required), key (required), value (required).

create-workflowB

Create a new workflow in n8n. Use to set up a new workflow with optional nodes and connections. IMPORTANT: 1) Arguments must be provided as compact, single-line JSON without whitespace or newlines. 2) Must provide full workflow structure including nodes and connections arrays, even if empty. The 'active' property should not be included as it is read-only.

Inputs: clientId (required), name (required), nodes, connections.

deactivate-workflowC

Deactivate a workflow by ID. This will prevent the workflow from running. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

Inputs: clientId (required), id (required).

delete-credentialB

Delete a credential by ID. You must be the owner of the credentials.

Inputs: clientId (required), id (required).

delete-executionC

Delete a specific execution by ID.

Inputs: clientId (required), id (required).

delete-projectA

Delete a project by ID. NOTE: Requires n8n Enterprise license with project management features enabled. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

Inputs: clientId (required), projectId (required).

delete-tagC

Delete a tag by ID.

Inputs: clientId (required), id (required).

delete-userC

Delete a user from your instance.

Inputs: clientId (required), idOrEmail (required).

delete-variableA

Delete a variable by ID. NOTE: Requires n8n Enterprise license with variable management features enabled. Use after list-variables to get the ID of the variable to delete. This action cannot be undone. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

Inputs: clientId (required), id (required).

delete-workflowA

Delete a workflow by ID. This action cannot be undone. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

Inputs: clientId (required), id (required).

generate-auditC

Generate a security audit for your n8n instance.

Inputs: clientId (required), daysAbandonedWorkflow, categories.

get-credential-schemaA

Show credential data schema for a specific credential type. The credential type name can be found in the n8n UI when creating credentials (e.g., 'cloudflareApi', 'githubApi', 'slackOAuth2Api'). This will show you what fields are required for creating credentials of this type.

Inputs: clientId (required), credentialTypeName (required).

get-executionC

Retrieve a specific execution by ID.

Inputs: clientId (required), id (required), includeData.

get-tagC

Retrieve a specific tag by ID.

Inputs: clientId (required), id (required).

get-userC

Get user by ID or email address.

Inputs: clientId (required), idOrEmail (required).

get-workflowB

Retrieve a workflow by ID. Use after list-workflows to get detailed information about a specific workflow. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

Inputs: clientId (required), id (required).

get-workflow-tagsC

Get tags associated with a workflow.

Inputs: clientId (required), workflowId (required).

init-n8nA

Initialize connection to n8n instance. Use this tool whenever an n8n URL and API key are shared to establish the connection. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

Inputs: url (required), apiKey (required).

list-executionsC

Retrieve all executions from your instance with optional filtering.

Inputs: clientId (required), includeData, status, workflowId, +1 more.

list-projectsA

List all projects from n8n. NOTE: Requires n8n Enterprise license with project management features enabled. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

Inputs: clientId (required).

list-tagsC

Retrieve all tags from your instance.

Inputs: clientId (required), limit.

list-usersB

Retrieve all users from your instance. Only available for the instance owner.

Inputs: clientId (required).

list-variablesA

List all variables from n8n. NOTE: Requires n8n Enterprise license with variable management features enabled. Use after init-n8n to see available variables. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

Inputs: clientId (required).

list-workflowsB

List all workflows from n8n. Use after init-n8n to see available workflows. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

Inputs: clientId (required).

update-projectB

Update a project's name. NOTE: Requires n8n Enterprise license with project management features enabled. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

Inputs: clientId (required), projectId (required), name (required).

update-tagC

Update a tag's name.

Inputs: clientId (required), id (required), name (required).

update-workflowC

Update an existing workflow in n8n. Use after get-workflow to modify a workflow's properties, nodes, or connections. IMPORTANT: Arguments must be provided as compact, single-line JSON without whitespace or newlines.

Inputs: clientId (required), id (required), workflow (required).

update-workflow-tagsC

Update tags associated with a workflow.

Inputs: clientId (required), workflowId (required), tagIds (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 33 tools

    Disambiguation4/5

    Most tools have distinct purposes targeting specific resources like workflows, credentials, projects, tags, users, variables, and executions. However, some tools like 'create-users' and 'delete-user' (singular vs plural) could cause minor confusion, and 'get-workflow-tags' vs 'update-workflow-tags' are closely related but still distinguishable.

    Naming Consistency5/5

    Tool names follow a highly consistent verb-noun pattern with hyphens (e.g., create-workflow, list-executions, delete-credential). All tools adhere to this convention, making them predictable and easy to parse, with no mixing of styles like camelCase or snake_case.

    Tool Count3/5

    With 33 tools, the count is borderline high for an MCP server, as it may feel heavy and overwhelming for agents. While n8n is a complex automation platform, the tool set could potentially be streamlined or grouped to reduce cognitive load, though it does cover a broad domain.

    Completeness5/5

    The tool set provides comprehensive CRUD/lifecycle coverage for all key n8n resources: workflows (activate, deactivate, create, get, update, delete, list), credentials (create, delete, get-schema), projects (create, delete, list, update), tags (create, delete, get, list, update), users (create, delete, get, list), variables (create, delete, list), and executions (delete, get, list). There are no obvious gaps, and tools like init-n8n and generate-audit add useful functionality.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers