Anacraft — Google Analytics 4

What anacraft — Google Analytics 4 does

anacraft — Google Analytics 4 gives an MCP-compatible assistant access to data from a selected Google Analytics 4 property. It is intended for questions about site performance using the property's own numbers rather than synthetic or preloaded data. The surrounding CLI can also display the same information in a terminal dashboard and generate reports for specific date ranges.

The project covers both reporting and measurement review. Reports include headline site metrics, popular pages, acquisition sources, countries, and current visitors. The audit checks whether the property is receiving data and whether important GA4 configuration is present, including web streams, key events, and purchase values.

How it works

Run craft login to complete Google OAuth, then use craft props to see properties available to the account and craft use <id> to save the default property. Reports query that property unless a command receives another property ID through --property.

The MCP server starts through craft mcp. Claude Desktop can be configured automatically with craft mcp --install; the generated configuration launches the local executable with the mcp argument. The README identifies site_status as the JSON report shape used by the MCP tool. Demo mode starts without a Google account and returns synthetic data.

The audit combines Google Analytics Data API results with Google Analytics Admin API configuration. This allows it to compare observed event activity with settings such as key-event definitions instead of checking only one side of the property.

Setup and configuration

On macOS or Linux, install a release with the project's shell installer, install from source with Cargo, or place a binary from the Releases page on PATH. The installer uses /usr/local/bin when writable and otherwise uses ~/.local/bin; INSTALL_DIR can select another destination.

After authentication and property selection, run craft or craft dash for the terminal dashboard. craft overview, pages, portals, realms, and live provide focused reports. The overview command accepts --days and can emit JSON or Slack Block Kit output, which supports scripts and webhook-based digests.

For a new site, the hosted dashboard or craft configure yoursite.com can create a GA4 property and web data stream, then provide the tag and measurement ID. The README also documents craft serve for running the dashboard locally on 127.0.0.1.

Tools and capabilities

• Ask an assistant for GA4 site-status information through MCP.
• Show headline metrics, period changes, daily user data, and triggered achievements.
• List popular pages, traffic sources, countries, and current visitors.
• Audit the last 28 days by default, or choose a longer period with --days.
• Export overview and audit results as JSON or Slack payloads.
• Apply audit fixes that GA4 can handle with craft audit --fix.
• Run reports with synthetic data using demo mode.

Limitations and notes

The MCP workflow requires craft login, a selected property, and an active subscription. Without those prerequisites, the server still starts but its tools report what is missing; demo mode does not require either account access or a subscription.

The available data depends on what the selected GA4 property has collected. For example, a property can receive an event without having that event marked as a key event, and event names are matched exactly. A purchase without a value can make revenue-related figures zero.

The dashboard and MCP offering are associated with the Anacrafter Elite plan according to the README. The CLI's report formats do not require a subscription. The local serve command binds to 127.0.0.1 and prints a bearer token once when it starts.

anacraft — Google Analytics 4 is therefore best suited to developers who already have, or are preparing, a GA4 property and want assistant-driven reporting alongside command-line inspection and audits.