> For the complete documentation index, see [llms.txt](https://developer.celigo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.celigo.com/readme.md).

# Celigo Developer Platform

Build, automate, and extend integrator.io from code. The API, CLI, and Platform MCP give you full control over every resource in your account — integrations, flows, connections, imports, exports, scripts, tools, AI agents, and more.

## Developer tools

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>API</strong></td><td>REST reference and guides — auth, pagination, rate limits, errors, and a full endpoint browser.</td><td><a href="https://developer.celigo.com/api">https://developer.celigo.com/api</a></td></tr><tr><td><strong>CLI</strong></td><td>Command-line tool with profiles, structured output, utilities like snapshot, search, and lint, and a local file tree you pull, review in git, and push back.</td><td><a href="https://developer.celigo.com/cli">https://developer.celigo.com/cli</a></td></tr><tr><td><strong>Platform MCP</strong></td><td>Connect AI agents — Claude, Cursor, Windsurf — to your integrator.io account.</td><td><a href="https://developer.celigo.com/mcp">https://developer.celigo.com/mcp</a></td></tr></tbody></table>

## Which tool to use

All three tools work on the same integrator.io resources with the same permissions. Pick the one that matches how you work. You can combine them.

| You want to                                                                                           | Use              | Why                                                                                                                                                                                                |
| ----------------------------------------------------------------------------------------------------- | ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Call integrator.io from your own code, or from a runtime without Node.js                              | **API**          | Direct REST access to every resource. You write the HTTP calls.                                                                                                                                    |
| Work in a terminal, script repeatable changes, or run in CI                                           | **CLI**          | Wraps the REST API with account profiles, JSON or table output, and account-wide utilities.                                                                                                        |
| Let an AI coding assistant — Claude Code, Cursor, Windsurf — build and troubleshoot from your machine | **CLI**          | Installing the CLI also installs [AI assistant skills](https://developer.celigo.com/cli/using-the-cli/skills). The assistant then runs `celigo` commands with grounded knowledge of integrator.io. |
| Ask questions and make changes in plain language from an AI client — Claude, ChatGPT, Cursor, VS Code | **Platform MCP** | Hosted by Celigo, nothing to install. Sign in with your Celigo credentials. The agent gets your permissions in the account and environment you pick.                                               |

The CLI and Platform MCP call the same REST API, so you can move between them. Explore and triage in a chat client, then script the repeatable steps with the CLI.

## Get started

{% columns %}
{% column width="50%" %}
Every developer tool shares the same API token. Create one in integrator.io, then pick your path below.

{% hint style="info" %}
**One token, three tools**

Your API token works with the REST API, CLI, and Platform MCP. Create it once at **Resources → API tokens** in [integrator.io](https://integrator.io) and you're ready for all three. Platform MCP can also sign in with your Celigo credentials — no token required.
{% endhint %}

{% hint style="warning" %}
**Need help?**

<details>

<summary>401 Unauthorized</summary>

Check that your token is correct and hasn't expired. Tokens are region-specific and work only against their own region's endpoint.

</details>

<details>

<summary>CLI command not found</summary>

Make sure you have Node.js 22+ and ran `npm install -g @celigo/celigo-cli`. Run `celigo --version` to verify.

</details>

<details>

<summary>MCP client not connecting</summary>

Confirm the `url` in your MCP client config and complete the browser sign-in when it opens. If you connect with a token instead, check the `Authorization` header. The endpoint is region-specific: `https://api.integrator.io/celigo-mcp` (US), `https://api.eu.integrator.io/celigo-mcp` (EU), `https://api.au.integrator.io/celigo-mcp` (AU), or `https://api.ca.integrator.io/celigo-mcp` (CA).

</details>
{% endhint %}
{% endcolumn %}

{% column width="50%" %}
{% stepper %}
{% step %}

#### Create an API token

Sign in to [integrator.io](https://integrator.io), open **Resources → API tokens**, and select **+ Generate token**. Copy the token — you'll need it next.
{% endstep %}

{% step %}

#### Make your first request

{% tabs %}
{% tab title="cURL" %}

```bash
curl -s https://api.integrator.io/v1/integrations \
  -H "Authorization: Bearer <YOUR_API_TOKEN>"
```

{% endtab %}

{% tab title="CLI" %}

```bash
npm install -g @celigo/celigo-cli
export CELIGO_API_TOKEN="<YOUR_API_TOKEN>"
celigo integrations list --format table
```

{% endtab %}

{% tab title="MCP" %}
Add to your MCP client config — no token needed. Your client opens a browser sign-in on first use:

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

Then ask your agent: **"List my integrations"**

No OAuth support, or prefer a token? Add an `Authorization: Bearer <YOUR_API_TOKEN>` header. See [Connect a client](https://developer.celigo.com/mcp/connect).
{% endtab %}
{% endtabs %}
{% endstep %}

{% step %}

#### See the result

{% tabs %}
{% tab title="cURL" %}

```json
[
  {
    "_id": "5a1b2c3d4e5f6a7b8c9d0e1f",
    "name": "Shopify → NetSuite",
    "createdAt": "2024-05-12T17:02:11.213Z"
  }
]
```

{% endtab %}

{% tab title="CLI" %}

```
┌──────────────────────────┬──────────────────┬─────────┐
│ _id                      │ name             │ mode    │
├──────────────────────────┼──────────────────┼─────────┤
│ 5a1b2c3d4e5f6a7b8c9d0e1f │ Shopify → NetS…  │ install │
└──────────────────────────┴──────────────────┴─────────┘
```

{% endtab %}

{% tab title="MCP" %}
Your agent responds with a summary of your integrations — names, IDs, and status — pulled live from your account.
{% endtab %}
{% endtabs %}
{% endstep %}
{% endstepper %}
{% endcolumn %}
{% endcolumns %}

## More resources

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Training</strong></td><td>Courses and certifications for builders and admins.</td><td><a href="https://training.celigo.com/">https://training.celigo.com/</a></td></tr><tr><td><strong>Community</strong></td><td>Connective — the Celigo customer community.</td><td><a href="https://connective.celigo.com/">https://connective.celigo.com/</a></td></tr><tr><td><strong>Help Center</strong></td><td>Product docs, how-tos, and support tickets.</td><td><a href="https://docs.celigo.com/hc/en-us">https://docs.celigo.com/hc/en-us</a></td></tr><tr><td><strong>Changelog</strong></td><td>Recent API, CLI, and Platform MCP changes.</td><td><a href="https://developer.celigo.com/changelog">https://developer.celigo.com/changelog</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developer.celigo.com/readme.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.