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

# Connectors & Custom MCP

> Connect Shopify, HubSpot, Google Sheets, and thousands of other apps — plus your own MCP servers — so the AdStellar agent can use them, and control exactly which tools it can run.

Beyond Meta, Slack, and Cometly, AdStellar connects to **thousands of third-party apps** through [Pipedream](https://pipedream.com). Once you connect an app, its tools become available to the AdStellar agent — so it can read your real orders from Shopify, pull deals from HubSpot, write a performance report to Google Sheets, and more.

You can also add your own **custom connector** (a private or self-hosted MCP server) when you need something that isn't in the catalog.

<Note>
  Connections are made once at the **team** level — when a teammate connects an app, it's available to your whole team. You then control **which workspaces** can use it and **which of its tools** the agent is allowed to run.
</Note>

## Connect an app

<Steps>
  <Step title="Open Integrations">
    Click **Integrations** in the left sidebar.
  </Step>

  <Step title="Find the app">
    Browse by category in the sidebar (Ecommerce, Email & SMS, Analytics, CRM, Support, and more) or use the search box. See [Available connectors](/integrations/available-connectors) for the full list.
  </Step>

  <Step title="Click Connect">
    Click the app's card. A secure window opens for you to sign in and authorize access.
  </Step>

  <Step title="Done">
    After you authorize, the card shows a **Connected** badge and the app's tools are immediately available to the agent.
  </Step>
</Steps>

## Manage a connector

Once an app is connected, **click its card** on the Integrations page to open its settings. (Custom connectors: click the connector's row.) From here you can control how the agent uses it.

### Turn the connector on or off

Use the **toggle** in the top-right of the connector page to switch the whole connector on or off. Turning it off withholds all of the app's tools from the agent **without disconnecting** the account — handy when you want to pause an integration temporarily.

### Choose which tools the agent can use

Under **Tool permissions** you'll see every tool the connected app exposes. Each tool has a short description and a badge:

* **Read** — the tool only looks things up (for example, listing orders or fetching a record). Safe, no changes are made.
* **Write** — the tool can make changes (for example, creating or updating a record, or sending a message).

Toggle any tool **on** (allowed) or **off** (not allowed). A common setup is to leave all the **Read** tools on and turn off the **Write** tools you don't want the agent to perform.

<Tip>
  Use **Set all to…** in the top-right of the list to allow or turn off every tool at once, then fine-tune individual ones. Use the search box to quickly find a tool by name. Changes save automatically.
</Tip>

When a tool is turned off, the agent simply won't have it available — it can't be called, even if you ask for it directly.

### Limit access to specific workspaces

Under **Workspace access**, choose where the agent can use this connector:

* **All workspaces** (default) — every workspace on your team can use it.
* **Specific workspaces** — pick exactly which workspaces get access. This is great for agencies and multi-brand teams, so one client's workspace can't reach another client's connected apps.

<Note>
  Workspace access only appears when your team has more than one [workspace](/workspaces/overview).
</Note>

### Refresh, reconnect, or disconnect

Open the **…** menu in the top-right of the connector page for:

* **Refresh tools** — re-check the app for its latest available tools.
* **Reconnect** — re-run the sign-in flow if the connection has expired or stopped working.
* **Disconnect** (or **Remove connector** for custom servers) — remove the app from your team. Its tools, permissions, and workspace settings are cleared.

## What the agent can do with a connected app

Just ask in plain language — for example, *"What was my real Shopify revenue last week vs. what Meta reported?"* — and the agent picks the right tool automatically. When it's using a connector, you'll see a chip in the chat like **"Querying HubSpot…"** with the app's icon.

<Note>
  The agent always prefers its built-in AdStellar tools for ad creation, performance, and Meta campaign management. Connected apps fill in the data and actions those built-ins don't cover. Before running any **Write** tool (creating, updating, deleting, or sending), the agent tells you what it's about to do.
</Note>

## Add a custom connector

If you run your own [MCP server](https://modelcontextprotocol.io), you can register it so the agent can use its tools.

<Steps>
  <Step title="Open Integrations">
    Click **Integrations** in the left sidebar.
  </Step>

  <Step title="Click Add Custom MCP">
    Use the **Add Custom MCP** button in the top-right.
  </Step>

  <Step title="Enter the details">
    Provide a **name**, the server's **URL** (a Streamable HTTP MCP endpoint — `https` recommended), and an optional **auth header** if your server requires one.
  </Step>

  <Step title="Add connector">
    Click **Add connector**. It appears in your connectors list, and you can open it to manage its tools and workspace access just like any other connector.
  </Step>
</Steps>

<Warning>
  Auth secrets for custom connectors are **encrypted at rest** and never shown again after you save them. Only add servers you trust — the agent can call the tools the server exposes (subject to the permissions you set).
</Warning>

## Browse available connectors

For a categorized list of popular apps you can connect — and how each connector's tools work — see [Available connectors](/integrations/available-connectors). The in-app **Integrations** page always shows the complete, searchable, up-to-date catalog.

## Troubleshooting

* **I don't see the Integrations options.** External integrations are rolled out gradually. If the connector catalog or **Add Custom MCP** button aren't visible, your team may not be enabled yet — contact support.
* **An app shows as connected but the agent can't use it.** Open the connector page and check that the connector toggle is **on**, the tools you need are **allowed**, and (if you have multiple workspaces) the current workspace has **access**. If the connection looks unhealthy, use **Reconnect**.
* **The agent isn't using a tool I expect.** Confirm that tool is toggled **on** under Tool permissions, then try **Refresh tools**.
* **A custom server's tools aren't showing up.** Confirm the URL is a reachable Streamable HTTP MCP endpoint and that any required auth header is set correctly, then use **Refresh tools**.