Choosing Your Interface

GoodMetrics exposes the same read-only analytics data through two interfaces. Start with the workflow you want to support.

Use case	Choose	Why
Build a dashboard, report, backend job, or internal integration.	REST API	You control the code, request URLs, query parameters, pagination, sorting, and response handling.
Ask questions about analytics in natural language.	MCP server	Connect an OAuth-capable MCP client, sign in to GoodMetrics, and let the client use purpose-built analytics tools.

REST API

Use the REST API when you are building software against GoodMetrics analytics data.

REST API requests use:

GET https://data.goodmetrics.io/{gmID}/events/{resource}

Reporting endpoints use query parameters for date ranges, filters, sorting, pagination, and comparison ranges. Realtime endpoints use the current live window automatically.

Start with Getting Started, then use the API Reference for endpoint-specific paths.

MCP server

Use the MCP server when you want an AI client to query GoodMetrics for you.

MCP clients connect to:

https://data.goodmetrics.io/mcp

Your client opens GoodMetrics in a browser so you can sign in and approve permission. You do not need to create or copy an API key.

The server includes quick tools for common questions and advanced tools for discovering endpoints and running custom queries. It is remote, read-only, and does not require installing anything.

Choose a guide from the MCP quickstarts.

Authentication at a glance

Interface	Authentication
REST API	Dashboard-issued API key sent as a bearer token.
MCP server	OAuth sign-in and consent through your GoodMetrics account.