# Snowplow quickstart with your coding agent
> Sign up for a hosted Snowplow environment, connect your coding agent with the Snowplow MCP server and skills, and run a starter prompt that designs your tracking, creates the schemas, adds the tracker, and checks the events.
> Source: https://docs.snowplow.io/docs/get-started/quickstart/
> Documentation index: https://docs.snowplow.io/llms.txt

Add Snowplow tracking to your application with one prompt. Your coding agent asks what you want to measure, then designs the tracking plan, creates the schemas in your Snowplow account, adds the tracker, and checks that the events arrive and pass validation.

You'll need a coding agent that supports MCP, such as Claude Code, Cursor, or Codex. If you don't have an application to track, the agent can create one.

## Sign up

Start a [free trial](https://snowplow.io/get-started/snowplow-free-trial) of Snowplow CDI Cloud, or create an account on the [Signals free tier](https://signals.snowplow.io/start?utm_source=docs.snowplow.io\&utm_medium=referral) for a hosted environment with no end date. Neither needs a credit card.

Your environment is provisioned automatically. You'll usually receive access instructions within moments of verifying your email address, and there's no infrastructure to set up. See the [free trial](/docs/get-started/free-trial/) page for the limits that apply.

Already on Snowplow CDI? Log in to [Console](https://console.snowplowanalytics.com) and skip to the next step.

## Install the Snowplow plugin

The plugin adds the [Snowplow MCP server](/docs/ai/snowplow-mcp/) and [skills](/docs/ai/skills/) to your agent.

```bash
npx plugins add snowplow/skills
```

The first time the agent uses a Snowplow tool, a browser window opens for you to log in to Console. The agent then works with the permissions of your Console account.

Prefer not to install anything? The [Snowplow Assistant](/docs/ai/console-agent/) in Console has the same tools, and can design the tracking plan, create the schemas, and generate the tracker code for you to add to your application.

## Run the starter prompt

Open your project in the agent and paste this prompt:

```text
Help me add Snowplow tracking to this project, using my connected Snowplow account.

Look at the project first, including any analytics or tracking that's already in
place. Ask me what I want to measure, with a few examples that fit this app. Then
propose a tracking plan: the events, the entities, and the schemas, with what
each one is for. Wait for my approval before you create anything in Console.

Once approved, create the schemas and the tracking plan in my account, add the
Snowplow tracker to the app, and send a test event for each event in the plan.
Check for failed events and fix any validation errors. If there's no app here,
create a minimal one. When you're done, list the files you changed, the
schemas you created, and how I can see the events arriving.
```

When the agent asks what you want to measure, describe it in the words of your product. For example, "product views, add to basket, each checkout step, and purchase, with the product and the basket on every event".

The agent loads the relevant Snowplow skill on its own as it plans the [events](/docs/fundamentals/events/), [entities](/docs/fundamentals/entities/), and [schemas](/docs/fundamentals/schemas/), adds and configures the [tracker](/docs/sources/), and reads [failed events](/docs/fundamentals/failed-events/) to propose a fix.

## Check that it works

The agent finishes by listing what it created and changed. To check for yourself, open [Console](https://console.snowplowanalytics.com) to see the schemas and the tracking plan, and open the [Snowplow Micro](/docs/testing/snowplow-micro/) instance included with your environment to inspect each event and its validation result as it arrives. The [Snowplow Inspector](/docs/testing/snowplow-inspector/) browser extension shows the same events as you use your app.

**Troubleshooting**

- If the browser login doesn't open, run `/mcp` in Claude Code, select the Snowplow server, and choose **Authenticate**. For other clients, see [authentication](/docs/ai/snowplow-mcp/#authentication).
- If events show up as failed, ask the agent to read the failed events and fix the schema or the tracking call. The validation error names the property and the rule it broke.
- If no events arrive, check your browser's network tab for tracking requests to the Collector endpoint. If an ad blocker stops them, turn it off for local testing. In production, serve the Collector from your own domain, or proxy the requests through your backend. See [cookies and ad blockers](/docs/get-started/tracking/cookies-and-ad-blockers/).

## Connect a destination

When the events look right in Micro, connect a [warehouse or lake destination](/docs/destinations/warehouses-lakes/) in Console so validated events load into it. The trial allows one warehouse or lake destination and one [event forwarding](/docs/destinations/forwarding-events/) destination. From there you can [query your data](/docs/destinations/warehouses-lakes/querying-data/) and [model it](/docs/get-started/modeling/) with the dbt packages.

## Next steps

These pages explain what the agent built and other ways to work with Snowplow:

- Read about [events](/docs/fundamentals/events/), [entities](/docs/fundamentals/entities/), and [schemas](/docs/fundamentals/schemas/) to understand the tracking plan the agent created
- Follow the [Signals quickstart](/docs/signals/quickstart/) to compute real-time attributes from the events you now collect
- Prefer working step by step? Continue with [tracking](/docs/get-started/tracking/) and the rest of this guide