> For the complete documentation index, see [llms.txt](https://docs.carto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carto.com/carto-for-agents/cli/installation.md).

# Installation

The CARTO CLI is published on npm as [`@carto/carto-cli`](https://www.npmjs.com/package/@carto/carto-cli) and installs as a global `carto` binary.

## Prerequisites

* **Node.js 22 or newer.** Check with `node --version`.
* A CARTO organization. The CLI works against CARTO Cloud (any region) and CARTO Self-Hosted deployments.

{% hint style="warning" %}
**CARTO Self-Hosted compatibility**

The CARTO CLI evolves with the rest of the CARTO Platform. The latest version of the CARTO CLI will always be compatible with CARTO Cloud. However, newer versions of the CLI might not be compatible with older versions of CARTO Self-Hosted deployments, due to missing API functionalities.

For a full compatibility list, check the [CARTO Self-Hosted release notes](/carto-self-hosted/release-notes.md).
{% endhint %}

## Install via npm

```bash
npm install -g @carto/carto-cli
```

Verify the install:

```bash
carto --version
carto --help
```

## Upgrade

```bash
npm install -g @carto/carto-cli@latest
```

## Next steps

* [Authenticate](/carto-for-agents/cli/authentication.md) to your CARTO organization with `carto auth login`.
* If you manage multiple CARTO organizations or environments, set up [named profiles](/carto-for-agents/cli/authentication.md#multiple-profiles).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.carto.com/carto-for-agents/cli/installation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.