Generic MCP Quickstart

This quickstart is for browser clients that support remote Streamable HTTP MCP servers and OAuth. It does not use a CLI, desktop configuration, or a local stdio server.

For product-specific instructions, see the ChatGPT Quickstart or Claude Quickstart.

Connect GoodMetrics

1. Open your client’s settings for apps, connectors, integrations, or MCP servers.

2. Add a new remote MCP server named GoodMetrics.

3. Enter the following value in the field labeled Server URL, MCP server URL, Remote server URL, or URL:

   https://data.goodmetrics.io/mcp

4. If the client asks for a transport, select HTTP or Streamable HTTP.

5. Select OAuth authentication if the client asks for an authentication method.

6. Leave API key, authorization URL, OAuth client ID, and OAuth client secret fields empty.

7. Choose Connect or Authorize.

8. Sign in to GoodMetrics, review the read-only analytics:read permission, and choose Allow Access.

9. Return to your MCP client and enable GoodMetrics for the conversation.

Your client handles OAuth discovery, authorization, and token refresh automatically.

Test the connection

List the GoodMetrics sites I can access.

After your client returns your sites, try:

Show the current active visitors for example.com.

Replace example.com with one of your connected domains. The server can match sites by name, domain, alias, or gmID.

See Example Prompts for more ideas.

Advanced client details

GoodMetrics publishes OAuth metadata at:

https://data.goodmetrics.io/.well-known/oauth-protected-resource/mcp

The advertised authorization server metadata is available at:

https://api.goodmetrics.io/.well-known/oauth-authorization-server

Clients request the analytics:read scope for the https://data.goodmetrics.io/mcp resource. The service supports dynamic client registration and the Authorization Code flow with PKCE S256.

The MCP transport uses request/response JSON-RPC over POST. It returns 202 Accepted for accepted notifications and 405 Method Not Allowed for GET; SSE and session streaming are not supported.

If a client reports that the server does not implement OAuth, confirm that both metadata URLs above return JSON. The MCP endpoint URL does not change.