Connect Microsoft Copilot to Measurebase

Measurebase speaks MCP - the open protocol AI assistants use to reach external tools. Microsoft Copilot reaches MCP servers through an agent: you add Measurebase as a tool to an agent of your own, then ask your tracking questions in that agent. With Copilot Studio it takes no code.

What you can do with the MCP

The MCP answers questions about your data and your tracking, sets up Measurebase with you, and improves your tracking settings. Ask the way you would ask a colleague. These are starting points, not commands.

Ask about your Measurebase data

• "How much traffic did we process this month, and which domain was busiest?"
• "How far into my request quota am I this billing cycle?"
• "Did my test hit from five minutes ago arrive?"
• "Show me the last 50 GA4 hits with a 4xx status."
• "Which bots hit my tagging server this week, and how much traffic was that?"

Ask about your tracking setup

• "Is anything wrong with my tracking?"
• "What is failing on my site right now? Show the top errors from the last 24 hours."
• "Why did purchases drop on Tuesday?"
• "Is Enhanced Ad Blocker Protection actually working on my site?"
• "Compare last week's consent-denied share to the week before."

Ask about your Google Tag Manager containers

• "Audit my containers."
• "What did last night's tracking audit find on my shop?"
• "Which Tag Manager containers can I link?"

Ask about your GA4 data

• "What were my top landing pages last month?"
• "How many users came in per channel in September?"
• "Which events count as conversions?"

Ask about your Google Ads and Meta Ads data

• "How are my Google Ads campaigns doing?"
• "Export the cost per campaign for September."
• "How did my Meta campaigns do last month?"

Answers about GA4, Google Ads and Meta need that account linked to your domain in Measurebase.

Set up Measurebase

• "Add shop.example.com and email the install instructions to my developer."
• "Generate the tracking script for my new domain."
• "Verify the DNS record for my new domain."
• "Link my GA4 property."
• "Turn on Cookie Keeper."

Improve your tracking settings

• Google Tag Manager: "Propose fixes for what the audit found and put them in a workspace."
• GA4: "Mark purchase as a key event in GA4."
• Google Ads: "Set up Google Ads for generate_lead."
• Meta: "Send a test event to Meta."

Tag Manager changes land in a workspace named Measurebase, and you preview and publish them yourself. Changes in GA4 and Google Ads go live at once, because those tools have no draft, so they need your confirmation first.

Manage alerts, clients and your team

• "Are there any open alerts on my accounts?"
• "Which of my clients need attention?"
• "Mute the DNS alert on my staging domain until I fix it."
• "Set the no-data alert for my shop to 12 hours."
• "Invite anna@example.com as editor."

Your agent answers with your live data: statistics, request types, browser and bot breakdowns, Consent Mode v2 signals, request logs, alerts, plan usage, and the ad-block detection status - across every account you're a member of.

Before you start

• A work account with access to Copilot Studio, or to the Microsoft 365 Agents Toolkit if you build in Visual Studio Code. Your organization may need to approve the agent or its connection first.
• A Measurebase login. You sign in through your browser and approve the connection yourself.

These routes use Microsoft's agent tools. Microsoft's documentation describes no way to add a server directly to the free Copilot app, or to Microsoft 365 Copilot chat without an agent. Using GitHub Copilot in your editor? Follow the VS Code guide instead.

Connect with Copilot Studio

The route without code, using Microsoft's MCP onboarding wizard.

1. In Copilot Studio, create or open an agent and go to its Tools page.
2. Select Add a tool, then New tool, then Model Context Protocol.
3. Enter a Server name and a Server description, such as "Tracking health, traffic, alerts and audits for my Measurebase domains". As the Server URL, enter https://mcp.measurebase.com/mcp.
4. Under authentication, choose OAuth 2.0 with the type Dynamic discovery. Select Create, then Next.
5. In the Add tool dialog, select Create a new connection. Sign in with your Measurebase login and click Allow on the consent screen that spells out what the agent gets.
6. Select Add to agent, then test the agent with a question.

To use the agent in Microsoft 365 Copilot or Teams, publish it, open Channels, select Teams and Microsoft 365 Copilot and choose Add channel. Sharing it across your organization needs an administrator's approval.

Connect with the Microsoft 365 Agents Toolkit

The route for developers, as a declarative agent in Visual Studio Code. It needs Agents Toolkit 6.12.0 or later.

1. Open the Microsoft 365 Agents Toolkit and select Create a New Agent/App, Declarative Agent, Add an Action and then Start with an MCP Server.
2. Enter the server address https://mcp.measurebase.com/mcp and choose OAuth (with dynamic registration). Press Enter at the scopes step, then choose a project location and an agent name.
3. In the Accounts pane, sign in to Microsoft 365 and check that Custom App Upload Enabled and Copilot Access Enabled are shown. In the Lifecycle pane, select Provision and then Confirm.
4. Open Microsoft 365 Copilot at m365.cloud.microsoft/chat and pick your agent under Agents. Ask a question, choose to sign in when asked, and click Allow on the Measurebase consent screen.

Microsoft updates these screens often. If a label looks different, see Microsoft's guides for Copilot Studio and the Agents Toolkit.

Prefer a token?

If sign-in is not an option in your setup, Copilot Studio can also use a personal API token. Create one in the dashboard under Settings → API tokens (read-only by default, valid until you revoke it). In step 4, choose API key with the type Header and the name Authorization, and enter Bearer YOUR_TOKEN as the value when you create the connection.

A connection with your token acts as you, so keep the token read-only unless you need more, and be careful who you share that agent with.

How access and privacy work

• Personal, not account-wide. A connection authenticates as you and follows your own memberships: it sees the accounts you can see, nothing else. Colleagues connect for themselves.
• Your roles apply, live. Every request re-checks your membership and role on the account it touches. Lose access to an account and the connection loses it that same second.
• Revocable in one click. Every connection shows up under Settings → API tokens - OAuth ones included. Revoke it there and the connection is dead immediately.
• Nothing is stored in between. The connector service keeps no credentials and no data; it forwards your token to the Measurebase API over TLS and returns the answer. Only a hash of any token is ever stored server-side.
• Standards, not improvisation. The flow is OAuth 2.1 with mandatory PKCE and single-use, short-lived authorization codes.