Trying to publish a flow as an own MCP action in Langdock. It is published and MCP access is allowed. I can integrate the URL in Langdock and it connects successful but it looks like no action is available in that integration.
@nephilim make sure the MCP Server Trigger node is the start of your workflow, not a regular webhook or manual trigger — Langdock won’t discover actions unless the workflow actually starts with the MCP Server Trigger and has at least one tool node wired to it.
@nephilim your regular nodes (Check Attachment, If, Send Email etc) can’t connect directly to the MCP Server Trigger’s tools output — you need to wrap them inside a Custom n8n Workflow Tool node, that’s the piece you’re missing. Drop a Custom n8n Workflow Tool node between the MCP Server Trigger and your logic, it acts as the “action” that Langdock discovers