Celigo

Celigo AI

One-stop shop for building integrations on the Celigo platform with AI.

This repo contains:

• Skills -- domain knowledge for AI coding assistants (Claude Code, Cursor, Codex, and 50+ more)
• MCP Prompts & Resources -- content served by the Celigo MCP server

Install Skills

npx skills add celigo/ai

Install specific skills

# List available skills
npx skills add celigo/ai --list

# Install one skill
npx skills add celigo/ai --skill getting-started

# Install to a specific agent
npx skills add celigo/ai --skill configuring-exports -a claude-code

Install as a Plugin

This repo is also a native plugin for Claude Code, Cursor, Codex, and Grok Build, bundling all of the skills below plus the Celigo Platform MCP server.

Claude Code -- in the app, or with the claude CLI:

/plugin marketplace add celigo/ai
/plugin install celigo@celigo

Cursor -- team admins can add this repo directly under Team Marketplaces. To add only the MCP server, use the one-click Add to Cursor link in Connect the Celigo MCP server.

Codex -- run codex plugin marketplace add celigo/ai, then install celigo from the Plugins Directory in the ChatGPT desktop app.

Grok Build -- install it straight from this repo. --trust lets the plugin's MCP server run:

grok plugin install celigo/ai --trust

For 50+ other agents, use the skills install above.

Installing the plugin also configures the Celigo Platform MCP server. It authenticates via OAuth -- the first time an agent uses it, you'll be prompted to sign in to Celigo, so no API token is required.

Each region runs its own identity provider, so the sign-in only completes against the region that hosts your account. The plugin connects to the US endpoint (https://api.integrator.io/celigo-mcp) unless you pick another region:

• Claude Code: choose Celigo region when the plugin asks, or change it later with /plugin configure celigo@celigo. From the CLI, pass it at install: claude plugin install celigo@celigo --config api_host=api.eu.integrator.io. The region picker needs Claude Code 2.1.271 or later.
• Cursor: set the plugin's Celigo region (CELIGO_API_HOST) under Plugins -> Configure in the Cursor dashboard, or set a CELIGO_API_HOST environment variable (for example api.eu.integrator.io), which takes precedence.
• Grok Build: open /mcps, select Celigo (it shows setup required), and pick your region. The server doesn't start until you do, even for US. To switch regions later, set a CELIGO_API_HOST environment variable (for example api.eu.integrator.io), which takes precedence.
• Codex: the plugin always uses the US endpoint. For the EU, AU, or CA, add your region's server by hand -- see Codex CLI.

The plugin connects to one region at a time. To work in accounts in more than one region, add each extra region as its own server under a different name, such as Celigo-EU. See Regions for every region's endpoint.

Using Claude (claude.ai, Desktop, or mobile)? Celigo is in Claude's connectors directory for every region: Add to Claude, then select Connect and pick your region's URL.

Using a different client -- VS Code, Windsurf, Gemini CLI, Codex CLI, or Claude Desktop's config file? See Connect the Celigo MCP server for one-click Add to Claude, Add to Cursor, and Install in VS Code links and copy-paste config.

Skills

Skill how-tos show celigo CLI commands, but most operations map directly to the bundled Celigo Platform MCP server's tools (list_* / upsert_* / delete_resource / run_flow / deploy_template), so agents connected over MCP follow the same skills and translate the command blocks. A few admin surfaces (the local account index, stacks, on-premise agents, users) remain CLI/REST/UI-only, and API tokens are managed only in the UI.

Choosing the CLI or the MCP server

Both reach the same integrator.io account, and most skills work on either:

• The Celigo Platform MCP server has nothing to install: chat clients such as Claude, Cursor, and VS Code sign in with OAuth and call its tools. It covers the everyday build-and-fix loop -- connections, exports, imports, flows, integrations, scripts, APIs, tools, AI agents, guardrails, lookup caches, MCP servers, EDI profiles, file definitions, Celigo Storage files, templates, and users, plus running flows and reading and triaging their errors and execution logs.
• The Celigo CLI suits agents with a shell. It adds the local file-tree workflow (celigo pull, diff, push, promote, lint), the account index (celigo account snapshot|search|dependencies|lint), and every domain the deployed MCP server has no tools for.

The deployed MCP server has no tools today for syncs, Event Streams topics, network policies, end users and their groups and roles, Storage Query and the hosted SFTP file server, stacks, on-premise agents, test runs of flows, tools and APIs, integration and flow clones, integration revisions and snapshots, connection pings and debug logs, export and import invokes, processor runs (Handlebars, filters, file parsers), notifications, long-runtime alerts, event reports, and recycle-bin restores and purges other than Celigo Storage files. For those, use the CLI, the integrator.io REST API, or the UI; API tokens are managed only in the UI. Where a skill has a references/mcp.md, it says what the server can and can't do for that skill.

Slash Commands

The plugin bundles slash commands for Cursor and Claude Code -- skills-backed helpers. The authoring ones work without a connected account; /celigo-troubleshoot reads the account through the CLI or the MCP server when either is connected:

MCP Prompts & Resources

The mcp/ directory contains prompts and resources served by the Celigo MCP server via the MCP protocol's prompts/list, prompts/get, resources/list, and resources/read endpoints, and the server's instructions. Newer server builds also serve the skills themselves, at skill://celigo/<name>/<path> and through a get_skill tool; the deployed server serves the prompts and resources only — see mcp/README.md.

Prompts

Resources

Adding MCP content

See the MCP README for the frontmatter schema and how the Celigo MCP server consumes these files.

Celigo CLI

The skills reference the Celigo CLI for examples. Install it with:

npm install -g celigo-cli

API and UI alternatives are noted where applicable.

Links

• Celigo Documentation
• Celigo Developer Guide
• Agent Skills Specification
• Skills Directory

License

MIT