---
title: "Snowplow MCP Server: Claude Setup | SourceMedium"
description: Snowplow's Console MCP server reads failed events and pipeline health and can edit schemas and event specs. Its local CLI MCP server checks schema files.
url: "https://sourcemedium.com/mcp-directory/snowplow/"
type: static
generatedAt: "2026-09-29T01:21:01.000Z"
---

[MCP Directory](https://sourcemedium.com/mcp-directory/) Site analytics and tracking Official SourceMedium integration
# Snowplow MCP server

Checked September 2026.

Snowplow's Console server reads pipelines, failed events, event volumes, and the data catalog, and can create data structures, manage event specifications and tracking plans, and update enrichments. The events themselves, from web, mobile, and server trackers, land in the customer's own warehouse or lake. A second, local server validates schema files through the Snowplow CLI.

## Snowplow MCP options

Every fact in a row comes from the publisher's own documentation.

| Option | Audience | Reads or changes | Sign-in | Setup |
| --- | --- | --- | --- | --- |
| Snowplow MCP server Snowplow | Merchants | Reads pipelines, failed events, data catalog, and event volumes in Snowplow Console; can create data structures, manage event specifications, tracking plans, source applications, and Signals, and update enrichments. Can write | OAuth sign-in | [Setup guide →](https://docs.snowplow.io/docs/llms-support/snowplow-mcp/) |
| Snowplow CLI MCP server Snowplow | Developers | Runs locally through the Snowplow CLI to create and validate data structure and tracking plan files on disk; publishing them to Console is a separate CLI step. Read only No account data | See guide | [Setup guide →](https://docs.snowplow.io/docs/llms-support/cli-mcp-server/) |
| Snowplow data through SourceMedium's MCP `https://mcp.sourcemedium.com/mcp` SourceMedium Ours | Merchants | Reads Snowplow data from modeled SourceMedium tables, next to your other connected sources, with canonical metric definitions. Read only | OAuth sign-in | [Setup guide →](https://sourcemedium.com/docs/ai-analyst/connect-an-ai-assistant) |

## Connect Snowplow to your assistant

Each card lists the servers whose setup guide covers that assistant.

### Connect Snowplow to Claude, Cursor, or Codex

- [Snowplow MCP server →](https://docs.snowplow.io/docs/llms-support/snowplow-mcp/)
Guide also covers Claude Desktop, Claude Code

## Other ways to reach Snowplow data

- [Snowplow Assistant (AI assistant in Console) →](https://docs.snowplow.io/docs/llms-support/console-agent/)
- [Snowplow Console API credentials →](https://docs.snowplow.io/docs/account-management/)
- [Snowplow Ecommerce dbt package →](https://docs.snowplow.io/docs/modeling-your-data/modeling-your-data-with-dbt/dbt-quickstart/ecommerce/)

## One MCP server per tool still can't answer a cross-channel question.

Each server brings its own sign-in, its own definition of revenue, and data your assistant can't join to the rest.

SourceMedium joins Snowplow with the rest of your store, ad, subscription, and returns data, keeps one set of maintained definitions, and gives ChatGPT, Claude, and other assistants a single connection to all of it.
## More in Site analytics and tracking

- [Twilio Segment MCP server →](https://sourcemedium.com/mcp-directory/segment/)
- [Algolia MCP server →](https://sourcemedium.com/mcp-directory/algolia/)
- [Amplitude MCP server →](https://sourcemedium.com/mcp-directory/amplitude/)