Request: Version compatibility documentation (n8n-mcp ↔ n8n instance versions & editions)

Problem

When using n8n-mcp to build workflows for an n8n instance, there's no clear documentation about:

1. Which n8n instance version each n8n-mcp release targets
2. Which n8n edition (Cloud vs Community) the node database was sourced from and tested against

The README shows a badge indicating "n8n version: 2.4.4", but it's unclear whether this refers to n8n Cloud or n8n Community Edition, and there's no compatibility matrix.

Why This Matters

Version mismatch concern:

• n8n-mcp bundles a pre-built SQLite database with node schemas
• If n8n-mcp targets a newer n8n version than my instance, it may suggest nodes/parameters that don't exist
• Workflows built using newer node documentation will fail when deployed to older instances

Edition mismatch concern:

• n8n Cloud and n8n Community Edition may have different:
  • Available nodes (some nodes may be Cloud-only or Community-only)
  • Feature availability
  • API capabilities
  • Release timelines (Cloud often gets updates before Community)
• Users need to know if the node database was built from Cloud docs vs Community docs

Suggested Improvements

1. Compatibility matrix in README or docs:

   n8n-mcp version	n8n Cloud version	n8n Community version	Database source	Release date
   2.33.x	2.4.4	1.70.x	Cloud docs	2026-01-xx
   2.30.x	2.3.x	1.68.x	Cloud docs	...

2. Clarify in README:

   • Is the node database sourced from n8n Cloud documentation or Community Edition documentation?
   • Has it been tested against both editions?
   • Are there any Cloud-only or Community-only nodes in the database?

3. Release notes that mention:

   • Which n8n version(s) the database was built from
   • Which edition(s) were tested

4. (Optional) A tool parameter to filter nodes by edition compatibility (e.g., edition: "community")

Environment

• n8n-mcp version: 2.31.1 (via npx)
• n8n instance: Self-hosted Community Edition on Hostinger
• Use case: Building workflows via Claude Code MCP integration

Questions for Maintainers

1. Is the current node database sourced from n8n Cloud or Community Edition documentation?
2. Are both editions tested before release?
3. Is there a recommended update strategy for users running self-hosted Community Edition?