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](https://server-track-lab.pages.dev), 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. |
## 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:
```json
{
"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
TDQS
Scored across 3 tools
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.
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.
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.
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.