Media MCP Bridge

Connect several subaccounts

Paste your credentials once, then list the subaccounts. Every row is validated against the live APIs on its own — one bad line fails that row, not the batch.

Shared credentials

Used for every subaccount below. The v3 key must be workspace-wide, so it can reach each subaccount you list.

Assistable v3 API key — starts with ask_live_

GHL Private Integration Token — optional if every row carries its own pit=. A private integration may be agency-wide or scoped to one location depending on how it was minted; if yours only covers one location, leave this blank and put pit=<token> on each row instead.

AI provider

Provider API key

Subaccounts

One per line — subAccountId, locationId, assistantId, label. Commas or tabs, so a spreadsheet paste works. Leave the assistant blank and it is filled in automatically when the subaccount has exactly one. Add pit=<token> anywhere in a row to give that location its own GHL token.
These are two different ids. The subaccount id is Assistable's own and comes from the dashboard URL, /portal/<subAccountId>/...; the location id comes from the CRM. Pasting the same value into both is the usual slip.

Just one subaccount? Use the single form →