n8n MCP Server (Custom)
Related Servers
Alternatives to n8n MCP Server (Custom)
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceA comprehensive MCP server that provides full control over n8n automation workflows through natural language. It offers 43 tools for managing workflows, executions, credentials, and data tables, with safety features like write-mode protection and double-validated workflow creation.431MIT
- FlicenseBqualityCmaintenanceA full-power MCP server for n8n that enables AI agents to create, read, update, delete, and test workflows and credentials, including webhook testing, validation, and backup/versioning.319-
- AlicenseAqualityDmaintenance🪄 MCP server for programmatic creation and management of n8n workflows. Enables AI assistants to build, modify, and manage workflows without direct user intervention through a comprehensive set of tools and resources for interacting with n8n's REST API.1038 npm86MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides AI assistants with access to documentation, schemas, and operations for over 535 n8n workflow automation nodes. It enables models to understand, create, and manage n8n workflows through natural language by connecting to the n8n API.79,567 npmMIT
- FlicenseBqualityBmaintenanceEnables AI assistants to fully automate n8n instances via 34 MCP tools, covering workflow creation, execution debugging, credential management, environment variables, tags, and user administration through natural language.341-
- AlicenseBqualityAmaintenanceMCP server for managing n8n workflows through AI assistants. Supports workflow CRUD operations, synchronization, inspection, and execution support for automation-focused workflows.19311 npm2MIT
TDQS
Scored across 27 tools
Each tool targets a distinct resource and action (e.g., list_workflows vs. get_workflow vs. execute_workflow). Even similar tools like get_instance_info and get_instance_version are clearly separated by their descriptions (health vs. version/settings). No two tools appear to do the same thing.
All tools follow the same n8n_verb_noun pattern, with verbs like list, get, create, update, delete, execute, stop, activate, deactivate. The naming is uniform and predictable, with no mixed conventions.
27 tools is on the higher side, but the server covers a broad domain (workflows, executions, credentials, variables, tags, node types, instance info). Each tool serves a clear purpose within that scope, so the count feels justified rather than bloated.
The toolset provides solid CRUD/lifecycle coverage for workflows, credentials, variables, and executions. Minor gaps exist, such as no create/update/delete for tags and no workflow import/export, but the core workflows an agent would need are well covered.