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

# Connect your AI app

Ava works with any app that supports MCP (Model Context Protocol). Once connected, just ask in plain language, for example *"research what's trending for my brand and draft three video briefs"*, and your assistant picks the right Ava tools.

The server URL is always:

```
https://mcp.avastudio.com/mcp
```

ChatGPT and Claude connect with [Sign in with Ava](/api-and-mcp/sign-in-with-ava.md): no key needed. Claude Code, Cursor and other agents use an [API key](/api-and-mcp/api-keys.md).

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

1. In ChatGPT on the web, open **Settings > Security and login** and turn on **Developer mode**.
2. Open **Plugins**, click **+**, then **Add custom MCP server**.
3. Name it **Ava**, paste the server URL above, choose **OAuth** for authentication, then create it.
4. Sign in to Ava when asked, check the permissions and click **Allow**.

Developer mode needs ChatGPT Plus, Pro, Business, Enterprise or Edu.
{% endtab %}

{% tab title="Claude" %}
For claude.ai and Claude Desktop:

1. Open **Customize > Connectors**, click **+**, then **Add custom connector**.
2. Paste the server URL above, click **Add**, then **Connect**.
3. Sign in to Ava when asked, check the permissions and click **Allow**.

On Team and Enterprise plans, an owner adds the connector first, under **Organization settings > Connectors**.

**Using an API key instead (Claude Desktop).** Open **Settings > Developer > Edit Config**, add this to `claude_desktop_config.json` with your key in place of `<your key>`, then restart Claude. It needs Node.js 18 or later. Claude Desktop doesn't read your shell's environment, so the key lives in this file: keep it to yourself.

```json
{
  "mcpServers": {
    "ava": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.avastudio.com/mcp",
        "--header",
        "x-api-key:${AVA_API_KEY}"
      ],
      "env": {
        "AVA_API_KEY": "<your key>"
      }
    }
  }
}
```

{% endtab %}

{% tab title="Claude Code" %}
Add this to `.mcp.json` in your project. Claude Code fills in `AVA_API_KEY` from the environment it starts in.

```json
{
  "mcpServers": {
    "ava": {
      "type": "http",
      "url": "https://mcp.avastudio.com/mcp",
      "headers": {
        "x-api-key": "${AVA_API_KEY}"
      }
    }
  }
}
```

Then set the key in the terminal you start Claude Code from:

```bash
read -rs AVA_API_KEY && export AVA_API_KEY   # paste the key, press Enter
claude
```

{% endtab %}

{% tab title="Cursor" %}
Add this to `.cursor/mcp.json` in your project, or to `~/.cursor/mcp.json` for every project. Cursor fills in `AVA_API_KEY` from your environment.

```json
{
  "mcpServers": {
    "ava": {
      "url": "https://mcp.avastudio.com/mcp",
      "headers": {
        "x-api-key": "${env:AVA_API_KEY}"
      }
    }
  }
}
```

{% endtab %}

{% tab title="Other apps" %}
Any MCP client that supports the Streamable HTTP transport can connect:

* **Server URL:** `https://mcp.avastudio.com/mcp`
* **Sign-in:** OAuth ([Sign in with Ava](/api-and-mcp/sign-in-with-ava.md)), or an API key in the `x-api-key` header (or `Authorization: Bearer <key>`).

Your own code can also call the same tools over [REST](/api-and-mcp/quickstart.md): `POST https://mcp.avastudio.com/v1/<tool>`.
{% endtab %}
{% endtabs %}

### Tips

* The [Ava Studio CLI](/api-and-mcp/cli.md#connect-an-mcp-client) can print MCP setup for Claude Code and Cursor with `avastudio mcp config`.
* **Never paste a key into a chat, a command or a file you commit.** Use the `AVA_API_KEY` environment variable as shown above.
* **Your assistant only sees the tools its key or connection allows.** A "Read only" key can look but can't spend credits. See [API keys and permissions](/api-and-mcp/api-keys.md).
* **Set a monthly credit limit** on keys and connected apps you don't watch closely.
* If a tool you expect is missing after an update, disconnect and reconnect the app so it reloads the tool list.