Trackly CLI
Search and track tech job listings from your agent via Trackly’s CLI MCP mode when you are sizing markets, scouting employers, or planning a services pivot.
Overview
io.github.kevinastuhuaman/trackly is a MCP server for the Idea phase that exposes Trackly’s job-tracking CLI data—99K+ jobs across 775+ companies—to AI agents over stdio.
What is this MCP server?
- Catalog spans 99K+ jobs and 775+ companies per published description
- Dual surface: Trackly CLI plus MCP via `npx` with `mcp` positional arg
- npm package trackly-cli v0.1.5, stdio transport
- Website and docs at usetrackly.app/cli
- GitHub source: kevinastuhuaman/trackly-cli
- Description states 99K+ jobs and 775+ companies
- Package version 0.1.5; identifier trackly-cli; stdio via npx `mcp` argument
Community signal: 1 GitHub stars.
What problem does it solve?
Builders guessing market demand lack a fast, agent-queryable view of who is hiring and for what skills.
Who is it for?
Indie hackers doing opportunity research, devtool positioning, or freelance niche selection who want MCP-native job market queries.
Skip if: Teams needing full ATS workflow inside their CRM, or builders who do not want npx-based CLI MCP startup.
What do I get? / Deliverables
After you add the Trackly MCP entry, your agent can query job and company signals from the Trackly corpus while you research niches or pricing power.
- Agent-accessible job and company tracking queries via Trackly
- CLI + MCP unified workflow documented at usetrackly.app/cli
- Research answers grounded in the advertised 99K+ job / 775+ company index
Recommended MCP Servers
Journey fit
Job-market intelligence belongs in Idea research because solo builders use hiring signals to validate demand before they commit months to a product. Research is the shelf for external labor-market datasets—not Build integrations—because the value is discovery and trend scanning across companies.
How it compares
Job-market data MCP/CLI, not a recruiting CRM integration like Attio.
Common Questions / FAQ
Who is io.github.kevinastuhuaman/trackly for?
It is for solo builders and researchers who use hiring trends to inform product ideas and want those queries available inside Claude Code, Cursor, or similar MCP hosts.
When should I use io.github.kevinastuhuaman/trackly?
Use it during idea and validate research when you need aggregated job and company signals before committing to a build or positioning angle.
How do I add io.github.kevinastuhuaman/trackly to my agent?
Configure MCP to run npx with `-y` and the trackly-cli package, passing the positional argument `mcp` for stdio mode per the registry package definition.