feat: add workflowNodeType field to MCP tool responses for proper n8n workflow creation
- Added workflowNodeType field to all node-returning MCP tools - AI agents now receive both internal format (nodes-base.webhook) and workflow format (n8n-nodes-base.webhook) - Created getWorkflowNodeType() utility to construct proper n8n format from package name - Solves issue where AI agents would search nodes and use wrong format in workflows - No database changes required - uses existing package_name field - Updated: search_nodes, get_node_info, get_node_essentials, get_node_as_tool_info, validate_node_operation - Updated CHANGELOG.md with comprehensive documentation of the changes This completes the fix for issue #71, ensuring AI agents can seamlessly create workflows with the correct node type format without manual intervention.
This commit is contained in: