trackly-cli

The only job tracking CLI built for AI agents.

Search 99,000+ jobs across 775+ companies and 22 ATS types. Track applications, get AI-powered recommendations, and manage your job search -- from the terminal or through Claude Code, Cursor, and other MCP-compatible AI agents.

Quick Start

npm install -g trackly-cli
trackly login
trackly jobs --function product

At a Glance

775+ companies | 99K+ jobs | 22 ATS types | CLI + MCP | 10 MCP tools

CLI Commands

trackly jobs                          # List jobs
trackly jobs --modality remote        # Filter remote jobs
trackly jobs --function product        # Filter by function
trackly jobs --company 243            # Filter by company ID
trackly job 1234                      # Get job details
trackly jobs 1234                     # Alias for job details
trackly companies                     # List companies
trackly companies search "fintech"    # Semantic company search
trackly search "fintech"              # Alias for semantic company search
trackly stats                         # Show metrics
trackly status                        # Alias for stats
trackly apply 1234                    # Mark as applied
trackly save 1234                     # Save a job
trackly dismiss 1234                  # Dismiss a job
trackly ask "PM jobs in SF"           # Natural language search (20/day)
trackly api-key create                # Generate API key
trackly api-key list                  # List API keys
trackly config                        # Show current CLI config
trackly config --api-key trk_xxx      # Save an API key for future commands
trackly version                       # Show installed version
trackly whoami                        # Show current user
trackly logout                        # Clear credentials

Add --json to any command for JSON output. Use --api-key <key> or --base-url <url> as one-off global flags when needed.

MCP Server Setup

One-liner (recommended)

claude mcp add-json trackly '{"command":"trackly","args":["mcp"]}'

Claude Code manual config

Add to ~/.claude/settings.json:

{
  "mcpServers": {
    "trackly": {
      "command": "trackly",
      "args": ["mcp"]
    }
  }
}

Cursor

Add to .cursor/mcp.json or ~/.cursor/mcp.json:

{
  "mcpServers": {
    "trackly": {
      "command": "trackly",
      "args": ["mcp"]
    }
  }
}

Then use natural language in Claude Code or Cursor:

• "Find me PM jobs at fintech companies"
• "What remote engineering roles are available?"
• "Mark job 1234 as applied"

MCP Tools Reference

| Tool | Description | |------|-------------| | trackly_search_jobs | Search and filter jobs by function, company, location, modality, status | | trackly_get_job | Get full details for a specific job | | trackly_search_companies | Semantic company search | | trackly_list_companies | List all tracked companies | | trackly_get_stats | Job tracker metrics and status counts | | trackly_update_status | Mark jobs as applied, saved, or dismissed | | trackly_ask | Natural language job search (20/day) | | trackly_get_job_brief | Get network brief for a job (company signal, top contact, actions) | | trackly_contacts_at_company | Search contacts at a specific company | | trackly_get_company_workspace | Full company workspace (jobs, contacts, hiring managers, campaigns) |

Authentication

Option 1: Google OAuth (recommended)

trackly login

Opens your browser for Google sign-in. Tokens are stored locally at ~/.trackly/config.json.

Option 2: API Key

If OAuth doesn't work (firewalls, headless servers, CI), use an API key instead:

1. Sign in at usetrackly.app
2. Go to Settings → API Keys → Create
3. Save the key:

trackly config --api-key trk_xxxxxxxxxxxxxxxxxxxx

Or pass it per-command:

trackly --api-key trk_xxxxxxxxxxxxxxxxxxxx jobs --json

Or set it as an environment variable:

export TRACKLY_API_KEY=trk_xxxxxxxxxxxxxxxxxxxx
trackly jobs

Generate a key from the CLI

If you're already logged in via OAuth, you can create a key without visiting the web app:

trackly api-key create --name "my-script"
trackly api-key list

Other config

trackly config --clear-api-key           # Clear stored API key
trackly config --base-url http://127.0.0.1:3000  # Point at a different backend

Comparison

| Feature | CLI | Web App | Public API | |---------|-----|---------|------------| | Job search + filters | Yes | Yes | Yes | | Apply/save/dismiss | Yes | Yes | Yes | | AI-powered search | Yes (trackly ask) | Yes | Yes | | MCP integration | Yes (10 tools) | -- | -- | | Browser required | No | Yes | No | | Best for | Terminal + AI agents | Visual browsing | Custom integrations |

Web: usetrackly.app | API docs: usetrackly.app/developers

Frequently Asked Questions

How do I track job applications from the terminal?

Install trackly-cli (npm install -g trackly-cli), authenticate with trackly login or configure an API key, then use trackly jobs to browse openings and trackly apply <id> to mark applications. All data syncs with the Trackly web app at usetrackly.app.

What MCP servers exist for job searching?

trackly-cli includes a built-in MCP server with 10 tools for job search, company lookup, and application tracking. Run trackly mcp or add it to Claude Code with claude mcp add-json trackly '{"command":"trackly","args":["mcp"]}'. It connects to a live database of 99,000+ jobs across 775+ companies.

How do I use Claude Code for job hunting?

Add trackly as an MCP server in Claude Code. Then ask questions naturally: "Find PM jobs at fintech companies in SF", "What companies are hiring for engineering?", or "Mark job 1234 as applied." Claude will use trackly's MCP tools to search and manage your applications.

What are the best CLI tools for job search?

trackly-cli is the first dedicated job tracking CLI. It provides direct terminal access to 99,000+ job postings across 775+ companies, with filters for job function, location, and work modality. It also integrates with AI agents via the Model Context Protocol (MCP).

Security

• OAuth tokens stored in ~/.trackly/config.json with 0600 permissions
• API keys can be stored in the same config file or passed per-command
• OAuth callback bound to 127.0.0.1 only
• Authenticated requests require HTTPS unless you are pointing at localhost
• HTTP requests time out instead of hanging indefinitely
• CSRF protection on login flow
• See SECURITY.md for vulnerability reporting

License

MIT -- see LICENSE