# Trackly CLI [Health: Active]

**Category:** 🏢 Workplace & Productivity  
**Repository:** https://github.com/trackly-app/trackly-cli  
**GitHub Stars:** 3  
**npm Downloads (last month):** 2190  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/trackly-cli

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

## Tools
Capabilities this server exposes over MCP:

- **trackly_search_jobs** — Search by roles, regions, states/provinces, internship level, favorites, recency, annual USD salary floor, sponsorship, work arrangement, and pipeline status
- **trackly_get_job** — Get details by Trackly ID, with availability and retry guidance
- **trackly_search_companies** — Semantic company search
- **trackly_list_companies** — List all tracked companies
- **trackly_get_stats** — Job tracker metrics and status counts
- **trackly_get_preferences** — Read bounded discovery preferences, edit availability, and save revision
- **trackly_update_experience_limits** — Atomically replace role-specific limits on a job's stated minimum years
- **trackly_update_status** — Mark jobs as applied, saved, or dismissed
- **trackly_ask** — Natural language job search (20/day)
- **trackly_get_job_brief** — Get a network brief, with availability and retry guidance
- **trackly_contacts_at_company** — Search contacts at a specific company
- **trackly_get_company_workspace** — Full company workspace (jobs, contacts, hiring managers, campaigns)
- **trackly_request_company** — Request a company be added to Trackly (rate-limited to 5 pending)
- **trackly_get_apply_queue** — Get user-approved jobs ready for execution
- **trackly_get_application_profile** — Get versioned profile answers and provenance
- **trackly_get_profile_onboarding** — Get schema plus missing questions
- **trackly_update_application_profile** — Save scoped answers with optimistic concurrency; revoking sensitive storage takes a two-step confirmation
- **trackly_start_apply_execution** — Start a target-counted accessible Apply execution
- **trackly_get_active_apply_execution** — Recover the active execution before legacy batch recovery
- **trackly_get_apply_execution** — Read the authoritative progress funnel and immutable child waves
- **trackly_list_recoverable_apply_executions** — List bounded exact-member recovery candidates after context loss
- **trackly_recover_exact_apply_members** — Recover only one explicitly confirmed candidate set without substitutes
- **trackly_list_apply_review_handoffs** — Rediscover active, value-free review-handoff receipts for one execution
- **trackly_claim_apply_review_handoff** — Claim and classify one exact review-handoff group before reconciliation
- **trackly_get_apply_execution_snapshot** — Fetch a compact bounded projection for current execution members and required profile keys
- **trackly_resume_parked_apply_member** — Explicitly resume one parked member for a fresh non-mutating access probe
- **trackly_approve_apply_execution_resume** — Approve one exact resume identity for an unchanged execution snapshot
- **trackly_advance_apply_execution** — Transactionally create the next eligible immutable wave with frozen accessKnowledge
- **trackly_list_apply_access_deferments** — List persistent user access deferments
- **trackly_defer_apply_access** — Persist a job or company deferment from a Trackly jobId
- **trackly_clear_apply_access_deferment** — Clear one discovered user access deferment
- **trackly_record_apply_execution_dispositions** — Record typed, value-free access classifications
- **trackly_stop_apply_execution** — Stop an execution without changing saved-job state
- **trackly_create_apply_batch** — Freeze an exact recent-first approved batch
- **trackly_cancel_apply_batch** — Retire a legacy fixed batch after explicit user confirmation
- **trackly_get_active_apply_batch** — Recover the newest unexpired active batch after context loss
- **trackly_get_apply_batch** — Read frozen membership with opaque pagination
- **trackly_claim_apply_batch** — Acquire or renew a batch mutation lease
- **trackly_checkpoint_apply_batch** — Bulk-record redacted inspection checkpoints and human actions
- **trackly_bind_apply_surface** — Bind an initial or recovered browser surface to the existing run and exact requisition URL
- **trackly_record_apply_surface_evidence** — Record current-epoch inventory, missing-tab, close-receipt, and post-close absence evidence
- **trackly_record_apply_submission_evidence** — Record redacted submit-request, success-page, user-confirmation, or provider-receipt evidence
- **trackly_approve_apply_batch_resume** — Approve one exact default resume for the current frozen run set
- **trackly_certify_apply_batch_truth** — Certify final answer and wording fingerprints after every other review-readiness gate
- **trackly_start_apply_run** — Start or reuse a manual-submit browser run
- **trackly_get_apply_evidence** — Get aggregate, value-free beta evidence and release readiness
- **trackly_get_apply_protocol** — Get current workflow and compatibility rules
- **trackly_report_apply_observation** — Send redacted ATS mechanics feedback
- **trackly_lint_application_text** — Locally lint application writing and return only value-free violations plus a draft hash
- **trackly_diagnose_local_path** — Locally diagnose the exact implicated filesystem path without deleting files
- **trackly_validate_apply_tab_keep_set** — Locally validate an exact expected/keep tab set against complete caller-supplied inventories without controlling the browser or sending tab IDs remotely
- **trackly_validate_apply_resume_upload** — Locally validate adapter capability and ordered value-free attachment proof stages
- **trackly_report_apply_observations** — Bulk-send up to 20 leased, batch-bound redacted observations
- **trackly_record_application_outcome** — Record review or confirmed submission outcome
- **trackly_record_application_outcomes** — Bulk-record up to 20 leased batch outcomes with per-member conflicts
- **trackly_prepare_resume** — Prepare a private expiring resume file for upload
- **trackly_verify_prepared_resume** — Recheck the confirmed resume immediately before attachment
- **get_more_tools** — Report a missing capability so Trackly can improve its MCP surface

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What Trackly CLI does

Trackly CLI gives MCP-compatible agents access to Trackly’s job discovery, company research, application tracking, and controlled application workflows. The underlying service indexes more than 250,000 jobs across over 5,400 companies and more than 40 ATS types.

Job search supports filters for role, region, state or province, internship level, favorites, recency, minimum annual USD salary, sponsorship, work arrangement, and pipeline status. Agents can retrieve individual job records, search companies semantically, list tracked companies, inspect tracker statistics, and find contacts or network information associated with a company.

The server also exposes application-profile and execution controls. Agents can read profile answers and their provenance, discover missing onboarding fields, update scoped answers with optimistic concurrency, and work with user-approved jobs in an Apply queue. Apply execution tools provide progress, recovery, review handoffs, access deferments, immutable waves, and explicit resume approval. Guided application work stops before final submission and can pause for authentication, CAPTCHA, verification, unexpected origins, or unobservable field state.

## How it works

Trackly offers two MCP connection modes. The hosted endpoint uses streamable HTTP at `https://mcp.usetrackly.app/api/mcp`; users authenticate through OAuth, with Google sign-in available during connector setup. Headless clients that cannot complete interactive sign-in can send a Trackly API key as a bearer token.

The local mode runs the installed CLI as an MCP process over stdio. Local connections provide the CLI’s MCP tool set and are intended for clients such as Cursor, Windsurf, and Claude Code. Hosted connections provide 55 tools, while the local distribution provides 58; hosted and local modes share the main search, company, status, and Apply functionality, with some local-only tools.

The CLI can also be used directly from a terminal. Commands cover job searches, job details, company lookup, statistics, preferences, status changes, contacts, briefs, company workspaces, API-key management, and agent setup. Adding `--json` produces JSON output for CLI commands.

## Setup and configuration

For hosted use, add a custom connector in a compatible AI client and enter the Trackly MCP URL, then complete sign-in. Claude Code can register the same endpoint with:

```bash
claude mcp add --transport http trackly https://mcp.usetrackly.app/api/mcp
```

For local use, install Node.js 20.20+ or 22.22+, then install and authenticate the package:

```bash
npm install -g trackly-cli
trackly login
trackly agent setup --client both
trackly agent doctor
```

Claude Code can register the local process with `claude mcp add --scope user trackly -- trackly mcp`. Cursor and Windsurf can use the CLI’s stdio MCP configuration. An API key can be saved with `trackly config --api-key <key>` or supplied for an individual command with `--api-key`; `--base-url` is available as a one-off global option.

## Tools and capabilities

- Search jobs with structured filters or natural-language queries through `trackly_ask`.
- Retrieve job details, network briefs, contacts, company workspaces, and company lists.
- Read statistics, discovery preferences, experience limits, application profiles, and onboarding requirements.
- Mark jobs as applied, saved, or dismissed, and maintain role-specific experience limits.
- Request new companies and inspect application queues and execution progress.
- Recover exact Apply candidates, review handoffs, parked members, and access deferments without substituting unconfirmed jobs.

## Limitations and notes

Natural-language `trackly_ask` searches are limited to 20 uses per day. Company requests are limited to five pending requests. Profile updates use optimistic concurrency, and revoking sensitive profile storage requires a two-step confirmation.

Apply automation is deliberately fail-closed. It does not submit applications automatically: the agent fills user-approved forms and stops before Submit for manual review. Greenhouse has full support in the local guided workflow; Ashby and Lever are best effort, while other supported ATS classes use constrained guided mode. LinkedIn-hosted forms and unverified origins remain manual-only. Browser capability, resume data, authentication state, and exact field state are checked during execution.

_Full upstream README: https://allmcps.com/mcp/trackly-cli/readme_