server-track-lab MCP server
Related Servers
Alternatives to server-track-lab MCP server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to set up server-side conversion tracking for Meta and TikTok, create and manage triggers, verify tracking, and answer questions about events, attribution, and journeys from chat.2MIT

Converly MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables 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- AlicenseNot gradedqualityAmaintenanceEnables AI agents to create, manage, and automate Meta (Facebook/Instagram) ads campaigns via the Marketing API, with safe defaults and AI-generated creative.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI clients to read Meta Ads performance with breakdowns and diagnostics and to create, update, or pause campaigns, ad sets, ads, creatives, audiences, and catalogs, with every write requiring explicit user approval. Runs as a hosted, OAuth-authenticated remote server with no local install.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables management and analysis of Meta (Facebook/Instagram) ads through natural language conversations, with 30 tools for reading and writing ad data.MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to manage Meta Ads (Facebook, Instagram) end-to-end through natural conversation, including launching campaigns, uploading creatives, updating budgets, and analyzing performance.42Business Source 1.1
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.