{"slug": "celigo-platform-mcp-and-the-celigo-cli-what-they-do-and-how-to-set-them-up", "title": "Celigo Platform MCP and the Celigo CLI: What They Do and How to Set Them Up Safely", "summary": "Celigo released two first-party ways to work with an integrator.io account outside its UI: a hosted Platform MCP endpoint at api.integrator.io/celigo-mcp (with EU, AU and CA variants) that requires no installation, and the MIT-licensed @celigo/celigo-cli, generally available since April 5, 2026, which exposes every REST resource as a 'celigo <resource> <verb>' command with profiles, JSON/YAML/table/CSV output and --jq filtering. Both call the same REST API under the same permissions, so neither can exceed what the signed-in user or token could do. The CLI adds offline linting against Celigo's published API schemas, push that refuses resources changed since the pull or connection documents still holding the '******' secret mask, and promote for writing a tree into another environment.", "body_md": "*Originally published on [integrationstars.com](https://integrationstars.com/celigo/blog/celigo-platform-mcp-cli/?utm_source=devto&utm_medium=referral&utm_campaign=celigo-platform-mcp-cli). Facts checked against Celigo's developer documentation on November 3, 2026.*\n\nCeligo now gives you two first-party ways to work with an integrator.io account outside the UI:\n\n`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.\nBoth 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.\n\n| You want to | Use | \n|---|---|\n| Ask questions and make one-off fixes in plain language | Platform MCP | \n| Script repeatable changes or run checks in CI | Celigo CLI | \n| Let a coding assistant build and troubleshoot from your machine | Celigo CLI (with Celigo skills loaded) | \n| Call integrator.io from your own code or a runtime without Node.js | REST API | \n\nA common pattern: diagnose in a chat client, then turn the fix into a reviewed CLI change.\n\nNot 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.\n\n`list_*` tools read, `upsert_*` tools create or update, and `delete_resource` deletes. Four details from Celigo's tool reference:\n\n`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.\n\n```\nnpm install -g @celigo/celigo-cli\nceligo login\n\n# Pull one integration into a folder and put it in git\nceligo pull --integration <integration-id> --dir ./acme --no-symlinks\ncd acme\ngit init && git add . && git commit -m \"baseline\"\n\n# After editing: check, plan, then write back\nceligo status\nceligo diff\nceligo lint\nceligo push --dry-run\nceligo push\n\n# Write the same tree into another environment\nceligo promote --to sandbox\n```\n\nSafety 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.\n\nFull guide, with the release timeline and FAQ: [integrationstars.com](https://integrationstars.com/celigo/blog/celigo-platform-mcp-cli/?utm_source=devto&utm_medium=referral&utm_campaign=celigo-platform-mcp-cli). Sources: [Celigo Developer Platform](https://developer.celigo.com/), [Platform MCP](https://developer.celigo.com/mcp), [Platform MCP tools](https://developer.celigo.com/mcp/tools), [Celigo CLI](https://developer.celigo.com/cli), [profiles and permission modes](https://developer.celigo.com/cli/getting-started/profiles), [local tree](https://developer.celigo.com/cli/local-tree), [2026 changelog](https://developer.celigo.com/changelog/2026), [@celigo/celigo-cli on npm](https://www.npmjs.com/package/@celigo/celigo-cli).", "url": "https://wpnews.pro/news/celigo-platform-mcp-and-the-celigo-cli-what-they-do-and-how-to-set-them-up", "canonical_source": "https://dev.to/entechsolutions/celigo-platform-mcp-and-the-celigo-cli-what-they-do-and-how-to-set-them-up-safely-2pn0", "published_at": "2026-11-18 20:37:01+00:00", "updated_at": "2026-11-18 20:41:53.582905+00:00", "lang": "en", "topics": ["ai-agents", "agent-protocols", "developer-tools", "ai-tools"], "entities": ["Celigo", "integrator.io", "Celigo Platform MCP", "Celigo CLI", "@celigo/celigo-cli", "Celigo MCP Server", "MCP Management", "Node.js"], "also_reported_by": [], "takeaway": "Celigo's CLI refuses pushes of resources changed since the pull and of connection documents still holding the '******' mask, and binds each pulled tree to the API host and token owner it came from, so use a separate token per agent to keep audit-log entries attributable.", "recommendation": null, "alternates": {"html": "https://wpnews.pro/news/celigo-platform-mcp-and-the-celigo-cli-what-they-do-and-how-to-set-them-up", "markdown": "https://wpnews.pro/news/celigo-platform-mcp-and-the-celigo-cli-what-they-do-and-how-to-set-them-up.md", "text": "https://wpnews.pro/news/celigo-platform-mcp-and-the-celigo-cli-what-they-do-and-how-to-set-them-up.txt", "jsonld": "https://wpnews.pro/news/celigo-platform-mcp-and-the-celigo-cli-what-they-do-and-how-to-set-them-up.jsonld"}}