Upbuild
Upbuild / MCP connector / Copilot Studio
Copilot Studio MCP server
Copilot Studio is Microsoft's agent builder. Add Upbuild to an agent there as a Model Context Protocol tool, with one server URL and one Google sign-in, and the agent reads Google Ads, Meta, TikTok, GA4, Adobe Analytics and seven more platforms live.
Every platform on one subscription
First, the disambiguation
Microsoft ships several products called Copilot and they take tools in different ways. This page is about the one where you build an agent, give it tools and publish it.
The agent builder at copilotstudio.microsoft.com. You create an agent, add Upbuild under Tools as a Model Context Protocol server, and the agent can call 80 read-only tools across every connected platform. This is the product this page is about.
Not where you install Upbuild, but where most people end up using it. Publish the agent to the Teams and Microsoft 365 Copilot channel and the business asks it in a Teams chat. That publish needs a Copilot Studio licence, which is separate from Upbuild; building and testing in the test pane does not.
A different product with a different tool surface, for code in an editor. Nothing on this page applies to it, and the Upbuild server URL below will not help you there.
Copilot Studio runs inside a Power Platform environment and needs one with a Dataverse database. A tenant's Default environment usually has none, and Copilot Studio will simply spin on it. A free Developer environment includes Dataverse and is the quickest way through.
What the agent reads
Upbuild holds no copy of your data. Each tool call goes to the platform API in the moment and returns what is there now, scoped to the login of the person who created the connection. One live organisation in Upbuild reaches 859 ad and analytics accounts across three connections, and an agent can ask about any of them in a sentence.
Everyone who uses the agent creates their own connection and signs in with their own Google account. Nobody inherits access they did not already have in Google Ads or Business Manager.
All 80 tools fetch. Nothing the agent can call changes a budget, pauses a campaign or writes a row. Writing happens only in the Upbuild app, as a scheduled export you set up yourself.
You are an admin, so you reach every account in the organization: 859 of them, across 3 connections.
| Account | Platform | Data streams | Connection |
|---|---|---|---|
| Northwind Retail | UK742-118-6093 | Google Ads | 6 | Northwind Google |
| Northwind Retail | DEact_884219073 | Meta Ads | 4 | Northwind Meta |
| Harbour Group | Nordics7011893 | TikTok Ads | not used | Harbour TikTok |
| Meridian Markets | Web318442905 | Google Analytics | 3 | Northwind Google |
Setup
About fifteen minutes end to end, most of it waiting for Microsoft to provision an environment. Two things decide whether it works: the environment has a Dataverse database, and you start the wizard from inside an agent rather than from the top-level Tools page.
Working in an environment that has Dataverse, open Agents, then your agent, then Tools, Add a tool, Model Context Protocol, New tool. The top-level Tools page opens the older connector editor, which has no Dynamic discovery option and will not authenticate. If the wizard is missing entirely, it is gated per tenant and has not reached yours yet.
Name it Upbuild, write a real description (Copilot Studio reads that description to decide when to reach for these tools) and paste the server URL https://connector.upbuild.app/mcp. Set Authentication to OAuth 2.0 and Type to Dynamic discovery, then select Create. If Create appears to do nothing, the name already exists in that environment: use another one.
Creating the tool never prompts for a sign-in, because Copilot Studio keeps the connector and the connection apart. In the agent's Tools panel, open the Connection dropdown next to Upbuild, choose Create new connection and authorise with Google. Wait for the status to read Connected, then ask the agent your first question.
Publishing to Teams and Microsoft 365 Copilot is a separate step: Publish, then Channels, then Teams and Microsoft 365 Copilot, then Add channel, then install it for yourself or send it for admin approval. Agencies that keep client logins apart can add a second and a third server, /mcp2 and /mcp3, each holding its own separate sign-ins.
In the agent
An agent published into Teams gets the questions that used to arrive as a request for a report. These four come back with numbers, from an agent whose only tool is Upbuild.
The reason most of these agents get built. Both platforms are read in the same turn and come back as one table with each account named, so nobody reconciles two exports by hand at eight in the evening.
One question over every account that person's login reaches. The agent walks the accounts itself, so there is no per-market request, no chasing a local team and no spreadsheet to consolidate afterwards.
GA4, Google Tag Manager and Adobe Launch sit in the same connector as the ad platforms, so a tracking question and a spend question take exactly the same route and need no second tool.
Organisations on the Upbuild app get its dashboard tools in the same connector, so an agent can create a dashboard that then refreshes itself every 30, 60 or 1440 minutes and lives at its own link, for the people who will never open Copilot Studio.
For the security review
Four questions, answered the way we answer them in a questionnaire. The longer pack, the data processing terms and the subprocessor list are on request.
Nothing is pasted into your tenant. The wizard uses OAuth 2.0 with dynamic discovery, so there is no client id and no secret sitting in the environment to rotate or to leak. Platform tokens are held encrypted on Upbuild's side and are never exposed to the agent, to Power Platform or to a browser.
Nothing on an advertising platform. Every one of the 80 tools reads. The only writes Upbuild ever performs are the scheduled exports you configure in the Upbuild app yourself, into your own BigQuery dataset, storage or spreadsheet.
The connection belongs to a person, not to the environment. Whoever creates it signs in with their own Google, Meta, TikTok or Snapchat login, and the agent reaches exactly the accounts that login already reaches. Access is decided again on every call rather than cached into a role.
Delete the tool in the agent, then revoke Upbuild in Google Account connections and, if it is linked, in your Meta Business integrations. Stored tokens stop working immediately. The transport is Streamable HTTP on one hostname, so a network reviewer has a single endpoint to allow.
Get in touch