Connect VS Code and GitHub Copilot to Measurebase

Measurebase speaks MCP - the open protocol AI assistants use to reach external tools - and so does GitHub Copilot in VS Code. Add Measurebase as a remote MCP server and Copilot Chat answers your tracking questions next to the code you are working on.

What you can ask

• "How much traffic did we process this month, and which domain was busiest?"
• "Are there any open alerts on my accounts?"
• "Is Enhanced Ad Blocker Protection actually working on my site?"
• "Did my test hit from five minutes ago arrive?"
• "How far into my request quota am I this billing cycle?"
• "Compare last week's consent-denied share to the week before."
• "Generate the tracking script for my new domain."

Copilot 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.

Connect in two minutes

1. Open the Command Palette, run MCP: Add Server…, pick HTTP, enter https://mcp.measurebase.com/mcp, name it measurebase, and choose User (every window) or Workspace (.vscode/mcp.json, shared through the repo). You need VS Code 1.101 or newer.
2. This is the entry VS Code writes:

{
  "servers": {
    "measurebase": {
      "type": "http",
      "url": "https://mcp.measurebase.com/mcp"
    }
  }
}

3. Click Start above the server entry (or run MCP: List Servers). VS Code discovers the Measurebase authorization server on its own, opens your browser for the Measurebase login, and shows the consent screen that spells out what it gets.
4. Click Allow. Open Copilot Chat, switch to Agent mode, and the Measurebase tools are listed behind the tools button - ask away.

Prefer a token?

You can skip the OAuth flow with a static header. Create a personal API token in the dashboard under Settings → API tokens (read-only by default, valid until you revoke it) and let VS Code prompt for it instead of storing it in the file:

{
  "inputs": [
    { "id": "measurebase-token", "type": "promptString", "password": true, "description": "Measurebase API token" }
  ],
  "servers": {
    "measurebase": {
      "type": "http",
      "url": "https://mcp.measurebase.com/mcp",
      "headers": { "Authorization": "Bearer ${input:measurebase-token}" }
    }
  }
}

VS Code asks for the token once and keeps it in its secret storage, so a workspace file can be committed without leaking it.

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.