Integrations. Tools that aren’t built-in.
Plooi connects to external tools through the MCP Client (Model Context Protocol). Anything you can reach over MCP folds into the canvas as a regular node.
MCP Client
The MCP Client lets you wire external services into a workflow as tools — internal databases, content repositories, custom APIs, automations. The output flows downstream like any other node.
Typical inputs:
- Server URL
- Query / tool call
- Auth configuration (depending on the tool)
Output:
- Structured tool responses you can feed into Strategy or Creative nodes for further folding.
⚠️
Mind data protection and access control whenever you pull external systems onto the sheet. Plooi forwards what you wire — that’s it.
Best practices
- Stable interfaces — use versioned endpoints.
- Small payloads — only pass the data you actually need.
- Clean separation — treat MCP outputs as structured inputs for the next node, not as final deliverables.