> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adside.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect your assistant

> Add Adside to Claude, ChatGPT, Claude Code or Codex with one URL.

Adside runs a remote [MCP](https://modelcontextprotocol.io) server. You add its URL to your assistant, sign in, and your assistant can work in Adside. There is nothing to install.

```text theme={null}
https://api.adside.ai/mcp
```

You need an Adside account with at least one workspace. To read or change campaigns, connect the ad platform to that workspace in Adside first.

> [tab] Claude
>
> Works on Claude web, Claude Desktop and the mobile apps, on every plan.
>
> **1. Open Connectors**
>
> In Claude, open **Customize**, then **Connectors**. Click the **+** button, then **Add custom connector**.
>
> **2. Add Adside**
>
> Name it `Adside`, paste the URL above, and click **Continue**.
>
> ![Claude's Add custom connector dialog, with Adside as the name and https://api.adside.ai/mcp as the server URL.](https://mintcdn.com/adside/xksYHBZTy9Zq3N_P/images/connect/claude-add-custom-connector.webp?fit=max\&auto=format\&n=xksYHBZTy9Zq3N_P\&q=85\&s=a3087c61255abb5f4020bcd3c4ba7b47)
>
> **3. Sign in**
>
> When Claude opens the Adside sign-in, sign in and click **Allow**. If you belong to several organizations, pick the one Claude should use.
>
> **4. Turn it on in a chat**
>
> In a chat, click **+**, then **Connectors**, and switch **Adside** on.
>
> ![Claude's chat menu, open on Connectors, with the Adside switch on.](https://mintcdn.com/adside/xksYHBZTy9Zq3N_P/images/connect/claude-turn-on-adside.webp?fit=max\&auto=format\&n=xksYHBZTy9Zq3N_P\&q=85\&s=cdec12dc2dfd49fca18dad257792bcd0)
>
> > [!NOTE]
> >
> > On a Team or Enterprise plan, an owner adds the connector first under **Organization settings**, **Connectors**, **Add**, **Custom**, **Web**. Then each member opens **Customize**, **Connectors** and clicks **Connect** on Adside.
>
> Claude asks you to sign in again when your access expires.

> [tab] ChatGPT
>
> ChatGPT connects to custom MCP servers on the **Business**, **Enterprise** and **Edu** plans. You add one in ChatGPT on the web: the mobile apps can't. Who can add it depends on the plan:
>
> * **Business**: workspace admins and owners.
> * **Enterprise and Edu**: admins, owners, and members an admin gave the **Create plugins with MCPs** permission.
>
> On **Pro**, ChatGPT can use Adside's read tools only, so it can report on your accounts but not change them. Other plans can't add a custom MCP server.
>
> **1. Open Plugins**
>
> In ChatGPT on the web, open **Plugins**. Select the **+** button, then **Add custom MCP server**. You don't need to turn on Developer mode first.
>
> **2. Add Adside**
>
> Name it `Adside`. Under **Connection**, paste the URL above, and set authentication to **OAuth**. ChatGPT shows a risk warning for every custom server: tick **I understand and want to continue**, then select **Create as a plugin**.
>
> **3. Sign in**
>
> When ChatGPT opens the Adside sign-in, sign in and click **Allow**. If you belong to several organizations, pick the one ChatGPT should use. ChatGPT then lists the Adside tools it found.
>
> **4. Use it in a chat**
>
> Install the plugin and start a new chat. Type **@** and pick **Adside**.
>
> The pick covers one message. You can keep discussing the answer without it, but mention Adside again when a follow-up needs new data or a change. One message can mention several apps.
>
> **Approvals.** ChatGPT may ask you to approve a tool call first, depending on the permission you chose for Adside, such as **Always ask** or **Allow read actions**. For a change that reaches people or is hard to undo, Adside also asks for its own [confirmation](https://docs.adside.ai/confirmations.md), so you may approve twice. Deep research can use Adside's read tools, never its changes.
>
> **New Adside tools.** ChatGPT keeps the list of tools it found when you added Adside. To pick up tools Adside has added since, open Adside in **Plugins** and select **Refresh**.
>
> > [!NOTE]
> >
> > To give your whole workspace Adside, an admin or owner publishes it: in the **Admin Console**, select the workspace, open **Plugins**, then **Manage Legacy Apps**, **Drafts** and **Publish**. On Enterprise and Edu, **Configure Access** chooses which groups get it and **Configure Actions** which tools are on. Members then find Adside in **Settings**, **Plugins**, and each signs in with their own Adside account, so each can do only what their Adside role allows. A published app keeps the tools it was approved with: when Adside adds or changes tools, an admin refreshes them in the workspace's app settings.
>
> If it doesn't work:
>
> * **No Add custom MCP server option**: your plan or role doesn't allow it. Ask a workspace admin.
> * **Adside shows Disabled by admin**: an admin needs to allow or publish it for the workspace.
> * **Calls fail after an Adside update**: the tools ChatGPT kept are out of date. Refresh them as above.
> * **ChatGPT lost access**: Adside lets ChatGPT renew its access, so this is rare. Reconnect Adside from **Settings**, **Plugins**.

> [tab] Claude Code
>
> Run this in your terminal:
>
> ```bash theme={null}
> claude mcp add --transport http adside "https://api.adside.ai/mcp"
> ```
>
> Then type `/mcp` in Claude Code. Adside shows as connected after you sign in once.

> [tab] Codex
>
> Run this in your terminal:
>
> ```bash theme={null}
> codex mcp add adside --url "https://api.adside.ai/mcp"
> ```
>
> Or add it to `~/.codex/config.toml`, which the CLI and the IDE extension share:
>
> ```toml theme={null}
> [mcp_servers.adside]
> url = "https://api.adside.ai/mcp"
> ```
>
> In the Codex terminal UI, use `/mcp` to see the servers you have connected.

## Try asking

* "Which of my workspaces has the highest CPA this week?"
* "Summarize the brand guidelines for my workspace."
* "What did our competitors launch this month?"

## Without a browser

For CI, scheduled scripts or a cloud agent, send a [personal API key](https://docs.adside.ai/authentication.md#personal-api-keys) instead of signing in. That page has the setup for Claude Code, Codex, the Claude API, the OpenAI Responses API and n8n.

## Other MCP clients

Any client that supports remote servers can connect. Adside uses Streamable HTTP and OAuth 2.1 with PKCE and dynamic client registration, and it does not offer a standalone event stream.

## Give an assistant fewer tools

Some clients limit how many tools they load. Add `features` to the URL to show only the areas you need:

```text theme={null}
https://api.adside.ai/mcp?features=reporting,brain
```

This narrows what the assistant sees and nothing more: your permissions decide what it can do either way. You can also name single tools with `tools=list_competitors,search_brain`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.