fix: enhance node type format normalization for better AI agent compatibility (Issue #74)
- Added support for n8n-nodes-langchain.* → nodes-langchain.* normalization - Implemented case-insensitive node name matching (e.g., chattrigger → chatTrigger) - Added smart camelCase detection for common patterns (trigger, request, sheets, etc.) - Fixed get_node_documentation tool to use same normalization logic as other tools - Updated all 7 node lookup locations to use normalized types for alternatives - Enhanced getNodeTypeAlternatives() to normalize all generated alternatives All MCP tools now consistently handle various format variations: - nodes-langchain.chatTrigger (correct format) - n8n-nodes-langchain.chatTrigger (package format) - n8n-nodes-langchain.chattrigger (package + wrong case) - nodes-langchain.chattrigger (wrong case only) - @n8n/n8n-nodes-langchain.chatTrigger (full npm format) Bump version to 2.7.19 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
czlonkowski