> 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/claude-code.md).

# Claude Code

Connect Celigo Platform MCP to [Claude Code](https://claude.com/claude-code), Anthropic's CLI agent.

## Prerequisites

* Claude Code installed and signed in.
* An integrator.io user (see [Connect a client](/mcp/connect.md)).

## Connect

Add the server with one command. Claude Code stores it and reconnects automatically.

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

Swap the host to target another region. See [Pick your endpoint](/mcp/connect.md#pick-your-endpoint).

Run the command from the directory you work in. No git repository is required. By default, Claude Code registers the server for that directory only. Add `--scope user` to make it available in every directory.

Then authenticate: in a Claude Code session, run `/mcp`, select **celigo**, and choose **Authenticate**. Your browser opens the Celigo sign-in page. Sign in and pick the account and environment the agent should work in.

To share the server with your team, run the `add` command from the project directory with `--scope project`, which writes it to a checked-in `.mcp.json`.

Confirm it registered:

```bash
claude mcp list
```

### Use an API token instead

For headless use, or if you prefer a token, pass it as a header when adding the server.

> ⚠️ **`--scope project` saves your token to a checked-in file.** The `Authorization` header, including the token, is written to `.mcp.json` at the project root. Keep that file out of version control so you never commit a live token.

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

## Verify

In a Claude Code session, ask:

> List my Celigo connections.

Claude Code calls `list_connections`, asks you to approve the tool call, and reports the result.


---

# 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/claude-code.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.