mcpbeat

Trackly CLI MCP Server

io.github.trackly-app/trackly
answering

Trackly CLI is answering right now. Last checked 12 min ago. 1 729 installs a week from npm. Last commit 3 Aug 2026.

AI job search for Claude, ChatGPT, Cursor. 128K+ jobs, 1,900+ companies. OAuth or stdio.

Installs per day peak 738 · avg 142 · +157% w/w
a month agotoday
Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
887 ms
Response time
average over 24h
1 729
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add trackly --transport http https://mcp.usetrackly.app/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "trackly": {
      "url": "https://mcp.usetrackly.app/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.trackly]
url = "https://mcp.usetrackly.app/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "trackly": {
      "url": "https://mcp.usetrackly.app/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "trackly": {
      "url": "https://mcp.usetrackly.app/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://mcp.usetrackly.app/api/mcp streamable-http needs key 884 ms 12 min ago

Trackly CLI — questions

Answers built from our own checks of this server.

Why is there no tool list for Trackly CLI?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Trackly CLI working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 887 ms. The bar chart above shows every period we have measured.
How do I connect Trackly CLI?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.
Does Trackly CLI need an API key?
Yes. Every time we knock, Trackly CLI answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Trackly CLI?
It answers our handshake in 887 ms on average, which is faster than 7% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Trackly CLI?
The npm package trackly-cli was installed 1 729 times in the last week. Week over week that is +157%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Trackly CLI open source?
Yes — it is published under the MIT licence, written in JavaScript, 1 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.