server-track-lab MCP server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SERVER_TRACK_LAB_API_KEY | Yes | Your server-track-lab API key. Get one at https://server-track-lab.pages.dev/signup (a test key `sst_test_…` never counts toward usage). | |
| SERVER_TRACK_LAB_BASE_URL | No | Optional base URL for the server-track-lab API | https://server-track-lab.pages.dev |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| track_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). |
| test_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. |
| get_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). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.