Celigo

Name: Celigo
Author: celigo

by celigoversion 0.12.0i★ –iRuns in the cloud

Registry namecom.celigo/celigo

Install

Overview

Description from the maker (original English)

Manage your Celigo integrator.io account: integrations, flows, connections, errors, and jobs.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://api.integrator.io/celigo-mcp

Run this in your terminal

claude mcp add --transport http celigo https://api.integrator.io/celigo-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "celigo": {
      "url": "https://api.integrator.io/celigo-mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "celigo": {
      "type": "http",
      "url": "https://api.integrator.io/celigo-mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://api.integrator.io/celigo-mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain celigo.com (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
… Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
… Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 32435 servers in this category
Published to the registry more recently than 57% of the other 32435 servers in this category
Basic checks equal to or better than 100% of the other 32435 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Celigo safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.12.0) reached the registry 30 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, Apify MCP Server

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

Apify MCP Server

by apify

Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Celigo AI

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

This repo contains:

[Skills](#skills) -- domain knowledge for AI coding assistants (Claude Code, Cursor, Codex, and 50+ more)
[MCP Prompts & Resources](#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](https://code.claude.com) -- in the app, or with the claude CLI:

/plugin marketplace add celigo/ai

/plugin install celigo@celigo

[Cursor](https://cursor.com) -- 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](https://developers.openai.com/codex) -- run codex plugin marketplace add celigo/ai, then install celigo from the Plugins Directory in the ChatGPT desktop app.

[Grok Build](https://x.ai/cli) -- 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](https://claude.ai/directory/connectors/celigo), 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](docs/connect-mcp.md) 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 / install_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) remain CLI/REST/UI-only, and API tokens are managed only in the UI.

Skill	Description
getting-started	Core concepts, build order, account discovery, and which skill to use
configuring-connections	Credentials, auth methods, OAuth, iClients
configuring-exports	Data source steps -- REST, SOAP, database, file, webhook, delta (incremental) exports
configuring-imports	Data destination steps -- mappings, lookups, upsert logic
building-flows	Pipelines wiring exports to imports -- scheduling, chaining, error management
building-syncs	Data Ingestion syncs -- replicating application tables into a data warehouse, with backfill and schema drift
building-apis	Custom HTTP endpoints for synchronous external access
building-tools	Reusable operations callable from flows, APIs, agents, and MCP servers
building-mcp-servers	MCP endpoints exposing tools to external AI agents
building-b2b	EDI integrations -- trading partners, X12/EDIFACT, file definitions
configuring-ai-agents	LLM-powered import steps on any supported model provider
configuring-filters	Expression and script filters on exports, imports, and branches
configuring-guardrails	PII detection, content moderation, AI-based validation
configuring-lookup-caches	In-memory key-value stores for fast lookups and dedup
configuring-topics	Event Streams topics -- publish once, consume in several flows; retention, messages, listener positions
managing-users	Workspace users -- invitations, permissions, MFA/SSO, access levels
managing-end-users	MCP end users, groups, roles, and capability grants
managing-integrations	Integration containers, cloning, and lifecycle management (ILM) across environments
managing-file-storage	Celigo Storage files and folders, Storage Query, and the hosted SFTP server for partners
managing-api-tokens	Inbound API tokens -- scoping, rotation, revoke/delete lifecycle
managing-network-policies	IP allow and deny lists for API tokens, MCP servers, and sign-in
managing-stacks	Bring-your-own compute for hooks and connector wrappers (server or AWS Lambda)
managing-on-premise-agents	Secure connectivity to private systems behind a firewall
using-marketplace-templates	Install Templates and Integration Apps; copy prebuilt flows
troubleshooting-flows	Diagnosing failures, partial errors, stuck jobs, empty runs
writing-mappings	Mapper 2.0, Transformation 2.0, lookups, response mapping
writing-handlebars	Dynamic template expressions for mappings, URIs, SQL, filters
writing-settings-forms	Settings forms that collect settings on integrations, flow groups, flows, exports, imports, connections, and iClients
writing-scripts	JavaScript hooks -- preSavePage, preMap, postMap, postSubmit
writing-sql	SQL for RDBMS exports/imports across Snowflake, Postgres, MySQL, and more

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](#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:

Command	Description
`/celigo-plan-integration`	Plan a new integration from requirements (design + build order)
`/celigo-handlebars`	Author or debug a Handlebars expression
`/celigo-sql`	Write SQL for an RDBMS export/import
`/celigo-mapping`	Build a field mapping (Mapper 2.0)
`/celigo-review-config`	Review a pasted resource config against best practices
`/celigo-troubleshoot`	Diagnose a failing, partial, empty, or stuck flow and say what to fix (read-only until you ask)

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/ / and through a get_skill tool; the deployed server serves the prompts and resources only — see mcp/README.md.

Prompts

Prompt	Description
getting-started	Orientation for the Celigo MCP server -- core concepts, build order, tool inventory
plan-new-integration	Plan a new integration from requirements
review-flow-config	Review an existing flow configuration
troubleshoot-flow	Diagnose a failing or misbehaving flow
diagnose-connection	Troubleshoot connection issues
audit-account-health	Audit account health and find issues
writing-handlebars	Write Handlebars template expressions

| writing-sql

Only the beginning is shown; read the rest in the repo

Celigo

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

Apify MCP Server

README from the maker

Celigo AI

Install Skills

Install specific skills

Install one skill

Install to a specific agent

Install as a Plugin

Skills

Choosing the CLI or the MCP server

Slash Commands

MCP Prompts & Resources

Prompts