| FMRS | 58 / 100 · C | 79 / 100 · B |
|---|
| Reliability | 8 / 20 | 12 / 20 |
|---|
| Security and permissions | 12 / 20 | 18 / 20 |
|---|
| Maintenance | 13 / 20 | 16 / 20 |
|---|
| Documentation | 14 / 20 | 18 / 20 |
|---|
| Setup experience | 11 / 20 | 15 / 20 |
|---|
| Best for | - Developers building n8n automation with Claude, Cursor, Windsurf, VS Code, Codex, or Antigravity.
- n8n users who need node documentation, template discovery, and workflow validation.
- Teams that want to self-host n8n-MCP or use it through the hosted dashboard.
| - Engineering teams scaling AI coding agents while controlling spend
- Platform teams that need auditable, rollback-aware agent execution records
- Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
|
|---|
| Not for | - Automation scenarios that do not use n8n.
- Users who need n8n instance management without configuring the n8n API.
- Production workflow changes made without testing.
| - Developers who just want a simple code-completion helper without run governance
- Teams unwilling to accept local JSONL run records with HMAC signing
- Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
|
|---|
| Required permissions | - Permissions required for basic node, documentation, template, and validation features are not specified in the source.
- n8n management features require N8N_API_URL and N8N_API_KEY.
- Credential and data-table tools may access sensitive n8n data; the source recommends disabling them in governance-sensitive environments.
| - Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
- Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
- Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
- Execution of user-configured verifier commands (e.g. npm test)
|
|---|
| Risks and side effects | - AI-generated results may be unpredictable; the source explicitly warns against editing production workflows directly.
- Copy workflows, test in development, back up important workflows, and validate changes before deployment.
- Enabling workflow write, delete, credential, or data-table management increases potential impact.
| - Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
- Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
- Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
- Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
|
|---|
| Supported clients | Claude Desktop, Claude Code, Windsurf, Cursor, VS Code, Codex, Antigravity | Claude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue |
|---|
| Tools | 24 | 0 |
|---|