Setup guide

Connected in a few minutes.

One URL, one Google sign-in, done. Pick your assistant below. Your 14-day free trial starts automatically the moment you ask your first question, no card required.

Plan requirements. Works on every Claude plan, including Free (Free allows one custom connector). On Team and Enterprise an owner enables Upbuild for the organization first; each person then connects with their own Google account.
1

Add Upbuild from the Claude directory

Upbuild is in the official Claude connector directory: one click, nothing to paste.

Open Upbuild in the Claude directory

2

Sign in with Google

Click Connect and authorize with the Google account that has access to your marketing platforms. You will only ever see accounts this login already has access to.

3

Optional: link Meta, TikTok, Snapchat and Adobe

Right after Google, the connect hub offers Meta Ads, TikTok Ads and Snapchat Ads with one click each. Adobe Analytics and Adobe Launch use a one-time guided credential setup (about 10 minutes) in your own Adobe Developer Console; the hub walks you through it and validates your credentials instantly. Link now or add any of them later.

4

Ask

Start a new chat, make sure Upbuild is enabled in the tools menu, and try:

Summarize last month across Google Ads and Meta: spend, conversions, ROAS, top 5 campaigns.

Multiple Google accounts? Agencies juggling client logins can connect up to three identities. Add /mcp2 and /mcp3 as separate connectors (same URL, different path) and each one holds its own Google and Meta sign-in. How to add a second login →

Multiple identities

One connector, up to three logins.

Agencies and freelancers often need Upbuild signed in with more than one Google account: one per client, or work and personal kept apart. Upbuild exposes three connector paths, /mcp, /mcp2 and /mcp3, and each holds its own Google and platform sign-ins, fully separate.

Claude: add /mcp2 as a custom connector
1

Open connector settings

In claude.ai go to SettingsConnectors and click Add custom connector. Custom connectors are available on paid Claude plans; on Team or Enterprise an admin may need to enable them first.

2

Paste the Upbuild endpoint

Name it after the client and paste the connector URL:

https://connector.upbuild.app/mcp2
3

Sign in with Google

Click Connect and authorize with the Google account that has access to your marketing platforms. You will only ever see accounts this login already has access to.

4

Optional: link Meta, TikTok, Snapchat and Adobe

Right after Google, the connect hub offers Meta Ads, TikTok Ads and Snapchat Ads with one click each. Adobe Analytics and Adobe Launch use a one-time guided credential setup (about 10 minutes) in your own Adobe Developer Console; the hub walks you through it and validates your credentials instantly. Link now or add any of them later.

5

Ask

Start a new chat, make sure the new connector is enabled in the tools menu, and try: “Summarize last month across Google Ads and Meta: spend, conversions, ROAS, top 5 campaigns.”

ChatGPT: add /mcp2 as a second plugin
1

Open Plugins and add one

With Developer mode already on, go to SettingsPlugins, click the + button next to the plugin search box and the New Plugin dialog opens.

2

Fill in the plugin

Name it after the client, leave Connection set to Server URL, and paste:

https://connector.upbuild.app/mcp2

Set Authentication to OAuth, tick I understand and want to continue on the custom-server notice, then click Create.

3

Sign in with Google

Click Connect and authorize with the Google account for this client. The new plugin keeps its own sign-ins, fully separate from the first.

Copilot Studio: add /mcp2 as a second MCP tool
1

Open the MCP wizard

Inside your agent go to ToolsAdd a toolModel Context ProtocolNew tool.

2

Add the second Upbuild server

Give it a name that does not exist yet in the environment (for example the client’s name), a real description, and paste the server URL:

https://connector.upbuild.app/mcp2

Set Authentication to OAuth 2.0 and Type to Dynamic discovery, then select Create.

3

Create its own connection

In the agent’s Tools panel, open the Connection dropdown next to the new tool, select Create new connection and sign in with the Google account for this client. The status should read Connected.

Gemini Enterprise: add /mcp2 as a second MCP server
1

Add a second server

In Gemini Enterprise, open the settings gear, choose your team name, then Manage team. Open Connected apps, select Add MCP Server and fill in the first screen:

Add MCP Server
Server URLhttps://connector.upbuild.app/mcp2
NameUpbuild Client B
DescriptionSame description as the first install.
Next
2

Same OAuth details

The Auth screen takes exactly the same values as the first install: both URLs, the shared Client ID and Secret, and mcp in Scopes. The credentials are valid for every connector path, nothing new to register.

3

Enable the actions for the new data store

Repeat the Google Cloud step for the new server: open console.cloud.google.com/gemini-enterprise, pick your tenant project, go to Data stores, open Upbuild Client B, then Actions: Reload custom actions, select all 55, Enable actions.

4

Connect with the second Google account

Back in Gemini Enterprise, open the settings gear, choose Connectors, find the new server and select Connect. Sign in with the Google account for this client; the two identities stay fully separate.

Use /mcp3 the same way for a third login. Each login is its own Upbuild account with its own seats and billing; sign-ins stay completely separate, and disconnecting one never touches the others.

Troubleshooting

If something looks off.

Adobe is asking me for a Client ID and Secret

That is Adobe’s model, not a bug: Adobe issues API access at the organization level, so you create a one-time OAuth Server-to-Server credential in your own Adobe Developer Console (about 10 minutes, needs a System Admin or Developer role) and paste the Client ID and Secret into the hub. Upbuild validates it live against Adobe before saving, stores it encrypted, and deletes it when you disconnect.

TikTok asked me to authorize again

That is TikTok’s design: its authorizations expire every 30 days. The connector detects it and walks you through a quick re-authorization; everything else stays connected.

The assistant says the connection expired or was revoked

Nothing to fix manually. Upbuild is self-healing: the next tool call re-prompts you to sign in, and scope changes are picked up automatically.

I want to check which account is connected

Ask the assistant to run whoami. It returns the Google identity behind the connection plus your subscription and trial status.

I do not see the accounts I expected

Upbuild only surfaces accounts your Google or Meta login already has access to. If an account is missing, get access granted on the platform itself (for example in Google Ads or Business Manager), then ask again.

How do I subscribe, change plan or cancel?

Ask the assistant for billing: the manage_billing tool returns a secure Stripe link where you can subscribe, switch plans, update payment details or cancel. No emails needed.

How do I disconnect completely?

Remove the connector in your assistant's settings, and revoke Upbuild's access from your Google Account connections and, if linked, your Meta Business integrations. Stored tokens become invalid immediately.

Copilot Studio just spins and never loads

The environment has no Dataverse database, which is normal for a tenant’s Default environment. Create or switch to an environment that has one and open Copilot Studio with that environment ID in the URL. Newer builds say “You need Dataverse in this environment” instead of spinning.

Copilot Studio: I do not see the Dynamic discovery option

You are in the older connector editor rather than the MCP wizard. Go back and start from Agents → your agent → ToolsAdd a toolModel Context ProtocolNew tool. If the wizard still does not appear, it is gated per tenant and has not reached yours yet.

Copilot Studio: I clicked Create and nothing happened

Usually a duplicate name. Copilot Studio rejects a connector whose display name already exists in the environment but does not always surface the error. Check Custom connectors in Power Apps for the same environment: it may already be there. Otherwise create it again with a different name.

Copilot Studio: nothing asked me to sign in

Creating the tool never prompts. Open the agent’s Tools panel, use the Connection dropdown and select Create new connection.

Copilot Studio: a tool I deleted still shows in the list

Deleting the custom connector in Power Apps can leave a stale row behind in Copilot Studio. It is harmless. Create the new tool with a different name and ignore the old row.

Copilot Studio: the Publish button is greyed out

Your account does not have a Microsoft Copilot Studio licence. Building and testing do not need one, only publishing to Teams and Microsoft 365 Copilot.

Gemini says it cannot find the Upbuild tools, or only sees one of them

The actions are not enabled. Go to the Google Cloud console, open your Upbuild data store, and check that the Actions tab shows all 55 rows as Enabled. Gemini sometimes claims a connector does not exist at all when its actions are off; enabling them fixes it.

Gemini: only 50 of the 55 tools are enabled

The Actions list paginates at 50 and the select-all checkbox only covers the visible page. Set rows per page to 200 and enable the rest.

Ready

That is the whole setup.

Ten platforms, 55 read-only tools, and a 14-day trial that starts when you do. If you get stuck, we will personally walk you through it.