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

# Open the Connections page

> Open the buyer's view of provider connections and their advertiser-account mappings

<Warning>
  Early access: `open_connections_page` is exposed only to customers enrolled
  in the `storefront-connections` flag. Until then the tool is not listed on
  the buyer MCP surface (Claude, ChatGPT, or Murph) and cannot be called.
</Warning>

`open_connections_page` launches the **Connections page** — the buyer's view
of the provider connections on the account (ad platforms, creative tools, and
data & measurement integrations), each connection's status, and the mapping of
its discovered accounts to your advertisers. It is a **widget launcher**: the
tool takes no arguments and returns only a UI resource directive; the page then
self-fetches its own data. It is buyer-only; writes remain limited to the page's
host-authorized connection and mapping operations.

## From an agent (MCP)

Ask in natural language — "show my connections", "connect Google Ads", "map
this account to an advertiser" — and the agent calls `open_connections_page`.
It takes no arguments:

```json theme={null}
{
  "name": "open_connections_page",
  "arguments": {}
}
```

The response carries the Connections page resource
(`ui://agentic-api/connections/mcp-app.html`) in `_meta`; a host that renders
MCP-UI widgets opens the page. Hosts that don't render widgets receive a plain
confirmation and no connection data — the tool never returns connection facts
itself.

## What the page reads

Once open, the page loads live data through the buyer API:

* **Connections** — [`list_storefront_connections`](/v2/buyer/storefronts/tasks/list-storefronts)
* **Account → advertiser mappings** — `list_storefront_connection_account_mappings`
* **Advertisers** — the account's advertisers, to map accounts against

Connecting a provider hands off to the provider's OAuth; mapping an account to
an advertiser is a durable write, and the page surfaces the reason inline if a
map or unmap fails so you can retry. See the
[connecting ad platforms guide](/v2/guides/connecting-ad-platforms) for the
end-to-end flow.

## Unlink a provider

**Unlink** is available on the card and detail view for an official adapter
that has a saved connection. Before anything changes, the page asks you to
confirm the organization-wide effect. Confirming archives that connection,
revokes and archives its credential, disables the accounts discovered through
it, and stops future provider syncs and campaign subscriptions through that
grant. Because the grant is shared, this affects every advertiser using the
connection.

Unlinking does not erase historical reporting data or advertiser mapping
intent. A mapped provider account remains usable when another active grant can
reach it; otherwise the mapping is retained but unavailable until the account
is reachable again. Any connected-account campaign subscription is stopped as
part of the archive. Reconnect the provider to create or restore usable access.

Publisher storefronts without an adapter connection record do not show this
action; their approval-gated relationship lifecycle is separate.