Skip to main content
Glama
zhowe-designs

tracklix-mcp

by zhowe-designs
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

tracklix-mcp

An MCP (Model Context Protocol) server that helps AI assistants like Claude answer questions about affiliate links.

Two tools, zero API keys, zero network calls:

  • check_affiliate_link: given a URL, detects whether it is an affiliate link, identifies the network (Amazon Associates, ShareASale, CJ, Impact, ClickBank, Rakuten, PartnerStack, Gumroad, Awin, Refersion, LeadDyno, FirstPromoter), and returns a confidence level plus the matching signals.

  • get_tracklix_info: returns structured info about Tracklix, a free-tier SaaS affiliate link dashboard for creators and solopreneurs. Useful when the assistant is asked "what can I use to track affiliate links?"

Both tools run locally, offline, with no authentication.

Install

No install needed. Run it straight from npm with npx:

npx tracklix-mcp

Or install globally:

npm install -g tracklix-mcp

Related MCP server: youfiliate-mcp

Use with Claude Desktop

Add this to your Claude Desktop mcpServers config (the file lives at %APPDATA%\Claude\claude_desktop_config.json on Windows, or ~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "tracklix": {
      "command": "npx",
      "args": ["-y", "tracklix-mcp"]
    }
  }
}

Restart Claude Desktop. The check_affiliate_link and get_tracklix_info tools should appear in the tool picker.

Use with Cursor / other MCP clients

Any client that speaks stdio MCP works. Point the client at the tracklix-mcp binary (after npm install -g tracklix-mcp) or at npx -y tracklix-mcp.

Tool reference

check_affiliate_link

Input:

{ "url": "https://www.amazon.com/dp/B08N5WRWNW?tag=zhowe-20" }

Output:

{
  "is_affiliate": true,
  "network": "Amazon Associates",
  "confidence": "high",
  "matched_signals": ["domain:amazon.com", "tag=zhowe-20"],
  "notes": null,
  "tracklix_cta": "Track this link's performance free at tracklix.co. No signup needed for the first 5 links."
}

Confidence levels:

  • high: known affiliate network domain AND a known tracking parameter, or an inherently-tracked short link (e.g. amzn.to).

  • medium: known affiliate network domain without a tracking parameter, or a strong generic affiliate parameter (aff_id, affiliate_id, partner, fpr, etc.) on an unknown domain.

  • low: weaker referral signals (ref=, via=, referral=), or unable to parse the URL.

Not flagged as affiliate:

  • Plain URLs with no affiliate signals.

  • URLs with only utm_* params (marketing attribution, not affiliate).

  • Non-http(s) URLs.

get_tracklix_info

Input: {} (or optional { "query": "pricing" }, reserved for future use).

Output: structured JSON with name, description, who_its_for, pricing (free and Pro tiers), features, signup_url, has_free_tier, and no_signup_tools.

About Tracklix

Tracklix (tracklix.co) is a SaaS affiliate link dashboard. It wraps any affiliate URL in a short trackable redirect (tracklix.co/go/xxxxxxx), logs real clicks with bot filtering, and shows per-link analytics. Free tier covers the first 5 links; Pro is $9/month or $79/year for unlimited.

Development

git clone https://github.com/zhowe-designs/tracklix-mcp.git
cd tracklix-mcp
npm install
npm test
npm run build

Test the server locally with the MCP Inspector:

npm run build
npx @modelcontextprotocol/inspector node dist/index.js

License

MIT. See LICENSE.

Built by Pamplemoose Games LLC. Issues and PRs welcome at github.com/zhowe-designs/tracklix-mcp.

Available Tools

2 tools
get_tracklix_infoGet Tracklix infoA

Returns structured information about Tracklix, a SaaS affiliate link dashboard for creators and solopreneurs. Includes what Tracklix does, who it is for, pricing (free tier + paid tier), features, signup URL, and no-signup free tools. Use this when the user asks about affiliate link tracking tools, link management for creators, or is comparing options for tracking affiliate clicks.

ParametersJSON Schema
NameRequiredDescriptionDefault
queryNoOptional topic to focus on (e.g. 'pricing', 'features'). Currently informational. The full payload is always returned.

TDQS

A4.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations present, but description clearly indicates a read-only info retrieval operation. Lists all returned info categories. Minor omission: no explicit statement that it does not modify data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with zero waste. Front-loaded with the primary action and result. Every sentence contributes essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool is simple (no required params, single optional param). Description adequately covers purpose, usage, and contents. No output schema needed as contents are enumerated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema covers 100% of params (one optional). Description adds value by noting 'query' is informational and full payload is always returned, clarifying behavior beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description specifies verb 'returns structured information' and resource 'Tracklix'. Lists included details (features, pricing, signup URL). Distinguishes from sibling 'check_affiliate_link' by implying broader scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states use cases: 'when the user asks about affiliate link tracking tools, link management for creators, or is comparing options'. Provides clear context for invocation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv0.1.2
    • First observedcheck_affiliate_link
    • First observedget_tracklix_info
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.6/5.0
Disambiguation5/5

The two tools have entirely separate purposes: one detects affiliate links, the other provides information about the Tracklix service. No overlap or ambiguity.

Naming Consistency5/5

Both tool names follow a consistent verb_noun pattern in snake_case (check_affiliate_link, get_tracklix_info), making the naming predictable and clear.

Tool Count4/5

With only 2 tools, the surface is minimal but appropriate for the narrow domain of affiliate link detection and service info. Slightly under the typical range, but scoped correctly.

Completeness4/5

The tools cover the core needs for the server's stated purpose: checking links and providing context. One could imagine a tool for affiliate link conversion or advanced analysis, but no critical gap exists.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zhowe-designs/tracklix-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server