tracklix-mcp
README.md
# tracklix-mcp
<!-- mcp-name: io.github.zhowe-designs/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](https://tracklix.co), 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`:
```bash
npx tracklix-mcp
```
Or install globally:
```bash
npm install -g tracklix-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):
```json
{
"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:
```json
{ "url": "https://www.amazon.com/dp/B08N5WRWNW?tag=zhowe-20" }
```
Output:
```json
{
"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](https://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
```bash
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:
```bash
npm run build
npx @modelcontextprotocol/inspector node dist/index.js
```
## License
MIT. See [LICENSE](./LICENSE).
Built by [Pamplemoose Games LLC](https://pamplemoose.co). Issues and PRs
welcome at [github.com/zhowe-designs/tracklix-mcp](https://github.com/zhowe-designs/tracklix-mcp).
TDQS
A4.6/5.0
Scored across 2 tools
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