n8n-mcp/CHANGELOG.md

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

[Unreleased]

[2.33.1] - 2026-01-12

Fixed

• Docker image version mismatch bug: Docker images were built with stale package.runtime.json (v2.29.5) while npm package was at v2.33.0
  • Root cause: build-docker job in release.yml did not sync package.runtime.json version before building
  • The publish-npm job synced the version, but both jobs ran in parallel, so Docker got the stale version
  • Added "Sync runtime version" step to release.yml build-docker job
  • Added "Sync runtime version" step to docker-build.yml build and build-railway jobs
  • All Docker builds now sync package.runtime.json version from package.json before building

[2.33.0] - 2026-01-08

Added

AI-Powered Documentation for Community Nodes

Added AI-generated documentation summaries for 537 community nodes, making them accessible through the MCP get_node tool.

Features:

• README Fetching: Automatically fetches README content from npm registry for all community nodes
• AI Summary Generation: Uses local LLM (Qwen or compatible) to generate structured documentation summaries
• MCP Integration: AI summaries exposed in get_node with mode='docs'

AI Documentation Structure:

{
  "aiDocumentationSummary": {
    "purpose": "What this node does",
    "capabilities": ["key features"],
    "authentication": "API key, OAuth, etc.",
    "commonUseCases": ["practical examples"],
    "limitations": ["known caveats"],
    "relatedNodes": ["related n8n nodes"]
  },
  "aiSummaryGeneratedAt": "2026-01-08T10:45:31.000Z"
}

New CLI Commands:

npm run generate:docs              # Full generation (README + AI summary)
npm run generate:docs:readme-only  # Only fetch READMEs from npm
npm run generate:docs:summary-only # Only generate AI summaries
npm run generate:docs:incremental  # Skip nodes with existing data
npm run generate:docs:stats        # Show documentation statistics
npm run migrate:readme-columns     # Migrate database schema

Environment Variables:

N8N_MCP_LLM_BASE_URL=http://localhost:1234/v1  # LLM server URL
N8N_MCP_LLM_MODEL=qwen3-4b-thinking-2507       # Model name
N8N_MCP_LLM_TIMEOUT=60000                       # Request timeout

Files Added:

• src/community/documentation-generator.ts - LLM integration with Zod validation
• src/community/documentation-batch-processor.ts - Batch processing with progress tracking
• src/scripts/generate-community-docs.ts - CLI entry point
• src/scripts/migrate-readme-columns.ts - Database migration script

Files Modified:

• src/database/schema.sql - Added npm_readme, ai_documentation_summary, ai_summary_generated_at columns
• src/database/node-repository.ts - Added AI documentation methods and fields
• src/community/community-node-fetcher.ts - Added fetchPackageWithReadme() and batch fetching
• src/community/index.ts - Exported new classes
• src/mcp/server.ts - Added AI documentation to get_node docs mode response

Statistics:

• 538/547 community nodes have README content
• 537/547 community nodes have AI-generated summaries

[2.32.1] - 2026-01-08

Fixed

• Community node case sensitivity bug: Fixed extractNodeNameFromPackage to use lowercase node names, matching n8n's community node convention (e.g., chatwoot instead of Chatwoot). This resolves validation failures for community nodes with incorrect casing.
• Case-insensitive node lookup: Added fallback in getNode to handle case differences between stored and requested node types for better robustness.

[2.32.0] - 2026-01-07

Added

Community Nodes Support (Issues #23, #490)

Added comprehensive support for n8n community nodes, expanding the node database from 537 core nodes to 1,084 total nodes (537 core + 547 community).

New Features:

• 547 community nodes indexed (301 verified + 246 popular npm packages)
• source filter for search_nodes: Filter by all, core, community, or verified
• Community metadata in search results: isCommunity, isVerified, authorName, npmDownloads
• Full schema support for verified community nodes (no additional parsing needed)

Data Sources:

• Verified nodes fetched from n8n Strapi API (api.n8n.io/api/community-nodes)
• Popular npm packages from npm registry (keyword: n8n-community-node-package)

New CLI Commands:

npm run fetch:community              # Full rebuild (verified + top 100 npm)
npm run fetch:community:verified     # Verified nodes only (fast)
npm run fetch:community:update       # Incremental update (skip existing)

Example Usage:

// Search only community nodes
search_nodes({query: "scraping", source: "community"})

// Search verified community nodes
search_nodes({query: "pdf", source: "verified"})

// Results include community metadata
{
  nodeType: "n8n-nodes-brightdata.brightData",
  displayName: "BrightData",
  isCommunity: true,
  isVerified: true,
  authorName: "brightdata.com",
  npmDownloads: 1234
}

Files Added:

• src/community/community-node-service.ts - Business logic for syncing community nodes
• src/community/community-node-fetcher.ts - API integration for Strapi and npm
• src/scripts/fetch-community-nodes.ts - CLI script for fetching community nodes

Files Modified:

• src/database/schema.sql - Added community columns and indexes
• src/database/node-repository.ts - Extended for community node fields
• src/mcp/tools.ts - Added source parameter to search_nodes
• src/mcp/server.ts - Added source filtering and community metadata to results
• src/mcp/tool-docs/discovery/search-nodes.ts - Updated documentation

Fixed

Dynamic AI Tool Nodes Not Recognized by Validator (Issue #522)

Fixed a validator false positive where dynamically-generated AI Tool nodes like googleDriveTool and googleSheetsTool were incorrectly reported as "unknown node type".

Root Cause: n8n creates Tool variants at runtime when ANY node is connected to an AI Agent's tool slot (e.g., googleDrive → googleDriveTool). These dynamic nodes don't exist in npm packages, so the MCP database couldn't discover them during rebuild.

Solution: Added validation-time inference that checks if the base node exists when a *Tool node type is not found. If the base node exists, the Tool variant is treated as valid with an informative warning.

Changes:

• workflow-validator.ts: Added inference logic for dynamic Tool variants
• node-similarity-service.ts: Added high-confidence (98%) suggestion for valid Tool variants
• Added 7 new unit tests for inferred tool variant functionality

Behavior:

• googleDriveTool with existing googleDrive → Warning: INFERRED_TOOL_VARIANT
• googleSheetsTool with existing googleSheets → Warning: INFERRED_TOOL_VARIANT
• unknownNodeTool without base node → Error: "Unknown node type"
• supabaseTool (in database) → Uses database record (no inference)

[2.31.8] - 2026-01-07

Deprecated

USE_FIXED_HTTP Environment Variable (Issue #524)

The USE_FIXED_HTTP=true environment variable is now deprecated. The fixed HTTP implementation does not support SSE (Server-Sent Events) streaming required by clients like OpenAI Codex.

What changed:

• SingleSessionHTTPServer is now the default HTTP implementation
• Removed USE_FIXED_HTTP from Docker, Railway, and documentation examples
• Added deprecation warnings when USE_FIXED_HTTP=true is detected
• Renamed npm script to start:http:fixed:deprecated

Migration: Simply unset USE_FIXED_HTTP or remove it from your environment. The SingleSessionHTTPServer supports both JSON-RPC and SSE streaming automatically.

Why this matters:

• OpenAI Codex and other SSE clients now work correctly
• The server properly handles Accept: text/event-stream headers
• Returns correct Content-Type: text/event-stream for SSE requests

The deprecated implementation will be removed in a future major version.

[2.31.7] - 2026-01-06

Changed

• Updated n8n from 2.1.5 to 2.2.3
• Updated n8n-core from 2.1.4 to 2.2.2
• Updated n8n-workflow from 2.1.1 to 2.2.2
• Updated @n8n/n8n-nodes-langchain from 2.1.4 to 2.2.2
• Rebuilt node database with 540 nodes (434 from n8n-nodes-base, 106 from @n8n/n8n-nodes-langchain)

[2.31.6] - 2026-01-03

Changed

Dependencies Update

• Updated n8n from 2.1.4 to 2.1.5
• Updated n8n-core from 2.1.3 to 2.1.4
• Updated @n8n/n8n-nodes-langchain from 2.1.3 to 2.1.4
• Rebuilt node database with 540 nodes (434 from n8n-nodes-base, 106 from @n8n/n8n-nodes-langchain)

[2.31.5] - 2026-01-02

Added

MCP Tool Annotations (PR #512)

Added MCP tool annotations to all 20 tools following the MCP specification. These annotations help AI assistants understand tool behavior and capabilities.

Annotations added:

• title: Human-readable name for each tool
• readOnlyHint: True for tools that don't modify state (11 tools)
• destructiveHint: True for delete operations (3 tools)
• idempotentHint: True for operations that produce same result when called repeatedly (14 tools)
• openWorldHint: True for tools accessing external n8n API (13 tools)

Documentation tools (7): All marked readOnlyHint=true, idempotentHint=true

• tools_documentation, search_nodes, get_node, validate_node, get_template, search_templates, validate_workflow

Management tools (13): All marked openWorldHint=true

• Read-only: n8n_get_workflow, n8n_list_workflows, n8n_validate_workflow, n8n_health_check
• Idempotent updates: n8n_update_full_workflow, n8n_update_partial_workflow, n8n_autofix_workflow
• Destructive: n8n_delete_workflow, n8n_executions (delete action), n8n_workflow_versions (delete/truncate)

[2.31.4] - 2026-01-02

Fixed

Workflow Data Mangled During Serialization: snake_case Conversion (Issue #517)

Fixed a critical bug where workflow mutation data was corrupted during serialization to Supabase, making 98.9% of collected workflow data invalid for n8n API operations.