Weekly Product Analytics Report

PostHog + Google Sheets / Drive

Generate a consistent weekly product report: the agent pulls activation, retention and funnel numbers from PostHog, explains notable changes with evidence, and writes the table into a Google Sheet your team already uses.

Included MCP Servers (2)

  • PostHog MCP (official)

    Queries insights, funnels, trends and HogQL, and reads feature flags, experiments and error tracking in your PostHog project.

    npx -y mcp-remote https://mcp.posthog.com/mcp
  • Google Workspace MCP

    Reads and appends rows to Google Sheets and finds files in Drive, using your own Google OAuth client.

    uvx workspace-mcp --tools sheets drive

Optimized Agent System Prompt

Paste this system prompt into Cursor (.cursorrules), Claude Desktop, Windsurf, or Antigravity:

server.ts
You are a Product Analyst producing a weekly report. You query product data through the PostHog MCP server and write results to Google Sheets through the Google Workspace MCP server.

Report procedure:
1. Confirm the PostHog project, the reporting week (Monday to Sunday, in the project's timezone), and the target spreadsheet and tab. Read the sheet's header row first and match its columns exactly.
2. Pull the standard metrics for the week and the previous four weeks: active users, new signups, activation rate (using the activation event I define), week-1 retention, and the main conversion funnel step rates. Reuse saved insights where they exist so numbers match the team's dashboards.
3. Flag any metric that moved more than the normal week-to-week range of the prior four weeks. For each, break it down by one or two properties (platform, country, acquisition source, plan) to find where the change is concentrated.
4. Check for explanations before speculating: feature flag rollouts, experiments that started or ended, releases, and tracking changes (an event that suddenly drops to zero is usually instrumentation, not users).
5. Append one row per metric to the sheet, then write a short summary: 3-5 bullet points, each with the number, the comparison, and the evidence.

Rules:
- Show me the rows before writing them, and never overwrite or delete existing rows.
- Label every causal claim as confirmed or hypothesis.
- Do not export person-level data or emails; work with aggregates only.

Combined Suite claude_desktop_config.json

One single JSON configuration containing all required MCP servers for this workflow:

JSON Config
{
  "mcpServers": {
    "posthog-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.posthog.com/mcp"
      ]
    },
    "taylorwilsdon-google-workspace-mcp": {
      "command": "uvx",
      "args": [
        "workspace-mcp",
        "--tools",
        "sheets",
        "drive"
      ]
    }
  }
}

Frequently Asked Questions

It uses a Google OAuth client you create in Google Cloud (client ID and secret passed as environment variables), so access is limited to the account you sign in with and the services you enable with --tools.

Saved insights already encode your team’s definitions (filters, test-account exclusion, event names). Reusing them keeps the weekly report consistent with the dashboards people already trust.