io.github.Surface-ops/server-track-lab
Send server-side conversions to Meta CAPI (live); Google validate-only, LinkedIn dry-run.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
server-track-lab-mcpclaude mcp add server-track-lab -e 'SERVER_TRACK_LAB_API_KEY=<your server_track_lab_api_key>' -- npx -y server-track-lab-mcp@0.1.0
{
"mcpServers": {
"server-track-lab": {
"command": "npx",
"args": [
"-y",
"server-track-lab-mcp@0.1.0"
],
"env": {
"SERVER_TRACK_LAB_API_KEY": "<your server_track_lab_api_key>"
}
}
}
}
Variables d'environnement
SERVER_TRACK_LAB_API_KEYobligatoire secret Your server-track-lab API key
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
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. |
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
- Get an API key at https://server-track-lab.pages.dev/signup (a test key
sst_test_…never counts toward usage). - 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 tohttps://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
Questions fréquentes
Qu'est-ce que io.github.Surface-ops/server-track-lab ?
Send server-side conversions to Meta CAPI (live); Google validate-only, LinkedIn dry-run.
Comment installer io.github.Surface-ops/server-track-lab ?
Il s'exécute sur votre machine. Dans Claude Code : claude mcp add server-track-lab -e 'SERVER_TRACK_LAB_API_KEY=<your server_track_lab_api_key>' -- npx -y server-track-lab-mcp@0.1.0. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour io.github.Surface-ops/server-track-lab ?
Oui. Il attend SERVER_TRACK_LAB_API_KEY, à renseigner dans sa configuration.
io.github.Surface-ops/server-track-lab est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient io.github.Surface-ops/server-track-lab ?
Il est publié par Surface-ops. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.