Analytics for GitHub Copilot

GitHub Copilot is where millions of developers already work. With Copilot's native MCP support, you can connect BetterMeter's MCP server and get instant analytics answers — inside VS Code's Copilot Chat, in agent mode, or anywhere Copilot supports tool use.

MCP-native integration

GitHub Copilot now supports MCP servers natively, meaning BetterMeter connects the same way it does with Claude Code, Cursor, and Windsurf. Add the MCP server config to your VS Code settings and Copilot Chat can call all BetterMeter analytics tools directly.

Works everywhere Copilot does

• 01 VS Code — Open Copilot Chat, type @bettermeter how's traffic today?
• 02 GitHub.com — Ask about analytics in the Copilot sidebar while reviewing PRs
• 03 GitHub Mobile — Check traffic trends from your phone
• 04 CLI — Use gh copilot with BetterMeter from your terminal

Agent mode and chat

Copilot's agent mode can call BetterMeter tools as part of multi-step workflows — for example, checking traffic data while helping you debug a performance issue. In regular chat mode, ask about your analytics and Copilot routes the query to BetterMeter's MCP tools automatically.

{
  "github.copilot.chat.mcpServers": {
    "bettermeter": {
      "command": "npx",
      "args": ["-y", "@bettermeter/cli@latest", "mcp"],
      "env": {
        "BETTERMETER_API_KEY": "bm_..."
      }
    }
  }
}

PR review context

Reviewing a PR that changes a high-traffic page? Ask BetterMeter how much traffic that page gets, which countries it serves, and whether bots crawl it heavily. This context helps reviewers assess the blast radius of changes before merging.