Claude ZipRecruiter connectorWhat Claude can find in ZipRecruiter job listings.
The Claude ZipRecruiter connector exposes 1 tool. It reads job listings, 0 tools change anything, 0 are undocumented. Below: what the search covers, where it stops, why applying still happens on ZipRecruiter, and who in your organization controls it.
Verified Trustpilot reviews · AI, automation & growth agency
Why plug ZipRecruiter into Claude
Instead of juggling tabs and filters on a job board, you describe the role you want in plain words and the connector fetches live ZipRecruiter listings into the conversation. Its publisher, ZipRecruiter, adds an optional carousel so you can flip through roles with salary and location, then open the ones worth a closer look.
A shortlist from one sentence. Ask for a role, a city and a pay band, and search_jobs narrows the results by location and radius, salary range, how recently the ad went up, remote, hybrid or on-site, employment type and seniority, according to ZipRecruiter's documentation.
By title, company or place. The directory description lists those three entry points for a search; the filters then apply on top of whichever one you start from.
Straight to the listing. Each result links to ZipRecruiter, and the publisher's examples show a View details window that offers to open the full ad on the site.
What it will not do: apply for you or reach jobs outside the United States and Canada. Its sheet only exposes reading by default, and nothing runs in the background either: no alert fires when a new ad appears. For that kind of watch, an automation tool is the right job; the Integrations hub gathers that side, and the Claude connectors hub lists the other connectors.
The vocabulary in one minute
Five words you will run into while setting this up.
- Connector
- The link you add once between Claude and an outside service, so Claude can use that service while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs by itself, and the directory sheet lists them by name.
- Authorization
- The sign-in screen a service shows to hand Claude its access. ZipRecruiter says its connector does not ask end users for one.
- Approval
- The confirmation Claude waits for before it goes ahead with something that changes an account, shown right in the conversation.
- MCP
- The shared standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service.
Connect ZipRecruiter to Claude in three steps
- 01
Find ZipRecruiter in your settings
Open Claude's settings, go to Customize, then Connectors, and look for ZipRecruiter. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch it on for the organization before members can add it.
- 02
Add it from its row
Click Connect next to it and follow whatever window appears. If the connector misbehaves later, Disconnect it and add it again, which is the documented fix for a broken link.
- 03
Check for a permission screen
Connectors usually open the service's own sign-in page at this point, and that page sets the scope of access. ZipRecruiter states its connector skips that step for end users, so you may land straight back in Claude.
The 1 tool, sorted by what it does
ZipRecruiter gives Claude 1 tool: 1 that read your account, 0 that change something in it.
One tool, and it reads. Its name stays in English, exactly as Claude shows it.
- 1 read
What Claude reads (1)
1 toolA single search over live ZipRecruiter listings.
search_jobs
Pulls live ZipRecruiter job ads that match a job title, a company or a place, filtered by pay, distance, work arrangement, contract type, seniority and posting date. Each call brings back up to 5 listings, limited to the United States and Canada.
What Claude asks before it acts
By default, Claude stops and asks you before any action it takes on an account on your behalf. Here, no source describes a confirmation specific to search_jobs, so that general rule is the one that applies.
On Team and Enterprise, owners decide whether members can let some actions through without being asked every time, and they can limit what a connector may do for the whole organization: keep reading, close writing. That setting binds everyone. Claude also works with your access and nothing more. The per-tool label (read-only versus write or delete) only shows up in a connected account's settings, never on a public page.
Which plans include it
Out of 819 sheets in the official directory, none shows availability per plan. That information is not published anywhere, connector by connector.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner enables a connector before members can use it. For the current state of this one, check its directory sheet from your own account.
Where this connector stops
A connector is not an automation. Claude calls this tool while it answers you, and nothing starts by itself when a new ad goes live.
Everything known here comes from ZipRecruiter itself: neither Claude's help center nor Anthropic's developer docs have a page for this connector. The verified badge on the directory is not a security audit, and Anthropic says on every sheet that it does not choose the tools a publisher exposes nor guarantee they behave as described. Only plug in what comes from a publisher you trust.
The publisher describes live listings: nothing in the sources links the search to a personal ZipRecruiter profile, saved jobs or past applications.
Need help connecting ZipRecruiter to Claude?
A person reads every message.
