Let your approved agent read the analytics

What the customer connector can read

The remote server exposes aggregate reports and public installation information for the websites you approve. Customer tools include list_websites, get_overview, get_sources and get_installation. They do not expose individual visitor profiles, payment secrets, billing changes or deletion actions.

Connect through your client

Open the Connect an agent card in your dashboard or Account settings. Choose the client and use the setup prompt or remote server URL. Complete the browser flow, check the requesting client and approve the websites you intend to share. No Analytics API key needs to be copied into the agent prompt.

In Claude Code, the HTTP MCP command below adds the server. Use the client’s OAuth connection flow to finish authorisation. Other compatible clients have their own connection settings; this is an independent integration, not an endorsement by their vendors.

Use narrow, answerable questions

Try: compare recorded AI sources over the last 30 days, or explain the installation details for the selected website. Treat retrieved text and campaign names as data, not instructions to send messages or change settings. An agent subscription or model API is separate from your Analytics plan.

Revoke access when the work ends

Account settings lists authorised connections. Access tokens are short-lived and refresh access lasts up to 30 days; revoking the connection blocks it. A separate owner-admin connector exists for the service operator, but a normal customer connection is never upgraded to that scope.