Skip to main content
Glama

Tracking Plan MCP Server

Beginner-friendly Model Context Protocol (MCP) server built with TypeScript + Node.js to create, list, inspect, and validate tracking plans for Ecommerce and Lead-Generation / Service Businesses.

Build Status Vitest TypeScript MCP SDK License


šŸ“Œ Project Overview

The Tracking Plan MCP Server allows AI assistants (such as Cursor, Claude Desktop, and Antigravity) to manage analytics tracking specifications locally.

It supports two distinct business models out-of-the-box:

  1. Ecommerce Businesses: Product views, cart activity, checkout steps, payment info, revenue, and purchase transactions.

  2. Lead Generation & Service Businesses: Service views, form starts, form submissions, lead generation, phone clicks, email clicks, WhatsApp clicks, appointment bookings, and quote requests.


Related MCP server: Orchestration MCP

šŸ›ļø Architecture & Data Flow

AI Assistant (Cursor / Claude Desktop / Antigravity)
      ↓
MCP Client
      ↓
MCP Server (stdio transport)
      ↓
MCP Tools (create_tracking_plan, get_tracking_plan, list_tracking_plans, validate_tracking_event)
      ↓
Tracking Plan Service (Business logic & Validation)
      ↓
JSON Storage (fs/promises)
      ↓
data/tracking-plans.json

šŸ’¼ Supported Business Types

šŸ›’ 1. Ecommerce

Tracks:

  • Product page views (view_item)

  • Cart interactions (add_to_cart, remove_from_cart, view_cart)

  • Checkout flow (begin_checkout, add_payment_info)

  • Purchases & revenue (purchase)

Purchase Event Required Parameters: transaction_id, value, currency, items.

šŸ“ž 2. Lead Generation / Service Businesses

Tracks:

  • Service page views (view_service)

  • Form interactions (form_start, form_submit)

  • Lead submissions (generate_lead)

  • Direct contacts (contact, phone_click, email_click, whatsapp_click)

  • Appointment bookings (appointment_start, appointment_booked)

  • Quote requests (quote_request)

Lead Submission Required Parameters: form_id, form_name.


šŸ› ļø MCP Tools Reference

Tool Name

Parameters

Description

create_tracking_plan

id, name, description, business_type, platform, events

Creates a new tracking plan after validating business_type and checking duplicate IDs.

get_tracking_plan

plan_id

Retrieves complete tracking plan definition.

list_tracking_plans

business_type (optional)

Lists all tracking plans, optionally filtered by ecommerce or lead_generation.

validate_tracking_event

plan_id, event

Validates a tracking payload against plan schemas, returning errors and warnings.


šŸ“‚ Project Structure

tracking-plan-mcp/
ā”œā”€ā”€ data/
│   └── tracking-plans.json            # JSON persistence storage
ā”œā”€ā”€ dist/                              # Compiled JavaScript output
ā”œā”€ā”€ src/
│   ā”œā”€ā”€ index.ts                       # MCP Server entry point & tool registration
│   ā”œā”€ā”€ models/
│   │   └── tracking.ts                # TypeScript types, Zod schemas, & ErrorCodes
│   ā”œā”€ā”€ services/
│   │   └── trackingPlanService.ts     # Business logic & event validator
│   ā”œā”€ā”€ storage/
│   │   └── jsonStorage.ts             # Safe JSON storage reader/writer
│   └── tools/
│       ā”œā”€ā”€ createTrackingPlan.ts      # create_tracking_plan tool handler
│       ā”œā”€ā”€ getTrackingPlan.ts         # get_tracking_plan tool handler
│       ā”œā”€ā”€ listTrackingPlans.ts       # list_tracking_plans tool handler
│       └── validateTrackingEvent.ts   # validate_tracking_event tool handler
ā”œā”€ā”€ tests/
│   ā”œā”€ā”€ createTrackingPlan.test.ts
│   ā”œā”€ā”€ getTrackingPlan.test.ts
│   ā”œā”€ā”€ listTrackingPlans.test.ts
│   └── validateTrackingEvent.test.ts
ā”œā”€ā”€ .gitignore
ā”œā”€ā”€ package.json
ā”œā”€ā”€ tsconfig.json
ā”œā”€ā”€ vitest.config.ts
└── README.md

šŸš€ Quick Start & Development

1. Installation

npm install

2. Run Vitest Unit Tests

npm test

3. Build Project

npm run build

4. Start Server

npm start

āš™ļø MCP Client Configuration

Cursor IDE Configuration

Add to .cursor/mcp.json or Cursor MCP settings:

{
  "mcpServers": {
    "tracking-plan-mcp": {
      "command": "node",
      "args": ["C:/Users/FLS/.gemini/antigravity/scratch/tracking-plan-mcp/dist/index.js"]
    }
  }
}

Antigravity Configuration

Add to .gemini/antigravity/mcp_config.json:

{
  "mcpServers": {
    "tracking-plan-mcp": {
      "command": "node",
      "args": ["C:/Users/FLS/.gemini/antigravity/scratch/tracking-plan-mcp/dist/index.js"]
    }
  }
}

šŸ’¬ Example AI Prompts

  • "Create an ecommerce GA4 tracking plan."

  • "Create a lead generation tracking plan for an HVAC business."

  • "Show me all ecommerce tracking plans."

  • "Show me all lead generation tracking plans."

  • "Validate this purchase event against the ecommerce tracking plan: { name: 'purchase', value: 99.99, currency: 'USD' }"

  • "Validate this lead form submission against the lead generation tracking plan: { name: 'generate_lead', form_id: 'f1', form_name: 'Contact Form' }"


šŸ“„ License

Licensed under the MIT License.

Available Tools

4 tools
create_tracking_planC

Creates a new tracking plan specification for an ecommerce or lead-generation business.

Inputs: id (required), name (required), events (required), platform (required), +2 more.

get_tracking_planB

Retrieves a complete tracking plan definition by plan_id.

Inputs: plan_id (required).

list_tracking_plansB

Lists all available tracking plans with optional filtering by business_type ('ecommerce' or 'lead_generation').

Inputs: business_type.

validate_tracking_eventC

Validates an analytics tracking event payload against a target tracking plan schema.

Inputs: event (required), plan_id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct purpose: retrieve a single plan, list plans, create a plan, and validate an event. No overlapping functionality, and the boundaries are clear from names and descriptions.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern (get_, list_, create_, validate_). No deviations or mixed conventions.

    Tool Count5/5

    Four tools is a lean and well-scoped set for tracking plan operations. Each tool serves a clear role without redundancy.

    Completeness3/5

    Core operations (create, read/list, validate event) are present, but missing update and delete operations leaves a notable gap in lifecycle management. Agents cannot modify or remove tracking plans.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A TypeScript MCP server for managing persistent knowledge graphs with entities, directional relations, and time-based observations. It enables users to create, search, and track structured information with built-in concurrency control and JSON file storage.
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      A TypeScript MCP server for launching, tracking, and managing external coding-agent runs across local and remote backends like Codex and Claude Code. It allows top-level agents to orchestrate subagents through tools for spawning tasks, polling events, and handling interactive sessions.
      7
      2
      -