An MCP (Model Context Protocol) server for Tealium data layer validation, documentation generation, debugging, and code generation. Built for tag management specialists and analytics engineers.

# Clone or download this repository
cd tealium-mcp-server

# Install dependencies
npm install

# Build
npm run build

# Add the server to Claude Code
claude mcp add --transport stdio tealium -- node /path/to/tealium-mcp-server/dist/index.js

# Verify it's configured
claude mcp list

Edit your Claude Desktop config file:

Linux/WSL: ~/.config/Claude/claude_desktop_config.json macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "tealium": {
      "command": "node",
      "args": ["/path/to/tealium-mcp-server/dist/index.js"]
    }
  }
}

Ask Claude:

"Validate this data layer: { page: { pageName: 'Home' }, user: { isLoggedIn: true } }"

Ask Claude:

"Debug this data layer from my booking page and tell me what's wrong"

Then paste your data layer JSON from the browser console.

Ask Claude:

"Generate documentation for my tracking specification"

Then provide your spec in JSON or paste CSV content.

Ask Claude:

"Generate TypeScript interfaces for my hotel booking data layer"

Ask Claude:

"Parse this tracking spec from my Google Sheet"

Then paste CSV content with columns like: variable, type, required, description

When a developer sends a data layer for review or when checking a live page:

"Validate this data layer against the hotel schema:
{
  page: { pageName: 'Booking Confirmation', pageType: 'confirmation' },
  hotel: { hotelCode: 'BCN001', hotelName: 'Barceló Sants' },
  booking: { bookingId: 'RES123', bookingTotal: 450, bookingCurrency: 'EUR' }
}"

When something isn't tracking correctly (e.g., QA finds missing data in reports):

"Debug this data layer from the booking page - events aren't firing correctly:
[paste JSON from browser console: copy(utag_data)]"

The tool will identify:

• Missing required variables
• Wrong data types (string vs number)
• Invalid dates
• Empty values
• PII exposure risks

When onboarding new developers or updating tracking specs:

"Generate documentation for our hotel booking data layer"

Or from an existing spec:

"Parse this tracking spec and generate documentation:
[paste CSV from Google Sheets]"

When developers need implementation code:

"Generate TypeScript code for our booking funnel data layer with these events:
- search.initiated
- hotel.viewed
- room.selected
- booking.completed"

When the analytics team sends a new tracking requirement (usually a spreadsheet):

"Parse this tracking spec from our Google Sheet:

variable,type,required,description
page.pageName,string,true,Page identifier
booking.bookingTotal,number,true,Total booking amount
booking.bookingCurrency,string,true,ISO currency code
..."

To quickly grab the data layer from any page:

// In browser DevTools console:
copy(JSON.stringify(utag_data, null, 2))

Then paste it into Claude with "Debug this data layer" or "Validate this".

# Use the MCP Inspector to test
npx @modelcontextprotocol/inspector node dist/index.js

This server includes specialized support for hotel/travel tracking:

• Search data: destination, check-in/out dates, guests, rooms
• Hotel data: code, name, brand, star rating, category
• Room data: type, code, capacity, amenities
• Booking data: ID, status, dates, nights, rates, totals
• Guest data: type, loyalty ID, tier, points

Perfect for hotel chains like Barcelo, Marriott, Hilton, etc.

# Build
npm run build

# Run development (build + start)
npm run dev

MIT