Originally published on integrationstars.com. Facts checked against Celigo's developer documentation on November 3, 2026.
Celigo now gives you two first-party ways to work with an integrator.io account outside the UI:
https://api.integrator.io/celigo-mcp (plus EU, AU and CA). Nothing to install.@celigo/celigo-cli): every REST resource as a celigo <resource> <verb> command, with profiles, JSON/YAML/table/CSV output and --jq filtering. Generally available since April 5, 2026; needs Node.js 22+; MIT licensed.
Both call the same REST API with the same permissions. Neither can do more than the signed-in user or the token could do through the API.
| You want to | Use |
|---|---|
| Ask questions and make one-off fixes in plain language | Platform MCP |
| Script repeatable changes or run checks in CI | Celigo CLI |
| Let a coding assistant build and troubleshoot from your machine | Celigo CLI (with Celigo skills loaded) |
| Call integrator.io from your own code or a runtime without Node.js | REST API |
A common pattern: diagnose in a chat client, then turn the fix into a reviewed CLI change.
Not to be confused with the Celigo MCP Server (the mcpServers resource you build to expose your own tools) or MCP Management (Celigo's gateway for governing MCP access). A tool you defined in an MCP Server can only do what you built it to do; Platform MCP can do anything your user or token can.
list_* tools read, upsert_* tools create or update, and delete_resource deletes. Four details from Celigo's tool reference:
upsert_* with an _id is a PUT of the whole document; patch_flow exists for single-field flow edits.upsert_connection keeps a stored secret when the ****** mask is sent back.read, operate or full (default celigo push --dry-run. list_audit_log_entries filters by source, including mcp and cli. A separate token per agent makes each change attributable.
npm install -g @celigo/celigo-cli
celigo login
celigo pull --integration <integration-id> --dir ./acme --no-symlinks
cd acme
git init && git add . && git commit -m "baseline"
celigo status
celigo diff
celigo lint
celigo push --dry-run
celigo push
celigo promote --to sandbox
Safety rules worth knowing: lint runs offline against Celigo's published API schemas; push refuses any resource changed since your pull; push refuses connection documents that still hold the ****** mask; a tree is bound to the API host and token owner it was pulled with; promote needs full mode on the target.
Full guide, with the release timeline and FAQ: integrationstars.com. Sources: Celigo Developer Platform, Platform MCP, Platform MCP tools, Celigo CLI, profiles and permission modes, local tree, 2026 changelog, @celigo/celigo-cli on npm.