Celigo

What the Celigo MCP server does

The Celigo MCP server gives AI agents access to Celigo integrator.io account operations through the Celigo Platform MCP endpoint. It is intended for working with integration resources rather than serving as a general-purpose automation platform. Agents can inspect account configuration, modify supported resources, run flows, and deploy templates.

The repository also includes domain guidance for Celigo concepts and workflows. Skills cover connections, exports, imports, flows, APIs, tools, B2B integrations, mappings, scripts, SQL, filters, guardrails, lookup caches, marketplace templates, and troubleshooting. These materials help an agent reason about how Celigo resources fit together before making changes.

How it works

The Celigo MCP server is hosted by Celigo and is connected through an MCP URL. The default endpoint is the US service at https://api.integrator.io/celigo-mcp. Authentication uses OAuth: when an agent first needs access, the user is prompted to sign in to Celigo, so an API token is not required for this connection method.

MCP tools generally follow resource-oriented operations such as list_*, upsert_*, and delete_resource. Additional operations include run_flow and deploy_template. The repository also supplies MCP prompts for tasks such as planning an integration, reviewing a flow, diagnosing a connection, troubleshooting a flow, and auditing account health. MCP resources provide reference material on account architecture, settings, connectors, errors, mappings, and tool usage.

Setup and configuration

Install the repository as a native plugin in Claude Code or Cursor, or add it through the Codex plugin marketplace. The plugin includes the skills, slash commands, and Celigo Platform MCP configuration. The repository also documents connections for VS Code, Windsurf, Gemini CLI, Claude Desktop, and Codex CLI.

The default plugin configuration uses the US endpoint. Accounts hosted in the EU, Australia, or Canada need a manually configured regional URL:

• EU: https://api.eu.integrator.io/celigo-mcp
• AU: https://api.au.integrator.io/celigo-mcp
• CA: https://api.ca.integrator.io/celigo-mcp

The separate skills package can be installed with npx skills add celigo/ai, either for all available skills or for a selected skill and agent.

Tools and capabilities

The Celigo MCP server supports account work involving integrations, flows, connections, errors, and jobs. Based on the documented operation patterns, an agent can:

• List supported Celigo resources.
• Create or update supported resources with upsert operations.
• Delete resources through the documented delete operation.
• Run flows and deploy templates.
• Use prompts to plan, review, troubleshoot, and diagnose Celigo configurations.
• Read structured reference resources served over MCP.

The repository also bundles Cursor and Claude Code slash commands for integration planning, Handlebars expressions, SQL, field mappings, and configuration reviews. These commands can assist with authoring even when no Celigo account is connected.

Limitations and notes

The Celigo MCP server does not cover every administrative surface. The local account index, API tokens, stacks, on-premise agents, and users remain available only through the CLI, REST API, or Celigo UI according to the repository documentation.

Regional identity providers matter during OAuth sign-in. A user with an EU, AU, or CA account may not complete authentication against the default US endpoint and must configure the matching regional endpoint instead. The repository's skills also reference the Celigo CLI, but CLI coverage should not be assumed to mean the same operation is available through MCP.