n8n Manager for AI Agents

Why it's ranked here

The tool covers the core workflow and execution loop, validates inputs, supports cursor pagination, retries selected transient failures, and works around incompatible workflow update methods. The decisive drawback is lifecycle status: development has stopped, and the author directs users to the broader n8n-mcp project for current features and updates.

What's good

The implementation anticipates awkward n8n API behavior. It supplies required workflow defaults, strips read-only fields before updates, and falls back from PATCH to PUT when needed. Tool descriptions explain operational constraints to the agent, including full-node updates and matching webhook methods. File-only logging keeps protocol output clean, while typed errors distinguish authentication, authorization, rate limits, timeouts, and network failures.

Tradeoffs

Workflow activation still requires the n8n interface, and direct execution works only through an active webhook trigger. The exposed tools cannot manage users or credentials, stop running executions, handle variables, or import and export workflows. Tags cannot be written. Update requests may require fetching and resending the full workflow. The repository is no longer actively developed, so unresolved compatibility issues should not be expected to receive updates here.

How to use it well

Use it for an existing n8n installation when an agent needs routine workflow editing, execution inspection, cleanup, webhook triggering, and connection checks. It fits controlled operator workflows where manual activation is acceptable and API credentials can be supplied through environment variables. Start with the health check, fetch before updating, and preserve the full node graph. Choose the successor project for ongoing development or broader automation. Keep the n8n interface for activation, credentials, users, and stopping executions.

Observed

License

MIT

Primary language

TypeScript with ES modules

Runtime

Node.js 20 or higher

Install surface

Clone the repository, install dependencies with npm, then compile with the TypeScript build script

Interfaces

Model Context Protocol over standard input and output, backed by n8n API v1 and webhook HTTP requests

Tool surface

Eleven MCP tools covering workflows, executions, webhooks, health checks, and tool discovery

Lifecycle

The repository is no longer actively developed; its management tools moved into n8n-mcp