MCP N8N Webhook Server
Related Servers
Alternatives to MCP N8N Webhook Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceA Model Context Protocol server that enables AI assistants to interact with N8N workflows, executions, and automation capabilities.12MIT
- AlicenseAqualityAmaintenanceA Model Context Protocol server that provides AI assistants with comprehensive access to n8n node documentation, properties, and operations for effective workflow automation.2893,909 npm23,035MIT
- FlicenseNot gradedqualityNot gradedmaintenanceA Model Context Protocol server that enables AI agents to interact with n8n workflows and automation tools through a standardized interface, allowing execution of workflows and access to n8n functions.-
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that provides AI assistants with comprehensive access to n8n node documentation, properties, and operations.93,909 npmMIT
- AlicenseNot gradedqualityFmaintenanceA Model Context Protocol server that enables AI assistants to interact with n8n workflows through natural language, supporting actions like listing, creating, updating, executing and monitoring workflows.600 npm1,632MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that allows AI agents to interact with n8n workflows through natural language, enabling workflow management and execution via SSE connections.87 npm7MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one checks connectivity/status, while the other saves data. There is no overlap or ambiguity between these functions, making it easy for an agent to select the correct tool.
Both tools follow a consistent 'n8n_verb_noun' pattern (n8n_health_check, n8n_save_data). This naming convention is uniform and predictable, enhancing readability and usability.
With only two tools, the server feels thin for a webhook server that might require more operations like listing, updating, or deleting data. This limited scope could hinder agent workflows, indicating an under-provisioned tool surface.
The server lacks essential CRUD operations for a webhook domain; it only offers health checks and data saving. Missing tools for retrieving, updating, or managing webhook data create significant gaps that will likely cause agent failures in broader tasks.