Connect
Connect n8n to Ducto
Wire Ducto into n8n workflows with the MCP Client Tool node. n8n runs headless, so authenticate with a bearer token minted in the dashboard — scoped to exactly what the workflow needs.
auth: bearer token, scoped and revocable
01
Mint a scoped token
On the dashboard's MCP page, create a token scoped to the platforms and tool classes this workflow uses. Narrow beats broad — you can always mint another.
02
Add the MCP Client Tool node
In your workflow, add the MCP Client Tool node to an AI agent, set the endpoint, and add the Authorization header:
endpoint: https://mcp.getducto.com/
header: Authorization: Bearer <your-token>
03
Select the tools
The node lists every tool your token allows. Expose all of them to the agent, or hand-pick the few this workflow should ever call.
04
Run governed
Scheduled audits, report drops, budget checks — reads run free, and any write the workflow proposes goes through caps, preview, and your approval classes.
When it doesn't work
The two things that actually go wrong
The node lists no tools
The token's scope doesn't cover any connected platform. Check the Connections page and the token's platform scopes on the MCP page.
Can a workflow approve its own writes?
No. Approval happens in the Ducto dashboard by a signed-in human. A token cannot approve anything — that's the point.
Other clients
Any MCP client over streamable HTTP works — tell us if yours needs a guide.