n8n MCP Server Trigger Node and associated Tools.

[devin95835]

May need to take a look at whether or not this more recent type of node and workflow builder made it into the library. I have literally been arguing with Claude as it keeps trying to tell me the node types I am using in a Google Docs/Sheets/Drive MCP Server I built in n8n "don't exist", that they are "phantom tool types". When I try to correct it and it goes back to the library, it comes back again telling me the node types don't exist. Problem is, you can't, for example, connect standard Google Doc or Sheet tools to an MCP Server Trigger. You can only utilize the ones that have been made available for that node type, which have a different tool type names.
Claude:
"Your workflow has phantom node types that don't exist in n8n:

n8n-nodes-base.googleDocsTool ❌
n8n-nodes-base.googleSheetsTool ❌
n8n-nodes-base.googleDriveTool ❌

The correct node types should be:

n8n-nodes-base.googleDocs ✅
n8n-nodes-base.googleSheets ✅
n8n-nodes-base.googleDrive ✅

However, when these regular nodes are connected to an MCP Server Trigger, they should automatically become available as tools."

Then, after I pointed out its erroneous conclusion:
"Ah! Now I see it clearly. The MCP Server Trigger can ONLY connect to LangChain tool nodes from the @n8n/n8n-nodes-langchain package. Looking at your workflow, you're using node types that literally don't exist.
The solution is to use HTTP Request Tool or Code Tool or Call n8n Sub-Workflow Tool to wrap the Google operations. Let me check if there are actual Google-specific tool nodes:"

My favorite LLM n8n default, go straight to the HTTP Request or Code nodes.