Skip to main content

For AI agents: a Markdown version of this page is at https://docs.snowplow.io/docs/ai.md. The index of all documentation pages is at https://docs.snowplow.io/llms.txt, and the index for this section is at https://docs.snowplow.io/docs/platform/llms.txt.

Snowplow + AI

Snowplow supports agentic and LLM-powered workflows in several ways. New to Snowplow? Snowplow quickstart with your coding agent goes from a hosted environment to validated events with the assistant doing the setup.

To connect your own coding agent, such as Claude Code, Cursor, or Codex, to your Snowplow account, run npx plugins add snowplow/skills. This installs the Snowplow MCP server and the Snowplow skills. Your agent can then answer questions about your account, design and implement tracking, configure your pipeline, and troubleshoot failed events.

Snowplow Signals

Looking for real-time behavioral context and profile data for your AI use cases? Check out Signals.

Connect your coding agent​

Coding agents only read the Snowplow documentation index, llms.txt, when something tells them to. Install the Snowplow MCP server and skills, then add the snippet to the instructions file your agent reads, so it fetches current versions and terminology before it writes Snowplow code. The docs home shows the same snippet.

  1. Install the Snowplow MCP server and skills:

    bash
    npx plugins add snowplow/skills
  2. Add this to CLAUDE.md in your project root. Claude Code reads it at the start of every session.

    markdownCLAUDE.md
    ## Snowplow

    - Before you write Snowplow tracking, schema, pipeline, or Signals code, fetch https://docs.snowplow.io/llms.txt and follow its "Instructions for AI agents" section.
    - Find pages through the product indexes: https://docs.snowplow.io/docs/cdi/llms.txt (Snowplow CDI), https://docs.snowplow.io/docs/signals/llms.txt (Signals), and https://docs.snowplow.io/docs/api-reference/llms.txt (reference).
    - Read any docs page as Markdown: replace the trailing slash in its URL with .md.
    - Check the package registry for the current version of a tracker or SDK. Don't copy version numbers from examples.
    - Say "self-describing event" and "entity", not "unstructured event" or "context".

See documentation for LLMs for the indexes and Markdown files the snippet points to.

Was this page helpful?