Skip to main content
Glama
andrewlwn77

n8n-workflow-downloader-mcp

by andrewlwn77
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

n8n Workflow Downloader MCP Server

npm version

An MCP (Model Context Protocol) server that enables AI agents to download n8n workflows from URLs.

Features

  • Download n8n workflows from URLs like https://n8n.io/workflows/3442

  • Returns the complete workflow JSON structure

  • Includes metadata (workflow ID, name, URL)

  • Handles errors gracefully

Related MCP server: n8n-MCP

Installation

As a global npm package

npm install -g n8n-workflow-downloader-mcp

For development

git clone https://github.com/andrewlwn77/n8n-workflow-downloader-mcp.git
cd n8n-workflow-downloader-mcp
npm install
npm run build

Usage

With Claude Desktop or other MCP clients

Add to your MCP configuration:

Using npx (recommended):

{
  "mcpServers": {
    "n8n-workflow-downloader": {
      "command": "npx",
      "args": ["n8n-workflow-downloader-mcp"],
      "transport": {
        "type": "stdio"
      },
      "env": {
        "PUPPETEER_EXECUTABLE_PATH": "/opt/google/chrome/google-chrome"
      }
    }
  }
}

If installed globally via npm:

{
  "mcpServers": {
    "n8n-workflow-downloader": {
      "command": "n8n-workflow-downloader",
      "transport": {
        "type": "stdio"
      },
      "env": {
        "PUPPETEER_EXECUTABLE_PATH": "/opt/google/chrome/google-chrome"
      }
    }
  }
}

If installed locally or from source:

{
  "mcpServers": {
    "n8n-workflow-downloader": {
      "command": "node",
      "args": ["./path/to/build/index.js"],
      "transport": {
        "type": "stdio"
      },
      "env": {
        "PUPPETEER_EXECUTABLE_PATH": "/opt/google/chrome/google-chrome"
      }
    }
  }
}

Environment Variables

  • PUPPETEER_EXECUTABLE_PATH (optional): Path to Chrome/Chromium executable

    • If not set, Puppeteer will use its bundled Chromium

    • Useful for systems with Chrome installed in non-standard locations

    • Example: /opt/google/chrome/google-chrome, /usr/bin/chromium-browser

Available Tools

download_n8n_workflow

Downloads an n8n workflow from a given URL.

Input:

Output:

  • workflow: The complete n8n workflow JSON object

  • metadata: Object containing:

    • id: The workflow ID

    • name: The workflow name

    • url: The original URL

Example usage in Claude:

Please download the n8n workflow from https://n8n.io/workflows/3442

Development

# Install dependencies
npm install

# Build TypeScript
npm run build

# Watch mode for development
npm run dev

# Run tests
npm test

# Run specific test suites
npm run test:unit        # Unit tests only
npm run test:integration # Integration tests only

# Run tests in watch mode
npm run test:watch

# Generate test coverage report
npm run test:coverage

# Test the server manually (for debugging/development)
node test-server.js

Testing

The project includes comprehensive test coverage:

  • Unit Tests (tests/unit/): Test individual modules in isolation

    • Downloader module validation and error handling

    • URL parsing and validation

    • Mock puppeteer interactions

  • Integration Tests (tests/integration/): Test the complete MCP server

    • Server initialization

    • Tool listing and discovery

    • End-to-end workflow download simulation

    • Error handling and validation

Run npm test to execute all tests, or use the specific test commands listed above.

Manual Testing

The test-server.js script provides a quick way to manually test the MCP server:

  • Initializes the server

  • Lists available tools

  • Demonstrates a tool call

  • Shows real-time server output

This is useful for debugging and development, complementing the automated test suite.

Technical Details

  • Uses Puppeteer to automate the workflow download process

  • Intercepts clipboard operations to capture workflow JSON

  • Built with TypeScript and the official MCP SDK

  • Implements stdio transport for local communication

  • Supports custom Chrome/Chromium executable paths via PUPPETEER_EXECUTABLE_PATH

Requirements

  • Node.js 16+

  • Chrome/Chromium (for Puppeteer)

Available Tools

1 tool
download_n8n_workflowDownload n8n WorkflowA

Download an n8n workflow from a given URL and return its JSON structure

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesThe n8n workflow URL (e.g., https://n8n.io/workflows/3442)

TDQS

A3.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the return format (JSON structure) but omits important details such as network fetch behavior, potential errors, or side effects. This leaves a significant transparency gap for a network-dependent operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no redundancy. Every word contributes to conveying the core action and output, making it exceptionally concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with one parameter and no output schema, the description covers the basic action and result but lacks guidance on error handling, output structure specifics, or typical usage context. It is minimally complete but leaves room for improvement, especially given the absence of annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already fully describes the single 'url' parameter with an example, so schema coverage is 100%. The description adds no extra semantic value beyond restating that a URL is used, which aligns with the baseline of 3 for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the tool's function: downloading an n8n workflow from a URL and returning its JSON structure. It uses a specific verb ('Download') and resource ('n8n workflow') with a concrete outcome, making the purpose unambiguous even without sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or alternative guidance is provided, but the description implies usage: when you have an n8n workflow URL and need its JSON representation. Since no sibling tools exist, the lack of exclusionary guidance is acceptable, though more explicit context would improve the score.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

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

  1. 1 tool updatev1.0.0
    • First observeddownload_n8n_workflow
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.8/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly described.

Naming Consistency5/5

The single tool name follows a consistent verb_noun pattern ('download_n8n_workflow'), which is clear and predictable.

Tool Count3/5

One tool feels thin for a server, but it is appropriate for the narrow purpose of downloading n8n workflows. The count is borderline but not unreasonable.

Completeness5/5

The tool fully covers the server's stated purpose of downloading a workflow from a URL. There are no obvious missing operations for this narrow domain.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers