Mcp
Back to PlatformAutomation platforms & MCP
How iPaaS tools (Zapier, Make, n8n, Workato) relate to Onboard REST and MCP.
MCP is optimized for interactive AI clients (desktop assistants, IDE integrations) that speak HTTP/SSE or stdio. Automation platforms such as Zapier, Make, n8n, or Workato usually integrate through REST and webhooks instead of MCP.
When to use which
| Surface | Typical use |
|---|---|
| REST API | Scheduled jobs, multi-step recipes, system-to-system sync |
| Webhooks | Event-driven fan-out when something changes in Onboard |
| MCP | Human-in-the-loop copilots in AI tools that support MCP |
You can use both: for example Zapier for provisioning and an MCP client for day-to-day CS questions on the same data.
Platform notes
- Zapier — Official Onboard app and triggers/actions: Onboard.io on Zapier. See Integrations.
- Workato — Enterprise recipes and governance; see Onboard’s Workato integration (Learning Center).
- Make / n8n / other iPaaS — Use generic HTTP modules with
Authentication against
https://rest.onboard.io, plus Webhooks for inbound events.
MCP alongside automation
Use MCP where a person steers an AI session; use iPaaS where policy-driven automation must run without a human at the keyboard. If you need architecture advice for splitting workloads, email [email protected].
Related
- Integrations — iPaaS, Retool, and API-first options
- MCP setup — hosted MCP URLs
- AI workflow examples
How is this guide?