Find your next Laravel job with an AI agent

Job hunting as a Laravel developer means the same tabs open every morning: a couple of general boards, a few Laravel-specific ones, and whatever a newsletter linked this week. The roles overlap, the filters differ, and the good ones are gone by the time you circle back. The problem is not a shortage of listings. It is that they live in too many places.

LaraBench aggregates more than 20 Laravel-specific sources into one feed. You can browse it on the web, and because it is also an MCP tool, you can hand the search to an AI agent and describe what you want in a sentence.

One Laravel jobs board, many sources

The Laravel jobs board collects listings from more than 20 sources that post Laravel work, and normalizes them into one searchable feed. You filter by stack, source, seniority, work arrangement, and country, and sort by newest or by salary. Every listing keeps a link back to the original posting, so you always apply at the source rather than through a middleman.

That is useful on its own. But typing the same filters into a web form every day is exactly the kind of repeat task an agent is good at.

Let your agent do the filtering

Once LaraBench is connected as an MCP server, your AI tool can call a search_laravel_jobs tool. You describe the search in plain language and the agent maps it onto the filters:

• A full-text query across title, company, description, technologies, and location.
• Technologies, such as laravel, livewire, inertia, vue, or filament.
• Seniority, from junior through lead.
• Work arrangement: remote, hybrid, or onsite.
• Countries, regions, or eligibility text.
• Salary: a minimum, a currency, a period, or only jobs that disclose pay.
• Specific sources, and a sort order.

So a prompt like "find remote senior Laravel roles that use Livewire, newest first" becomes a single tool call, and the agent gets back structured results it can reason about, not a page of HTML to scrape.

What comes back for each job

The tool returns detailed, structured data per role, so the agent can compare and shortlist without guessing:

• Title and a short description excerpt, with a link to the full listing.
• Salary when it is disclosed: minimum, maximum, currency, and period.
• Company name, and location with its work arrangement and country.
• Detected technologies, each with the evidence for why it matched.
• Seniority and employment type when the source provides them.
• The source it came from, plus an apply link back to the original post.
• Freshness: when it was posted, and when LaraBench first saw it.

Because technologies come with the evidence for each match, an agent can tell the difference between a role that mentions Laravel in passing and one that is built on it. Because salary and freshness are structured, it can sort and filter on them directly.

An example search

Say you ask your agent for remote senior Laravel and Livewire roles, sorted newest first. It calls the jobs tool with those filters and gets back the current matches, each with its company, location and work arrangement, detected stack, source, and posted date. From there it can do the parts that are tedious by hand: drop anything outside your timezone, rank the ones that disclose salary, and hand you a short list with the apply link for each. You open the ones worth your time and apply on the original site.

The point is not that the agent replaces your judgment. It is that the first pass over a noisy, scattered market is the part worth automating.

View full size

Free window and Premium

Jobs search is free. Free searches cover roles posted in the last 7 days, which keeps results current. Signing in with Premium extends the search window to the last 90 days, which helps when you want a wider view of what is out there.

One practical detail: the jobs search works with LaraBench closed. The MCP shim can call the website jobs API directly, so unlike running code, you do not need the desktop app open to search. See the MCP setup guide for connecting Claude Code, Codex, or Cursor in one click.

Or browse it yourself

Not every search needs an agent. The jobs board has the same feed and the same filters in a normal web page, so you can scan roles, adjust filters, and open listings by hand whenever you would rather click than prompt.

View full size

FAQ

Which AI tools can search Laravel jobs through LaraBench?

Any MCP client connected to LaraBench, including Claude Code, Claude Desktop, Codex, and Cursor. They call the search_laravel_jobs tool with your filters and get structured matches back.

Do I need LaraBench open to search jobs?

No. The jobs search works with the app closed, because the MCP shim calls the website jobs API directly. Running code in your own app is the part that needs the app open.

Is the jobs search free?

Yes. Free searches cover the last 7 days of postings. Premium extends the search window to the last 90 days.

Where do the jobs come from?

From more than 20 Laravel-specific sources, aggregated into one feed. Each listing links back to the original posting so you apply at the source.

How fresh are the listings?

Each job carries its posted date and the date LaraBench first saw it, sources are imported twice a day, and you can sort by newest first.