MCP N8n vs Repomix

A side-by-side look at the MCP N8n and Repomix MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

MCP N8n logoMCP N8nDeveloper Tools · Local subprocess (stdio)Operate and build n8n: 61 tools, 560-node catalog, validation, autofix, snapshots and backups.64GoodAuth: not declaredRepomix logoRepomixDeveloper Tools · Local subprocess (stdio)Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search64GoodAuth: not declared

Verdict: choose MCP N8n for developer tools work as a local process; choose Repomix for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

MCP N8n logoChoose MCP N8n when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: N8N_BASE_URL, N8N_API_KEY.
  • You want tools like n8n_create_workflow, n8n_list_workflows, n8n_list_workflows_summary.
Explore MCP N8n

Repomix logoChoose Repomix when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like pack_codebase, directory, compress.
Explore Repomix

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMCP N8n logoMCP N8nRepomix logoRepomix
CategoryDeveloper ToolsDeveloper Tools
Quality signal64/100 · Good64/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsN8N_BASE_URLN8N_API_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars2128,991
Directory activity 1 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
Tools6123

Tools & capabilities

MCP N8n tools 61

  • n8n_create_workflowCreate a new workflow in n8n. Prefer n8n_search_nodes + n8n_validate_workflow first so the JSON is valid. You can specify nodes, connections, and settings.
  • n8n_list_workflowsList all workflows with full details. Can filter by active status, tags, name, or project. WARNING: Returns complete workflow data including nodes and connections - use n8n_list_workflows_summary for better token efficiency.
  • n8n_list_workflows_summaryList workflows with minimal data (id, name, active, tags, updatedAt only). Recommended for browsing and listing - uses 90% fewer tokens than n8n_list_workflows. Use n8n_get_workflow to fetch full details of a specific workflow.
  • n8n_get_workflowGet detailed information about a specific workflow by ID.
  • n8n_update_workflowUpdate an existing workflow. Supports partial updates: omitted fields keep their current values (the current workflow is fetched and merged automatically).
  • n8n_delete_workflowDelete a workflow permanently. A local snapshot is saved first so it can be restored with n8n_rollback_workflow (into a new workflow).
  • n8n_activate_workflowActivate a workflow to start receiving triggers.
  • n8n_deactivate_workflowDeactivate a workflow to stop receiving triggers.
  • n8n_transfer_workflowTransfer a workflow to another project.
  • n8n_get_workflow_tagsGet all tags associated with a workflow.
  • n8n_update_workflow_tagsUpdate tags for a workflow.
  • n8n_list_executionsList workflow executions. Can filter by status, workflow ID, or project. TIP: Set includeData=false and use fields parameter to reduce token usage.
  • +49 more on the listing page

Repomix tools 23

  • pack_codebasePackage a local code directory into a consolidated XML file for AI analysis
  • directoryAbsolute path to the directory to pack
  • compress(Optional, default: false) Enable Tree-sitter compression to extract essential code signatures and structure while removing implementation details. Reduces token usage by ~70% while preserving semantic meaning. Generally not needed since grep_repomix_output allows incremental content retrieval. Use…
  • includePatterns(Optional) Specify files to include using fast-glob patterns. Multiple patterns can be comma-separated (e.g., "**/*.{js,ts}", "src/**,docs/**"). Only matching files will be processed.
  • ignorePatterns(Optional) Specify additional files to exclude using fast-glob patterns. Multiple patterns can be comma-separated (e.g., "test/**,*.spec.js", "node_modules/**,dist/**"). These patterns supplement .gitignore, .ignore, and built-in exclusions.
  • outputPatterns(Optional) Per-file inclusion levels, mirroring the config-file `output.patterns` option. An array of `{ pattern, compress?, directoryStructureOnly? }` entries; the first matching pattern wins, `directoryStructureOnly` takes precedence over `compress`, and a match with neither flag forces full cont…
  • topFilesLength(Optional, default: 10) Number of largest files by size to display in the metrics summary for codebase analysis.
  • attach_packed_outputAttach an existing Repomix packed output file for AI analysis
  • pathPath to a directory containing repomix-output.xml or direct path to a packed repository XML file
  • pack_remote_repositoryFetch, clone, and package a GitHub repository into a consolidated XML file for AI analysis
  • remoteGitHub repository URL or user/repo format (e.g., "yamadashy/repomix", "https://github.com/user/repo", or "https://github.com/user/repo/tree/branch")
  • read_repomix_outputRead the contents of a Repomix-generated output file. Supports partial reading with line range specification for large files.
  • +11 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

MCP N8n

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-n8n": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-n8n"
      ],
      "env": {
        "N8N_BASE_URL": "YOUR_N8N_BASE_URL_HERE",
        "N8N_API_KEY": "YOUR_N8N_API_KEY_HERE"
      }
    }
  }
}

Repomix

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "repomix": {
      "command": "npx",
      "args": [
        "-y",
        "repomix@latest"
      ]
    }
  }
}

Frequently asked questions

MCP N8n is categorized under Developer Tools and uses a local stdio subprocess. Repomix belongs to Developer Tools and uses a local stdio subprocess. Pick MCP N8n for developer tools work and Repomix for developer tools.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

MCP N8n has no declared pricing — check the project's own site. Repomix has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add mcp-n8n and repomix as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, MCP N8n has a quality signal of 64/100 (Good) with 1 views, 0 installs and 21 GitHub stars. Repomix has 64/100 (Good) with 3 views, 0 installs and 28,991 GitHub stars.