> For the complete documentation index, see [llms.txt](https://docs.avis.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avis.net/avis-creative-studio/avis-mcp.md).

# AVIS MCP

AVIS MCP connects the AI tools you already use (ChatGPT, Claude, Claude Code or Codex) to AVIS. Once connected, you can work with AVIS from a prompt in that tool: bring your brief, scenes and creative assets together in AVIS, or create images and videos with your AVIS account.

<figure><img src="https://3712251980-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fd1iOtdhEqFbDy8JzwAnH%2Fuploads%2FKSrVXN2AmDojk7buIQEp%2Fimage.png?alt=media&amp;token=a446ccc3-34dd-4805-adf8-dd671dcd817c" alt="" width="563"><figcaption><p>AVIS MCP page</p></figcaption></figure>

**Open AVIS MCP**

1. On the **Home** screen, select **MCP** in the left sidebar.
2. Under **Connect your AI tools to AVIS**, choose your AI tool. A window opens with the setup steps for that tool. To set it up yourself, click **Set up manually**.

Every tool uses the same **MCP server URL**. Click **Copy** next to it in the window:

```
https://mcp-studio.avis.net/mcp
```

**Connect ChatGPT**

1. Open ChatGPT settings, then **Apps**. If needed, turn on developer mode in **Advanced settings** so you can create a custom connector.
2. Choose **Create** or **Add a custom connector**, depending on your ChatGPT version.
3. Paste the MCP server URL. Choose **OAuth** if asked. Leave the client ID and secret empty when dynamic registration is supported.
4. Sign in with your AVIS account in the browser, review the requested permissions, approve access, then return to ChatGPT.
5. Start a new conversation and ask which AVIS tools are available, to confirm the connection.

<figure><img src="https://3712251980-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fd1iOtdhEqFbDy8JzwAnH%2Fuploads%2FpngfyztM2i15RKOcf09X%2Fimage.png?alt=media&amp;token=944cb410-9296-4fcf-92f8-d8ddf4266dcb" alt="" width="563"><figcaption><p>Connect ChatGPT to AVIS</p></figcaption></figure>

**Connect Claude**

1. Open Claude settings, then **Connectors**.
2. Choose **Add custom connector** and enter **AVIS** as the name.
3. Paste the MCP server URL. Choose **OAuth** if asked. Leave the client ID and secret empty when dynamic registration is supported.
4. Sign in with your AVIS account in the browser, review the requested permissions, approve access, then return to Claude.
5. Start a new conversation and ask which AVIS tools are available, to confirm the connection.

<figure><img src="https://3712251980-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fd1iOtdhEqFbDy8JzwAnH%2Fuploads%2FIOzKU9pZE0EBYHU5JDWo%2Fimage.png?alt=media&amp;token=15c681fb-7052-4e03-bcdb-a17c1d489bbc" alt="" width="563"><figcaption><p>Connect Claude to AVIS</p></figcaption></figure>

**Note:** Custom connectors depend on your ChatGPT or Claude plan and your administrator's settings. If you don't see the option, check with your administrator.

**Connect Claude Code**

The easiest way is the **setup prompt** (recommended): in the window, click **Copy** next to **Setup prompt**, paste it into Claude Code and follow along. To set it up yourself:

1. In the terminal, run:

```
claude mcp add --transport http --scope user avis "https://mcp-studio.avis.net/mcp"
```

2. In Claude Code, run `/mcp`, choose **avis**, then **Authenticate**. Sign in to AVIS in the browser that opens and click **Allow**.
3. Ask Claude Code who is signed in to AVIS and which Workspaces you have, to confirm the connection.

<figure><img src="https://3712251980-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fd1iOtdhEqFbDy8JzwAnH%2Fuploads%2FTkjSWRAFVCPlVoeRQPye%2Fimage.png?alt=media&amp;token=89ab7c31-f592-4ff7-ace0-2bc1b82020f0" alt="" width="563"><figcaption><p>Connect Claude Code with a setup prompt</p></figcaption></figure>

**Connect Codex**

Use the **setup prompt** (recommended) the same way, or set it up yourself:

1. In the terminal, run:

```
codex mcp add avis --url "https://mcp-studio.avis.net/mcp"
```

2. Run `codex mcp login avis`. Sign in to AVIS in the browser that opens and click **Allow**.
3. Ask Codex who is signed in to AVIS and which Workspaces you have, to confirm the connection.

<figure><img src="https://3712251980-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fd1iOtdhEqFbDy8JzwAnH%2Fuploads%2FmkhMDfl8JfzyvdXRYqmv%2Fimage.png?alt=media&amp;token=e76e8a8f-bc5d-491f-800d-172ae1b9b8d3" alt="" width="563"><figcaption><p>Connect Codex with a setup prompt</p></figcaption></figure>

**Credits**

AVIS shows the cost of every generation first and only spends credits after you agree.


---

# 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.avis.net/avis-creative-studio/avis-mcp.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.
