JobCubby

Run your job search like it's your job

Hiring

Artificial Intelligence

Career

Visit WebsiteSee on Product Hunt

Thanks for the detailed answers in the comments, Pavel, especially the breakdown on scoped OAuth permissions for connected agents. Splitting read/write/destructive access so a connected assistant can be given read-only is the right default for something holding someone's whole job search.

A concrete case where the MCP server helps: someone actively interviewing who wants Claude to log a new application and draft screening answers between meetings, without switching to a separate tab to update a tracker by hand afterward.

I noticed the exchange with Manjeet about self-hosting and AGPL. We work on Heym, which is self-hosted and source-available in a similar automation and MCP space, so I get why that request comes up for anything holding salary history and employer contacts. If the tracker core does eventually get open sourced, would that be something people could realistically self-host against their own Postgres, or more of a reference implementation without a full deployment story behind it?

The assist-only stance, drafts prepared but a person always hits submit, seems like the right line to hold as more of this becomes agent-driven on both sides of the hiring process.

Nice execution and the developer docs are genuinely well written. I'll say the thing though. A tool holding my entire employment history and job search needs to be open source or at least source available, full stop. Self-hosting is the only real answer to the "what if you shut down" problem, exports are a consolation prize. The moment there's an AGPL repo I can run in my homelab, I'm your loudest advocate. Until then I'm rooting for you from the sidelines.

@solopa Interesting idea but you're asking people to hand an AI agent write access to literally their entire job search, salary expectations, work history, who they know at which company. That's some of the most sensitive data a person has, especially if they're searching while still employed. Where is this data stored, who can see it, do you train models on it, and what happens to it if JobCubby shuts down? Job search tools come and go fast so I'd want to know there's an export and delete story before putting anything real in there.

Coming at this from the other side of the table. Slightly terrifying to imagine candidates showing up with an AI that logged every interaction with me, follow-up timing optimized, my name saved as a contact with notes. The power balance in hiring has been tilted toward companies with ATSs for decades, so honestly, fair play. Just funny to watch the tooling arms race arrive at our doorstep.

@solopa Congrats on the launch! Looks clean. Honest question though, I've been tracking my job search in a Notion template for years and before that a spreadsheet, and tools like Teal and Huntr already do the tracker plus AI resume thing. What actually made you build another one? Is the MCP stuff the whole pitch or is there something in the core tracker that made you switch from whatever you used before?

Honestly the MCP server angle is kind of brilliant, I would love to see a salary negotiation prep mode built in. Like, have the AI help you benchmark offers, draft counter emails, and prep you for compensation conversations using data from the role and your tracked experience.

The MCP server angle is genuinely useful, I ran my whole search from Claude last week and it felt like having a personal assistant without the awkwardness of copy pasting. Cover letter drafts are solid, just need to tweak the tone a bit.