Skip to main content
Glama
server-track-lab MCP server

server-track-lab MCP server

server-track-lab MCP server

Let AI agents send server-side conversion events (leads, signups, purchases, subscriptions) to ad platforms through server-track-lab, using your own server-track-lab API key.

Tools

Tool

What it does

track_event

Send one conversion. server-track-lab normalizes, SHA-256 hashes and dedupes it (by event_id), then forwards it.

test_meta_connection

Send one synthetic Lead to Meta Events Manager → Test events with your saved pixel, token and test code.

get_stats

This month's accepted / deduplicated / failed events, free allowance, and the human vs agent usage split.

Related MCP server: Meta Ads MCP

Honest status (Oct 2026)

  • Meta Conversions API: live, with your own pixel ID and access token.

  • Google: Data Manager API validate-only preview. Google checks the request; nothing is recorded.

  • LinkedIn: dry-run. The payload is built and shown, not sent.

  • Pricing: first 1,000 billed events each month free, then CA$2 per 1,000. Agent traffic is welcome, counted in its own bucket and billed the same as human traffic.

Setup

  1. Get an API key at https://server-track-lab.pages.dev/signup (a test key sst_test_… never counts toward usage).

  2. Add to your MCP client config:

{
  "mcpServers": {
    "server-track-lab": {
      "command": "npx",
      "args": ["-y", "server-track-lab-mcp"],
      "env": { "SERVER_TRACK_LAB_API_KEY": "sst_live_or_test_key" }
    }
  }
}

Optional: SERVER_TRACK_LAB_BASE_URL (defaults to https://server-track-lab.pages.dev).

The server talks only to the server-track-lab API and sends the header X-Client-Type: agent. Docs: https://server-track-lab.pages.dev/docs

MIT licensed · by Canada Site Ops

Available Tools

3 tools
get_statsGet usage statsA

This month's accepted, deduplicated and failed events for the workspace, plan and free allowance, and the usage split between human/app and agent/bot traffic (both billed the same).

Inputs: no named parameters.

test_meta_connectionTest the Meta connectionA

Send one synthetic Lead to Meta Events Manager → Test events using the workspace's saved Meta pixel, token and test_event_code. Returns sent/skipped/failed with Meta's error and a hint. Does not affect production data.

Inputs: no named parameters.

track_eventSend a conversion eventA

Send one server-side conversion (lead, signup, purchase, subscribe...) to server-track-lab, which normalizes, SHA-256 hashes and dedupes it, then forwards it: Meta Conversions API live (with the workspace's own pixel/token), Google Data Manager API validate-only preview (nothing recorded), LinkedIn dry-run (not sent). Reuse the same event_id on retries; duplicates are free and not re-sent. Counts as billed usage (first 1,000/month free, then CA$2 per 1,000).

Inputs: user (required), event_id (required), event_name (required), test, +5 more.

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation4/5

    The three tools mostly target distinct actions: retrieving stats, testing a Meta connection with a synthetic event, and sending a live conversion. test_meta_connection and track_event overlap in that both send event payloads, but the descriptions clearly distinguish test-only behavior from billed production tracking.

    Naming Consistency5/5

    All tool names use consistent snake_case with a clear verb_noun pattern: get_stats, test_meta_connection, track_event. The convention is predictable and readable across the entire set.

    Tool Count3/5

    Three tools is quite thin for a conversion tracking server, though each has a clear role. It sits at the borderline between a focused minimal surface and an underpowered one.

    Completeness3/5

    Core actions are present (track an event, view stats, test Meta setup), but notable gaps remain: no tool to inspect individual event status, manage saved credentials/pixels, or retrieve event history. Agents may hit dead ends when debugging beyond the simple Meta test flow.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables management and analysis of Meta (Facebook/Instagram) ads through natural language conversations, with 30 tools for reading and writing ad data.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to manage Meta Ads (Facebook, Instagram) end-to-end through natural conversation, including launching campaigns, uploading creatives, updating budgets, and analyzing performance.
      42
      Business Source 1.1
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to create, manage, and automate Meta (Facebook/Instagram) ads campaigns via the Marketing API, with safe defaults and AI-generated creative.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables an AI assistant to set up and manage server-side conversion tracking by connecting ad platforms like Google Ads, Meta, and GA4, building and publishing conversion flows that fire when forms are submitted, installing tracking snippets, and reviewing conversion events. It also supports diagnosing missing conversions and excluding internal traffic, all through a hosted connector authorized against the user's own account.
      MIT