- Add Railway-specific Docker image build to CI/CD workflow
- Builds n8n-mcp-railway image alongside standard image
- Railway image optimized for AMD64 architecture
- Automatically published to ghcr.io on main branch pushes
- Create comprehensive Railway deployment documentation
- Step-by-step deployment guide with security best practices
- Claude Desktop connection instructions via mcp-remote
- Troubleshooting guide for common issues
- Architecture details and single-instance design explanation
- Update README with Railway documentation link
- Removed inline Railway content to keep README focused
- Added link to dedicated Railway deployment guide
This enables zero-configuration cloud deployment of n8n-mcp
with automatic HTTPS, global access, and built-in monitoring.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Enhanced database adapter to support multiple WASM file resolution strategies
- Added require.resolve() for reliable package location in npm environments
- Made better-sqlite3 an optional dependency
- Improved error handling with clear messages
- Updated version to 2.7.13
- Updated CHANGELOG and README badges
- Updated n8n from 1.100.1 to 1.101.1
- Updated n8n-core from 1.99.0 to 1.100.0
- Updated n8n-workflow from 1.97.0 to 1.98.0
- Updated @n8n/n8n-nodes-langchain from 1.99.0 to 1.100.1
- Rebuilt node database with 528 nodes
- All validation tests passing
- Bumped version to 2.7.12
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Database now contains 499 n8n workflow templates
- FTS5 index is properly populated for template search
- Fixes 'no templates found' issue in Docker image
- Template search works with both FTS5 and LIKE fallback
This ensures the Docker image includes a fully populated template database.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Critical fixes based on Claude Desktop feedback:
1. Fixed crypto documentation: require('crypto') IS available despite editor warnings
- Added clear examples of crypto usage
- Updated validation to guide correct require() usage
2. Clarified $helpers vs standalone functions
- $getWorkflowStaticData() is standalone, NOT $helpers.getWorkflowStaticData()
- Added validation to catch incorrect usage (prevents '$helpers is not defined' errors)
- Enhanced examples showing proper $helpers availability checks
3. Fixed JMESPath numeric literal documentation
- n8n requires backticks around numbers in filters: [?age >= `18`]
- Added multiple examples and validation to detect missing backticks
- Prevents 'JMESPath syntax error' that Claude Desktop encountered
4. Fixed webhook data access gotcha
- Webhook payload is at items[0].json.body, NOT items[0].json
- Added dedicated 'Webhook Data Access' section with clear examples
- Created process_webhook_data task template
- Added validation to detect incorrect webhook data access patterns
All fixes based on production workflows TaNqYoZNNeHC4Hne and JZ9urD7PNClDZ1bm
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add bin configuration to package.json for npx execution
- Implement smart database path resolution for npx/global/local installs
- Create dedicated npm publish script using runtime-only dependencies
- Add .npmignore to control published package contents
- Update README with npx as primary installation method
- Add n8n version badge to README
- Sync version between package.json and package.runtime.json
- Update CHANGELOG for v2.7.8 release
This allows users to run 'npx n8n-mcp' without installing the package,
reducing friction and making it easier to get started with n8n-MCP.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add AUTH_TOKEN_FILE environment variable support for reading auth tokens from files
- Support Docker secrets pattern for production deployments
- Add Known Issues section documenting Claude Desktop container duplication bug
- Update documentation with authentication options and best practices
- Fix issue #16: AUTH_TOKEN_FILE was documented but not implemented
- Add comprehensive tests for AUTH_TOKEN_FILE functionality
BREAKING CHANGE: None - AUTH_TOKEN continues to work as before
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Renamed start_here_workflow_guide to tools_documentation for clarity
- Added depth parameter to control documentation detail (essentials/full)
- Converted output from JSON to LLM-friendly plain text format
- Added per-tool documentation capability
- Created two-tier documentation system:
- Essentials: brief info with key parameters and tips
- Full: comprehensive docs with examples and best practices
- Documented 8 commonly used MCP tools
- Removed 380+ lines of unused getWorkflowGuide method
- Fixed duplicate tool definitions
- Updated all documentation references
- Added test script for tools documentation
BREAKING CHANGE: start_here_workflow_guide renamed to tools_documentation
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Created complete CHANGELOG.md from v1.0.0 to v2.7.0 based on git history
- Updated README.md to fix incorrect CHANGELOG path reference
- Added n8n-docs/ directory to .gitignore (was accidentally tracked)
- Removed n8n-docs from git tracking
The CHANGELOG now follows Keep a Changelog format and includes all major features,
fixes, and improvements for each version with proper categorization.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Removed ~965MB of temporary directories (temp/, extracted-nodes/, etc)
- Deleted outdated database files and backups (.bak files)
- Removed legacy shell scripts (mcp-server-v20.sh, rebuild-v20.sh)
- Cleaned up orphan test files and debugging scripts
- Removed duplicate schema file (src/db/schema.sql)
- Deleted old Dockerfile.old and empty database files
- Updated documentation structure in README.md
- Added n8n_diagnostic tool to documentation
- Condensed version history in CLAUDE.md
- Created release notes for v2.7.0
Total impact: Removed 34 files, saving ~965MB+ of disk space
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Added clear separation between basic config (docs only) and full config (with n8n API)
- Showed both configurations side-by-side for Docker and local installation
- Added notes explaining n8n API credentials are optional
- Updated Docker Compose example to show optional environment variables
- Improved HTTP deployment section with both minimal and full configurations
- Removed redundant configuration sections
- Made it clearer that management tools are optional features
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
BREAKING CHANGES:
- Renamed n8n_update_workflow to n8n_update_full_workflow for clarity
NEW FEATURES:
- Added n8n_update_partial_workflow tool for diff-based workflow editing
- Implemented WorkflowDiffEngine with 13 operation types
- Added transactional updates with two-pass processing
- Maximum 5 operations per request for reliability
- Operations can be in any order - engine handles dependencies
- Added validateOnly mode for testing changes before applying
- 80-90% token savings by only sending changes
IMPROVEMENTS:
- Enhanced tool description with comprehensive parameter documentation
- Added clear examples for simple and complex use cases
- Improved error messages and validation
- Added extensive test coverage for all operations
DOCUMENTATION:
- Added workflow-diff-examples.md with usage patterns
- Added transactional-updates-example.md showing before/after
- Updated README.md with v2.7.0 features
- Updated CLAUDE.md with latest changes
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- NEW: n8n_validate_workflow tool to validate workflows from n8n instance by ID
- Fetches workflow via API and runs comprehensive validation
- Uses existing WorkflowValidator for consistency
- Supports all validation profiles and options
- Updated start_here tool with new workflow lifecycle info
- Updated README with new tool documentation
- Updated Claude Project Setup instructions
This completes the workflow lifecycle management:
discover → build → validate → deploy → execute → monitor
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Update axios to 1.7.2 and zod to 3.23.8 for better stability
- Add fast AMD64-only workflow for testing (docker-build-fast.yml)
- Fix multi-platform build issues with better-sqlite3 native compilation
The multi-platform builds were hanging due to better-sqlite3 requiring
native compilation for each platform. This provides a workaround.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Added environment variables (MCP_MODE, LOG_LEVEL, DISABLE_CONSOLE_OUTPUT) to local installation config
- These settings ensure proper stdio communication and clean output for Claude Desktop
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Replace "Docker Desktop" prerequisite with generic "Docker installed"
- Add detailed Docker installation instructions for macOS, Linux, and Windows
- Include package manager options (Homebrew, apt-get, winget, Chocolatey)
- Add Docker verification command
- Update related documentation files for consistency
- Use collapsible section to keep Quick Start clean
Now users understand they can use any Docker installation method, not just Docker Desktop.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Update n8n version from v1.97.1 to v1.99.1 in README
- Fix 7 broken documentation links to point to existing files
- Standardize Docker image size to ~280MB across all docs (was inconsistent: 150MB/200MB/283MB)
- Add missing npm scripts for test commands (test:essentials, test:enhanced-validation, etc.)
- Update CHANGELOG.md with missing versions 2.4.0 through 2.5.1
- Update README_CLAUDE_SETUP.md to list all 21+ MCP tools (was only showing 6)
- Document 5 additional npm scripts in CLAUDE.md
- Update AI-capable nodes count to 263 (was 35 in old docs)
All documentation now accurately reflects the current codebase state.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add comprehensive AI tools guide in start_here_workflow_guide
- New 'ai_tools' topic with detailed AI workflow patterns
- Key insight: ANY node can be used as an AI tool
- $fromAI() expression examples and best practices
- AI tool connection validation guidance
- Update recommended workflow to include validate_node_minimal
- Quick required fields check before full validation
- Performance tips for validation tools
- Enhance Claude Project Setup instructions
- Clear 5-phase workflow process
- Emphasis on AI tool integration
- Validation best practices
- Better tool usage examples
- Add validation_guide section to workflow guide
- When to use each validation tool
- Performance considerations
- AI workflow validation patterns
These updates make it much clearer how to use the MCP tools effectively,
especially for AI workflows where ANY node can be connected as a tool.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Update tool descriptions to clarify ANY node can be used as AI tool
- Add get_node_as_tool_info to available tools in README
- Enhance workflow validation tool descriptions for AI connections
- Update README with v2.5.1 release notes
- Remove redundant _General__Scrape_with_HTTP_tool.json file
- Bump version to 2.5.1 in package.json
The key insight: ANY n8n node can be connected to an AI Agent's tool
port, not just those marked with usableAsTool=true. This update makes
that clear throughout the documentation and tool descriptions.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Phase 2 Professional Validation Features:
1. Validation Profiles:
- minimal: Only required fields
- runtime: Critical errors + security warnings
- ai-friendly: Balanced (default)
- strict: All checks + best practices
2. New Node Validators:
- Webhook: Path validation, response modes, auth warnings
- PostgreSQL: SQL injection detection, query safety
- MySQL: Similar to Postgres with MySQL-specific checks
3. New Tools:
- validate_node_minimal: Lightning-fast required field checking
- Updated validate_node_operation with profile support
4. SQL Safety Features:
- Detects template expressions vulnerable to injection
- Warns about DELETE/UPDATE without WHERE
- Catches dangerous operations (DROP, TRUNCATE)
- Suggests parameterized queries
5. Enhanced Coverage:
- Now supports 7+ major nodes with specific validators
- Flexible validation based on use case
- Professional-grade safety checks
This completes the major validation system overhaul from the original plan.
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
- Update version badge to 2.4.2
- Replace validate_node_config with validate_node_operation in docs
- Add v2.4.2 release notes highlighting validation improvements
- Update Claude Project Setup instructions to use new tool
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
Major optimization that reduces Docker image size by 87% and build time by 10x:
- Remove ALL n8n dependencies from runtime Docker image
- Add package.runtime.json with only 5 essential runtime deps
- Optimize Dockerfile to build TypeScript without n8n packages
- Add BuildKit optimizations with cache mounts
- Update documentation to highlight the improvements
Results:
- Image size: ~1.5GB → ~200MB (87% reduction)
- Build time: ~12 minutes → ~1-2 minutes
- No n8n version conflicts at runtime
- Better security with minimal attack surface
The key insight is that since we always rebuild the database locally
before deployment, the Docker runtime never needs n8n packages.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Fixed the initialization timeout issue with minimal changes:
1. Added stdout flush after server connection to combat Docker buffering
2. Fixed docker-entrypoint.sh to not output to stdout in stdio mode
3. Added process.stdin.resume() to keep server alive
4. Added IS_DOCKER environment variable for future use
5. Updated README to prioritize Docker with correct -i flag configuration
The core issue was Docker's block buffering preventing immediate JSON-RPC
responses. The -i flag maintains stdin connection, and explicit flushing
ensures responses reach Claude Desktop immediately.
Also fixed "Shutting down..." message that was breaking JSON-RPC protocol
by redirecting it to stderr in stdio mode.
Docker is now the recommended installation method as originally intended.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Based on debugging MCP initialization timeout issues:
1. Changed Quick Start to prioritize local installation (working)
2. Moved Docker to Option 2 with experimental warning
3. Added detailed explanation of Docker timeout issue:
- Server receives initialize request but doesn't respond
- Claude times out after 60 seconds
- Container outputs "Shutting down..." breaking JSON-RPC
4. Removed non-existent npx package reference
5. Consolidated configuration file locations
6. Removed HTTP server section from Quick Start (keep it simple)
The Docker issue appears to be related to MCP protocol handling in the
container environment. Local installation works reliably, so that's now
the recommended approach until Docker issues are resolved.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Fixed multiple issues preventing n8n-MCP from working with Claude Desktop:
1. Removed --pull always flag that caused:
- Multiple simultaneous container starts
- Image pulling during JSON-RPC communication
- Timeout errors and connection failures
2. Added --name flag to prevent duplicate containers
3. Added explicit docker pull step to ensure image is ready
4. Proper step numbering for clear setup flow
The logs showed 'Shutting down...' breaking JSON-RPC communication and
multiple containers trying to start simultaneously. This configuration
ensures single, stable container execution.
Tested configuration now works reliably with Claude Desktop.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Major simplification of Docker setup:
- Removed unnecessary docker-compose.yml creation (was causing conflicts)
- Removed volume mounting (not needed for stateless MCP)
- Added --pull always to ensure latest version
- Separated Claude Desktop setup from HTTP server setup
- Fixed the fundamental issue: can't mix service mode with interactive mode
The new approach:
- Claude Desktop: Simple docker run with stdio mode
- HTTP Server: Separate section for team deployments
- No volume conflicts or container name issues
- Works immediately without any prep work
This fixes the configuration that wouldn't work due to:
1. Docker Compose running as daemon vs Claude needing interactive
2. Named volume dependencies
3. Container conflicts
Now it's truly a 5-minute setup with just copy-paste.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Added Node.js prerequisite for Option 2: Local Installation (any version)
- Added Node.js 18+ prerequisite for Option 3: Remote Server
- Added prerequisites section to Local Development Setup
- Clarified that any Node.js version works for local installation due to automatic fallback
This ensures users know they need Node.js installed before attempting local installations.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Major improvements:
- Fixed "95% smaller" to user-friendly "10-20 properties instead of 200+"
- Reorganized documentation section with clear categories:
- Setup Guides
- Usage & Best Practices
- Technical Documentation
- Troubleshooting
- Added comprehensive Claude Project system instructions
- Step-by-step workflow for using MCP tools
- Best practices for n8n automation
- Example workflow demonstration
- Created .github/ABOUT.md for GitHub repository description
- Clear value proposition
- Impact metrics
- Use cases and quick start
The Claude Project instructions provide a complete template for optimal
n8n workflow creation, emphasizing the correct tool usage order and
documentation-first approach.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Added missing `start_here_workflow_guide` tool to Core Tools list
- Added beta warnings for HTTP mode in two places:
- Option 3: Remote Server (Beta)
- Production Deployment section
- Tool list now accurately reflects all 13 available tools
- Clear warning that HTTP mode is under development and not thoroughly tested
This ensures users are aware of the experimental nature of HTTP mode
while still providing the functionality for those who need it.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Major reorganization to improve onboarding and clarity:
Structure changes:
- Moved Claude testimonial up after Overview for immediate social proof
- Quick Start now Docker-first with exact commands (5-minute setup)
- Added Docker Desktop prerequisite
- Features section moved after Quick Start
- Reorganized MCP tools into Core/Advanced categories
- Simplified Claude Desktop configuration with 3 clear options
- Separated Local Development from Quick Start
- Added Production Deployment section for teams
- Updated metrics with performance data
- Added centered footer with community message
Content improvements:
- Clearer docker-compose.yml creation commands
- Exact file paths for Claude Desktop config
- Updated tool examples focusing on essentials
- Consolidated recent updates
- Better categorization of documentation links
The README now provides a smoother path from discovery to deployment,
with Docker as the primary recommended approach.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Added compelling testimonial section after Overview
- Created full interview document in docs/CLAUDE_INTERVIEW.md
- Added quick quote at the top: "Before MCP, I was translating. Now I'm composing."
- Highlights real-world impact: 45 minutes → 3 minutes workflow creation
- Shows concrete before/after examples with 6 errors → 0 errors
- Demonstrates value beyond just time savings (confidence, discovery, peace of mind)
The testimonial provides social proof and helps users understand the practical
benefits of n8n-MCP through a relatable first-person experience.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
