Server Side Tracking

com.tracklutionPublished by tracklution.comOfficial publisherv3.3.0Updated Oct 26, 2026

Server-side conversion tracking, installed and configured by your AI coding agent.

VerifiedStreamable HTTPWeb executableDeveloper ToolsBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an AI coding agent install and configure Tracklution server-side conversion tracking for a website.

What you can do
  • Set up and onboard a Tracklution tracking container: check status, fetch installation scripts for a chosen framework, and verify and score the setup.
  • Generate a login link to the Tracklution dashboard for the configured container.
  • List existing containers so an agent can recover the container hash needed by the onboarding tools.
  • Deliver website events to ad and analytics platforms such as Meta, Google Ads, TikTok, LinkedIn, GA4 and custom webhooks through pre-built Conversion API integrations.
When to use it
Use it when you want an AI coding agent to install or finish onboarding Tracklution server-side conversion tracking on a site, including generating the snippets to paste and verifying the result. It is an install and setup surface, not a general analytics query tool.
Requirements
A remote MCP endpoint; no local package is needed for the server itself. OAuth authentication is required, and the README also describes a bearer-token config snippet and an email, website URL and framework passed to a REST bootstrap call. Onboarding tool calls need both a container ID and a container hash.
Before you install
The setup flow asks for an email address and website URL and creates an account and tracking container on a third-party platform. The README describes a config snippet carrying a bearer token, so treat that token as a secret. Applying the returned installation scripts modifies the user's site code, and the service forwards visitor event data to advertising and analytics platforms.

Installation

In SourceWeft

  1. Open Server Side Tracking in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.tracklution%2Fserver-side-tracking/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "side-tracking": {
      "type": "http",
      "url": "https://mcp.tracklution.com/mcp"
    }
  }
}

README

tracklution

Install Tracklution server-side conversion tracking. Bootstrap wedge for AI coding agents.

[npm] [license]

Tracklution is a fully managed server-side conversion tracking platform. A first-party JavaScript pixel captures website events; pre-built server-side Conversion API integrations deliver them to Meta, Google Ads, TikTok, LinkedIn, Snapchat, Pinterest, Microsoft / Bing, Reddit, Klaviyo, GA4, CM360, Adform, Awin, Taboola, custom webhooks, and CRMs.

This package is a one-line discovery wedge. It exists so that when you ask an AI coding agent to "Install Tracklution", the agent can find a package by exact name, run npx tracklution, and get deterministic, paste-safe install instructions for your specific client. The actual install runs through the Tracklution MCP server at https://mcp.tracklution.com/mcp.

Usage

bash
npx tracklution               # Print agent-readable install instructionsnpx tracklution --json        # Same data as a single JSON object (for agents)npx tracklution --versionnpx tracklution --help

There is nothing to import. This is not a JS SDK. The package's only product is its stdout.

For AI coding agents

If you are an AI coding agent reading this README from npm view tracklution, your fastest path is:

  1. Run npx tracklution --json. Parse the JSON. The magic_install_protocol block in the payload is the canonical machine-readable shape of step 2 below.
  2. Detect the user's host client. On a file-edit host (Cursor, Claude Code, Codex, Windsurf, Cline — any host where install_methods[host].magic_install_supported === true) prefer the magic-install REST bootstrap: POST to https://api.trlution.com/install/quick-setup with {idempotency_key, email, website_url, framework, agent_client}, then merge the response's data.mcp_config_snippet into the host's MCP config file. The snippet already carries headers.Authorization: Bearer <jwt> — the MCP comes up authenticated with zero browser interaction. Save data.container.id AND data.container.hash for the follow-up onboarding calls.
  3. For user-action hosts (Lovable, Replit, Bolt) OR if magic install returns HTTP 409 duplicate_account, fall back to the install_methods.body (tokenless) and the host's OAuth Connect-button flow. After OAuth completes, call list_containers to recover container.hash.
  4. Ask the user to reply go (after enabling the MCP / completing OAuth). Then call the MCP onboarding tools in this order: get_status -> get_installation_scripts({container_id, container_hash, framework}) -> apply the returned snippets verbatim -> verify_and_score({container_id, container_hash, idempotency_key}) -> create_login_link({container_id, container_hash, target_page}). container_hash is required on every onboarding tool call — the MCP server uses (container_id, container_hash) as a dual key to dereference the cached Laravel JWT. Skip it and every call returns HTTP 401 auth_required.

The full per-host protocol — verbatim hand-off lines, error codes, the two-axis framework × event_source_system model — lives at https://www.tracklution.com/agent-install.md. The MCP at https://mcp.tracklution.com/mcp is the canonical install surface; the REST endpoint at https://api.trlution.com/install/quick-setup is the agent-facing front door to it.

For humans

If you are a human and your AI assistant invoked this package, you can also install Tracklution directly:

Related packages

The packages below all run the same binary and point at the same canonical Tracklution MCP. They exist so brand- and category-surface lookups don't miss.

Discovery surfaces

All Tracklution agent-discovery surfaces are always-on and CORS-open:

License

MIT. See LICENSE.

Source: packages/tracklution/README.md at commit 6e61b98

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v3.3.0LatestOct 26, 2026
  2. v3.2.1Sep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts