MCP Tracking

Track which tools AI clients call on your MCP server, how often, which clients (Claude, Cursor, Windsurf) drive the most usage, and error rates.

import { BetterMeter } from "@bettermeter/node";
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";

const bm = new BetterMeter({
  siteId: "my-mcp-server",
  apiKey: "bm_...",
});

const server = new McpServer({
  name: "my-server",
  version: "1.0.0",
});

// Wraps server.tool() — auto-tracks every invocation
bm.wrapMcpServer(server);

// Tools registered after wrapping are automatically tracked
server.tool("search_docs", { query: z.string() }, async (args) => {
  // ... your tool logic (unchanged)
});

bm.trackTool({
  tool: "search_docs",
  client: "claude-code",
  protocolVersion: "2024-11-05",
  durationMs: 250,
  success: true,
  inputTokens: 150,
  outputTokens: 800,
});

What gets tracked

Tool names, client names, duration, success/failure, and optional token counts. Tool input parameters and output content are never sent.

MCP Tools Reference

BetterMeter runs as an MCP server for AI assistants. Every CLI command has a matching MCP tool with the bettermeter_ prefix.

{
  "mcpServers": {
    "bettermeter": {
      "command": "npx",
      "args": ["bettermeter"]
    }
  }
}

Mutating MCP tools require an exact confirmation phrase (CONFIRM <action> <target>) for the specific action and target before they create, update, delete, scan, or send paid requests.

All analytics tools accept site_id (string) and range (today|7d|30d|90d|12m) — except bettermeter_all_sites, which is account-wide: it declares no site_id, and its range also takes a custom YYYY-MM-DD..YYYY-MM-DD window. limit (number, 1-100, optional) is declared only by the list tools that return ranked rows; the summary, trend, and detail tools do not accept it. The bettermeter_export MCP tool supports json and md formats (the CLI export command also supports csv). Usage examples for AI assistants:

Full Tool List

Human-traffic tools exclude known and high-confidence automated traffic by default. Set include_bots=true when you explicitly need the unfiltered totals.

The tools that accept limit are bettermeter_pages, bettermeter_sources, bettermeter_bots, bettermeter_countries, bettermeter_browsers, bettermeter_visitors, bettermeter_sessions, bettermeter_events, bettermeter_campaigns, bettermeter_conversions, bettermeter_keywords, bettermeter_campaign_visitors, bettermeter_export, bettermeter_cli_commands, bettermeter_mcp_tools, bettermeter_mcp_clients, and bettermeter_api_endpoints. Omitting it returns the endpoint's own default page, which differs per dataset; send it only to ask for a specific number of rows. On bettermeter_sources (with filter) and bettermeter_bots (with category) the limit is applied before the filter, so a filtered result can hold fewer rows than the limit.

Meta spend is commercially sensitive and requires EDITOR or ADMIN access in both direct tools and Pulse; VIEWER Pulse catalogs omit only the spend tool. bettermeter_ad_spend_sync calls Meta and updates stored spend, so it also requires the exact phrase CONFIRM sync ad spend <site_id>.