> 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/mcp/connect.md).

# Connect a client

Connecting takes two things: a Celigo API token and a one-time entry in your AI client's MCP config. Most people are running in under five minutes.

## Quickstart

1. **Create a token.** In [integrator.io](https://integrator.io), go to **Resources > API tokens**, create a **full-access** token, and copy it (it is shown only once).
2. **Add the server to your client.** Fastest path, Claude Code:

   ```bash
   claude mcp add --transport http celigo \
     https://api.integrator.io/celigo-mcp \
     --header "Authorization: Bearer YOUR_API_TOKEN"
   ```

   On any other client, paste this and swap in your token:

   ```json
   {
     "mcpServers": {
       "celigo": {
         "url": "https://api.integrator.io/celigo-mcp",
         "headers": { "Authorization": "Bearer YOUR_API_TOKEN" }
       }
     }
   }
   ```
3. **Verify.** Ask the agent: *"List my Celigo connections."* If it returns a summary of your connections, you are connected.

For exact steps in your client, including where the config lives and the success indicator to look for, use the guide for yours:

* [Claude Code](/mcp/connect/claude-code.md)
* [Claude Desktop](/mcp/connect/claude-desktop.md)
* [Cursor](/mcp/connect/cursor.md)
* [VS Code](/mcp/connect/vscode.md)
* [ChatGPT](/mcp/connect/chatgpt.md)
* [Windsurf](/mcp/connect/windsurf.md)
* [Other MCP clients](/mcp/connect/other-clients.md)

## Pick your endpoint

The endpoint is region-specific, and a token works only in its own region.

| Region | Endpoint                                  |
| ------ | ----------------------------------------- |
| US     | `https://api.integrator.io/celigo-mcp`    |
| EU     | `https://api.eu.integrator.io/celigo-mcp` |

If you sign in at `integrator.io` you are on US; at `eu.integrator.io` you are on EU.

## About the token

The server uses the same Bearer token as the REST API and respects the same permissions, so the agent can do what you could do through the API and nothing more. Full-access tokens are needed for most write operations. Treat the token like a password: do not commit it to source control or paste it in shared chats, and rotate it in **Resources > API tokens** when needed. A project config file that holds your token should stay out of version control.

## Troubleshooting

| What you see                             | Usual cause and fix                                                                                     |
| ---------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| Calls fail with `401`                    | Token is wrong, expired, or from the other region. Re-check the token and that the endpoint matches it. |
| Calls fail with `403`                    | The token lacks permission for that action. Most writes need a full-access token.                       |
| Calls fail with `422`                    | The agent sent invalid data. Ask it to call `get_schema` first to learn the correct fields.             |
| The client will not connect              | Confirm it supports Streamable HTTP and that the URL and `Authorization` header are correct.            |
| Tools do not appear after editing config | Fully quit and reopen the client. Closing the window is often not enough.                               |


---

# 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/mcp/connect.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.