Blog

How do I find jobs with Claude Code?

2026-09-28

To find jobs with Claude Code, connect a job feed to it as an MCP server, then ask for roles in plain English. With Find your role first, that's one claude mcp add command, and Claude Code can then search about 250,000 open roles pulled straight from company career boards on Greenhouse, Lever and Ashby.

Claude Code can already browse the web. So why add anything? Mostly because searching the open web for job postings is slow and messy, and a feed gives it a clean list to start from.

Why not just ask Claude Code to search the web?

You can. It'll run a few searches, open some pages, and come back with something. The trouble is what it finds. General web search surfaces aggregator pages, old reposts and listings that closed weeks ago. And it's hard to ask a search engine what a company posted in the last few hours.

A job feed flips the order. Claude Code asks the feed for matching roles first, gets short records with links, and only then opens the handful of postings worth reading. That's fewer tool calls and a much better starting list.

Step 1: get an agent key

Sign in with Google at findyourrolefirst.click/account. Subscribe ($9 a month), then create an agent key. Keep it somewhere safe; it goes in the next command.

Step 2: add the MCP server to Claude Code

Paste this into your terminal, with your key in place of YOUR_API_KEY:

claude mcp add --transport http --scope user jobfeed https://findyourrolefirst.click/mcp --header 'Authorization: Bearer YOUR_API_KEY'

The --scope user part makes the feed available in every project, so you don't have to add it again per folder.

Step 3: check it connected

Start Claude Code and type:

/mcp

You should see jobfeed in the list. If it shows an error, the usual cause is a key pasted with a stray space or quote.

Step 4: ask for roles

Now just ask. A few prompts that work well:

Find product manager roles in New York posted in the last day.

Search for backend engineer roles at Ashby-hosted companies discovered since yesterday. Group them by company.

Look for design roles that mention remote in the location. Open the top five postings and tell me which ones ask for B2B experience.

Behind the scenes Claude Code calls search_jobs, which matches on title, company and location. It can filter by when a role was published or by when the feed first discovered it, and by source (Greenhouse, Lever or Ashby). Honestly, "discovered since" is the filter I'd reach for most, because it catches roles that just went live even when the board shows an older date.

How Claude Code reads the full job description

The feed returns the title, company, location, dates, and the links to the original posting and the application. It leaves out the full description on purpose.

When a role looks interesting, Claude Code opens the original posting with its own web fetch tool and reads the live page. That keeps your context small, since you only pull full descriptions for the roles that survived the first cut. It also means Claude Code reads the page the company is maintaining right now, rather than a copy.

A simple daily routine

Here's a loop that works without much ceremony:

1. Each morning, ask Claude Code for roles in your field discovered since yesterday.
2. Have it open the postings that match and write two lines on each: what the role is and why it might fit.
3. Pick the ones you care about. Apply yourself, from the apply link.

The feed also has a get_changes tool that returns new, updated, reopened and closed roles from a saved cursor, which suits a script or a scheduled check better than a chat. And get_usage shows how much of your monthly allowance is left.

What about LinkedIn alerts or job boards?

They still have a place. LinkedIn alerts are free and cover companies that never touch Greenhouse, Lever or Ashby. Large job boards cover more of the market too.

The tradeoff is timing and control. Alerts arrive on the platform's schedule, and what they include depends on how that platform ranks things. A feed wired into Claude Code runs when you ask, returns roles from the company's own board, and lets the agent do the reading. To be fair, the two work fine together: the feed for tech companies and startups on those three systems, alerts for everything else.

How the allowance works

$9 a month covers 3,000 new roles, up to 1,000 new a day. If Claude Code pulls up a role you've already seen that month, it's free to read again. A search that finds nothing is free too. So you can ask the same question twice without worrying about it.

It won't apply to jobs for you. That part stays with you.

How to try it

1. Sign in with Google at findyourrolefirst.click/account.
2. Subscribe and create an agent key.
3. Run the command:

claude mcp add --transport http --scope user jobfeed https://findyourrolefirst.click/mcp --header 'Authorization: Bearer YOUR_API_KEY'

1. Type /mcp in Claude Code to confirm, then ask for roles.

Using Codex instead? There's a separate guide on searching for jobs with Codex CLI.

Questions

Can Claude Code search for jobs?

Yes. Connect a job feed as an MCP server and Claude Code can search it directly. With Find your role first it searches about 250,000 open roles from company career boards on Greenhouse, Lever and Ashby.

How do I add a job search MCP server to Claude Code?

Run claude mcp add --transport http --scope user jobfeed https://findyourrolefirst.click/mcp --header 'Authorization: Bearer YOUR_API_KEY', then type /mcp to confirm it connected.

Does Claude Code get the full job description?

The feed gives it the links, and Claude Code opens the original posting with its own web fetch tool when a role looks worth reading.

How fresh are the roles?

Every board is checked every two hours, with checks spread through the day, so new roles land continuously.

Can Claude Code apply to jobs for me?

No. The feed finds roles and returns the apply link, and you apply.