Upbuild
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 sign-in with Google or Microsoft, and the agent reads live across all your ad and analytics accounts, such as Google Ads, Meta or GA4.
Live data in the chat
Upbuild has an MCP server as part of its toolset, so your agent calls your platforms itself, across every major ad and analytics platform, such as Google Ads, Meta or GA4. Ask across three of them in one sentence and the numbers come back live, dated today, with the tool that fetched them named in the reply.
Every tool that touches an advertising platform is read-only. Nothing your agent can call will change a budget, a tag, an audience or a campaign.
Sign-in is per person. On your own, you see exactly the accounts your logins already reach, and a colleague on the same connector sees theirs. As a member of an organisation on Upbuild, you also inherit every account your company shares with you. No shared service account, no accounts you were never given.
| Platform | Spend | Conv. | CPA | vs last monthvs prev |
|---|---|---|---|---|
| Google Ads | €128,400 | 3,210 | €40.00 | +4% |
| Meta Ads | €86,900 | 2,470 | €35.18 | +27% |
| TikTok Ads | €31,250 | 640 | €48.83 | -11% |
Meta moved most: two campaigns that launched mid-month carry the rise.
Dashboards, from your agent
Describe the dashboard you want in your agent, and it is built from your live accounts and published to your Upbuild account in the same conversation. From then on it refreshes itself, every 30 minutes, every hour or once a day, at its own link that your team and your stakeholders can open, with no Copilot licence and no platform login.
Want another chart, a different market split or a weekly refresh? Say so in your agent and the dashboard updates in place. Every change is saved as a version you can restore.
The link is the deliverable. Share it with named colleagues or your whole organisation, and the numbers people read are today's numbers, not the ones from the day you exported them.
dashboard_createPublished. Monthly Paid Media Review is live on Upbuild and refreshes every hour.
dashboard_updateUpdated. ROAS by market is on the dashboard, now refreshing weekly. Version 2.
Exports and alerts, from your agent
A scheduled export is a job Upbuild runs for you: it collects the data you name from every account you choose, on the schedule you set, and delivers ready-to-use tables to your data warehouse, cloud storage or a spreadsheet. Ask for one in your agent in a sentence, and Upbuild keeps it running whether or not your agent is open. Exports and alerts live in the Upbuild app, so this needs an Upbuild account, not just the connector.
Add a Monday run, pull more history, add a destination or change the time: say so in your agent and the export updates. Every change is saved as a version you can restore.
Tell your agent what to watch, such as any campaign past 80% of its monthly budget, and who to tell. Upbuild checks it every time the data refreshes and sends the warning by email, Slack or Microsoft Teams. It never changes anything in your accounts.
export_createScheduled. Paid media daily runs every morning at 06:00 into your data warehouse, and the history from January 2023 is loading now.
export_updatealert_createDone. The Monday run is added and the budget alert is live, checked on every refresh. Version 2.
Prompts
Written the way a media buyer would ask, not the way an API is queried. Press Copy, paste it into your agent, and swap in your own account names.
Name the platforms, the period and the numbers you care about. Your agent fetches each one and lines them up in one table.
Say what you need to send on: a table, a one-page review, three sentences of commentary. Your agent does the collecting and the writing.
Change the names, keep the shape.
Which Copilot
Microsoft ships several products called Copilot, and they take tools in different ways. Here is which one this page covers.
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 every read-only tool 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.
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 or Microsoft. 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.
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 tool reads. What the agent creates lives on Upbuild: dashboards, exports and alerts in your own account.
The connection belongs to a person, not to the environment. Whoever creates it signs in with their own platform logins, such as Google or Meta, and on their own the agent reaches exactly the accounts those logins already reach; as a member of an organisation on Upbuild, they also inherit every account the company shares with them. 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 sign-ins stop working immediately. Everything goes through one hostname, so a network reviewer has a single address to allow.
Get in touch