n8n

Manage n8n workflows via REST authoring and MCP runtime execution.

1|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/anntnzrb/agents --skill n8n-anntnzrb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n
Source: https://github.com/anntnzrb/agents/tree/main/assets/skills/n8n
Command: npx skills add https://github.com/anntnzrb/agents --skill n8n-anntnzrb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires httpx, and includes scripts (resource) and assets (resource) components.

What problem does it solve?

n8n automation via REST API (authoring) and MCP (runtime). Use REST for workflow CRUD; use MCP for listing/triggering enabled workflows.

Core Features & Use Cases

  • REST-based authoring: create, update, and activate workflows via REST endpoints.
  • MCP runtime: list enabled workflows and trigger them through MCP.
  • n8nctl CLI: manage REST interactions without curl or jq for quick automation.

Quick Start

Create a workflow using the REST API, then enable it for MCP execution and trigger it through MCP.

Frequently Asked Questions about n8n

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate n8n workflow management without using curl or jq?

You can automate n8n workflow management using the n8nctl CLI, which handles REST API interactions for creating, updating, and activating workflows without manual curl or jq commands.

How do I trigger n8n workflows through MCP at runtime?

To trigger n8n workflows through MCP, annotate workflows as availableInMCP, then use the MCP URL and access token to list and execute enabled workflows at runtime.

Does n8n automation support self-hosted, cloud, and local deployments?

n8n automation supports self-hosted, cloud, and local deployments, requiring an n8n base URL and REST API key for authoring, plus an MCP URL and access token for runtime execution.

What's the best way to create and enable an n8n workflow for MCP execution?

The best way is to create the workflow via REST API authoring endpoints, then annotate it as availableInMCP and trigger it through the MCP runtime using the required access token.

Do I need REST API credentials and MCP tokens separately for n8n automation?

Yes, n8n automation requires an n8n base URL and REST API key for workflow CRUD authoring, plus a separate MCP URL and access token for listing and triggering workflows at runtime.

Why use REST for n8n workflow authoring and MCP for runtime execution?

REST handles workflow CRUD operations like creation and activation, while MCP provides the runtime layer to list and trigger only workflows annotated as availableInMCP for execution.