That is worth planning for: the JSON has to live somewhere the client process can read, and whatever properties that service account can see are what the assistant can see. Grant it access to the properties you actually want analysed and nothing else — the scope of the credential is the scope of the tool.
A growth and analytics toolset for a team, published as a workspace of MCP packages. The Google Analytics package is the one that ships; more are marked as coming.
- Analytics data pulled directly into the conversation
- Traffic and conversion analysis, rather than a raw metric dump
- Custom reports, defined in the request
- Google Search Console data alongside Analytics
Run as `npx @weppa-cloud/mcp-google-analytics` from the client config — no build step for the published package. One setting: `GOOGLE_ANALYTICS_CREDENTIALS`, an absolute path to your credentials JSON file on disk. To work on it locally instead, clone the repo, `npm install`, `npm run build`, and develop inside `packages/google-analytics`.
One command plus a key — npx @weppa-cloud/mcp-google-analytics, then supply credentials