Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words
Beginner mode On
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch
☰ MenuSettings
Beginner mode On
ColoursSystemLightDark
LanguageไทยEnglish中文日本語한국어EspañolDeutsch

Server Side Tracking

by tracklutionversion 3.3.0i★ –iRuns in the cloud
Registry namecom.tracklution/server-side-tracking

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://mcp.tracklution.com/mcp

Run this in your terminal

claude mcp add --transport http server-side-tracking https://mcp.tracklution.com/mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "server-side-tracking": {
      "url": "https://mcp.tracklution.com/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://mcp.tracklution.com/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain tracklution.com (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

  • More stars than 0% of the other 32466 servers in this category
  • Published to the registry more recently than 75% of the other 32466 servers in this category
  • Basic checks equal to or better than 100% of the other 32466 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Server Side Tracking safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (3.3.0) reached the registry 11 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, HotCodePush

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

HotCodePush

by hotcodepush-team

Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.

Runs in the cloudUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

tracklution-cli

Monorepo for the npm packages that act as Tracklution's brand- and category-surface discovery wedge for AI coding agents:

  • tracklution -- canonical. The published bin runs the agent-readable install instructions.
  • create-tracklution -- alias so npm create tracklution@latest works.
  • @tracklution/cli -- scope-reserved alias.
  • tracklution-mcp -- alias today; future versions will offer a local stdio<->Streamable-HTTP MCP proxy.
  • server-side-tracking -- category-surface alias for npm view server-side-tracking / npx server-side-tracking.
  • conversion-tracking -- category-surface alias for npm view conversion-tracking / npx conversion-tracking.
  • conversion-api -- category-surface alias for npm view conversion-api / npx conversion-api.

What this is

When a user prompts an AI coding agent (Cursor, Claude Code, Codex, Windsurf, Cline, Lovable, Replit, Bolt, ...) with "Install Tracklution" -- or, by category, "Install server-side tracking" / "Install conversion tracking" -- most agents reflexively run npm view and then npx . These packages exist so that reflex succeeds and the agent gets deterministic, paste-safe install instructions delivered via the agent's normal stdout-reading toolloop -- instead of falling back to web search and inventing tracking code.

The actual install runs through the Tracklution MCP server at https://mcp.tracklution.com/mcp. The agent reaches that MCP via a one-shot REST bootstrap at https://api.trlution.com/install/quick-setup (the "magic install" path) -- which provisions the user's account and returns an mcp.json snippet that already carries Authorization: Bearer . This CLI publishes the machine-readable description of that flow.

User: "Install Tracklution"

| v Agent runs npm view tracklution (finds the package) Agent runs npx tracklution (reads stdout + parses --json) Agent POSTs to /install/quick-setup (one HTTP call, REST bootstrap) Agent merges data.mcp_config_snippet (Authorization header included) Agent calls get_status -> get_installation_scripts -> verify_and_score (every onboarding call carries container_hash for auth)

User-action hosts (Lovable, Replit, Bolt) cannot drive HTTP-POST + file-edit from inside the agent, so they fall back to the OAuth Connect-button flow -- the CLI's install_methods block tells the agent which hosts support magic install via magic_install_supported: true.

Layout

tracklution-cli/

package.json workspace root (private, not published) packages/ tracklution/ canonical published package (the bin) bin/cli.js src/payload.js single source of truth for the stdout payload package.json create-tracklution/ resolve-and-spawn shim at-tracklution-cli/ resolve-and-spawn shim (publishes as @tracklution/cli) tracklution-mcp/ resolve-and-spawn shim server-side-tracking/ resolve-and-spawn shim (category-surface) conversion-tracking/ resolve-and-spawn shim (category-surface) conversion-api/ resolve-and-spawn shim (category-surface) tests/ cli.test.js default / --json / --version / --help parity.test.js compare local payload to live install-recipes endpoint aliases.test.js each alias produces the same stdout as the canonical plugins/ claude/tracklution/ Claude plugin bundle (submitted from this repo path; skills are the single copy) openai/tracklution/ OpenAI plugin package source (plugin.json, mcp.json, assets/) scripts/build-openai-plugin.js builds the OpenAI ZIP: package source + the Claude skills server.json MCP Registry entry (remote only) .github/workflows/ test.yml lint, tests, pack dry-run; uploads the OpenAI ZIP as a run artifact publish.yml npm publish on v* tags release.yml attaches the OpenAI ZIP to the GitHub release on v* tags (public link) mcp-registry.yml manual: publish server.json to the MCP Registry

Development

npm install               # installs workspace deps, symlinks packages/* into each others node_modules

npm test # runs Vitest across all three test files npm run lint # syntax-checks every bin/cli.js npm run pack:dry # dry-run npm pack for all published packages

Publishing

Bump the version in every packages/*/package.json (keep them in lockstep), tag vX.Y.Z, push to GitHub. The publish workflow at .github/workflows/publish.yml verifies the lockstep, then runs npm publish --provenance for each package in dependency order (canonical tracklution first, then all alias shims).

The same tag push runs .github/workflows/release.yml, which builds the OpenAI plugin ZIP and attaches it to the tag's GitHub release (created if missing). Public download links, no GitHub login needed:

  • https://github.com/tracklution/tracklution-cli/releases/download/vX.Y.Z/tracklution-openai-plugin- .zip
  • https://github.com/tracklution/tracklution-cli/releases/latest/download/tracklution-openai-plugin.zip (always the newest release)

To attach a ZIP built from main to an existing release without a new tag, run the release workflow by hand (Actions, release, Run workflow) with the tag name. The run summary prints the download links.

Directory listings
  • ChatGPT (OpenAI): the ZIP above is what gets uploaded at platform.openai.com/plugins. When you change anything under plugins/openai/tracklution/ or the skills, bump version in plugins/openai/tracklution/plugin.json (OpenAI treats each upload as a new package version) and release as above. Before the first submission the portal also needs review.demo_recording_url in plugin.json and the domain-verification token served by the MCP host (OPENAI_APPS_CHALLENGE_TOKEN).
  • Claude: the directory reads plugins/claude/tracklution straight from this repo; there is nothing to upload. Validate locally with claude plugin validate ./plugins/claude/tracklution --strict.
  • Skills live once, in plugins/claude/tracklution/skills/; the OpenAI build copies them into the ZIP.
  • MCP Registry: bump version in server.json (a version can be published only once) and run the mcp-registry workflow by hand.

Single source of truth

The install methods, MCP URL, and reference URLs are duplicated across:

Drift is policed by tests/parity.test.js, which fetches the live https://www.tracklution.com/api/install-recipes/ endpoint and deep-checks the install_methods block of payload.js against it. The test is skipped if PARITY_TEST_SKIP=1 (offline CI) or the live endpoint returns a non-200.

License

MIT.

Ask PopNx