Nodehero
- dinosaur24/zapguard
NodeHero is an MCP server that provides AI workflow error analysis for n8n, Make, Zapier, and 10+ automation platforms.
About
NodeHero MCP connects coding agents to AI-driven analysis when no-code and low-code workflows fail on platforms such as n8n, Make, and Zapier. developers who operate customer automations or their own ops stacks can invoke the stdio npm server nodehero-mcp so the agent interprets error context instead of manually reading opaque platform logs. The package is published from the zapguard repo’s mcp-server subfolder at version 1.0.1. This is monitoring and incident understanding for integration pipelines, not building new workflow nodes in the IDE. Complexity is intermediate because you must map platform-specific failures to the tools’ inputs. It helps when you juggle multiple automation vendors; it does not replace native platform debuggers if you never use MCP or those platforms.
- AI workflow error analysis for automation platforms
- Covers n8n, Make, Zapier, and 10+ platforms per description
- Stdio npm package nodehero-mcp v1.0.1
- Source in dinosaur24/zapguard repository subfolder mcp-server
- No API key listed in published server schema
Nodehero by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add nodehero-mcp -- npx -y nodehero-mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Package | nodehero-mcp |
|---|---|
| Transport | STDIO |
| Auth | None |
| Repository | dinosaur24/zapguard ↗ |
What it does
Diagnose failed n8n, Make, Zapier, and other automation workflows from your agent with AI-backed error analysis over MCP.
Who is it for?
Best when you're running n8n, Make, or Zapier stacks and want MCP-side AI explanations when flows break in production.
Skip if: Skip if you have only custom code paths and no no-code workflows, or developers and need infra metrics instead of workflow-run diagnostics.
What you get
After registering the nodehero-mcp stdio server, your agent can analyze workflow errors and suggest fixes across supported automation platforms.
- AI-interpreted workflow failure analysis via MCP tools
- Actionable guidance oriented toward fixing automation runs
- Cross-platform error insight for 10+ automation vendors (per description)
By the numbers
- Server version 1.0.1; npm identifier nodehero-mcp
- Explicit platforms: n8n, Make, Zapier; description cites 10+ platforms total
- Repository: github.com/dinosaur24/zapguard (mcp-server subfolder)
Recommended MCP Servers
Agent Audit McpImmutable audit trail for agent-to-agent interactions2
Agentguard47Read-only MCP server for coding-agent traces, alerts, costs, usage, and budget health.4
Agentic Observability MCPAgent tracing, cost tracking, anomaly detection for LLM agents
Agent Incident Relay McpAgent Incident Relay MCP — Article 73 5-clock broadcaster.
Agent Infra Mcp18 tools: agent memory, API drift detection, and HMAC-signed trust receipts
Agentmonitorrelay McpAI agent run monitoring with incident replay and SLA receipts.How it compares
Automation error-analysis MCP, not a generic application log aggregator or deployment skill.
FAQ
Who is NodeHero MCP for?
Developers and small teams who depend on n8n, Make, Zapier, or similar platforms and want their coding agent to help interpret workflow failures.
When should I use NodeHero MCP?
Use it in Operate when a scheduled or triggered workflow fails and you need structured error analysis before editing nodes or reconnecting APIs.
How do I add NodeHero to my agent?
Add the npm stdio MCP server nodehero-mcp to your client configuration per your host’s MCP docs and restart; no secret env vars are defined in the published server.json.