ZipRecruiter
by ZipRecruiter
Search live ZipRecruiter job listings from an AI agent. One tool, search_jobs, matched literally by ZipRecruiter's own llms.txt. No OAuth and no user account. The interactive job carousel widget is the surface worth reading closely — its Apply button appends auto_apply=1.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect ZipRecruiter via MCP
https://api.ziprecruiter.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
ZipRecruiter Tools & Capabilities (1)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
auto_apply=1is undocumented and we did not test it. The widget's Apply button appends it to the job URL before opening the page. ZipRecruiter publishes nothing describing the parameter, and because ZipRecruiter states applications cannot be withdrawn, we would not test it. Its behaviour is genuinely unknown, not merely unmentioned.- Five results per call. ZipRecruiter caps
search_jobsat five results with an offset of zero through five, so an agent sees roughly thirty listings at most before it runs out of pagination. Any claim your agent makes about "the whole market" rests on that sample. - No safety annotations could be read. The endpoint rate-limited our IP before we completed a
tools/list, so we cannot reportreadOnlyHintordestructiveHint. Two vendor statements call the tool read-only; the server's own declaration is unread. - The endpoint rate-limits aggressively.
https://api.ziprecruiter.com/mcpreturned HTTP 429 with a plain-text body after a modest number of requests and stayed blocked for several minutes at a time, while other paths on the same host answered normally. NoRetry-Afterheader was sent and ZipRecruiter documents no limit. - US and Canada only. ZipRecruiter documents the country filter as accepting US or CA. This is not a global job search.
- The documentation page is invisible to text extractors.
https://api.ziprecruiter.com/mcp/docsreturns 253KB of HTML that yields six words to an HTML-to-text pass, because the entire page is a React application whose copy lives in an inline JavaScript bundle. There is no__NEXT_DATA__and no RSC payload. We recovered the content by reading string literals out of that bundle; a reader using ordinary tooling would conclude the page is empty. - The privacy policy predates the connector. ZipRecruiter's Global Privacy Policy, effective 2025-08-12, contains no reference to MCP, the Model Context Protocol, AI assistants or third-party AI models. Its only AI mention concerns matching job seekers with employers.
- No
llms-full.txtand no.mdroute. Of the four documentation routes, only the nominated URL and/llms.txtexist on these hosts;llms-full.txt, the.mdsuffix and several sibling doc paths return 404. The two that exist are the whole corpus. - ZipRecruiter's marketing host blocks automated readers.
www.ziprecruiter.com/blog/returned HTTP 403 behind a Cloudflare interstitial to our requests. The press-release quotation below was retrieved by a separate research pass and we could not independently re-fetch it. - Whether a search is logged against you is unresolved. With no account there is no history to write, but ZipRecruiter's privacy policy describes collecting usage and technical data from visitors generally. We found no statement covering MCP requests specifically.
Frequently asked questions
No tool can. The server exposes one tool, search_jobs, and it only reads listings. But the job carousel widget renders an Apply on ZipRecruiter button that opens the listing in your browser with auto_apply=1 appended to the URL. That is a click you make, not a call the model makes, and it leaves the connector entirely.
ZipRecruiter does not say anywhere we could find. The parameter appears in the widget's own compiled JavaScript, and we found no ZipRecruiter help article, blog post or developer page describing it. Because a ZipRecruiter 1-Click Apply cannot be withdrawn, treat the behaviour as unknown rather than assuming it merely pre-fills a form.
No. ZipRecruiter's documentation states plainly that the HTTP MCP transport does not require end-user OAuth, and the directory records the server as authless. The endpoint served us a JSON-RPC protocol error rather than an authentication challenge, and no RFC 9728 resource descriptor exists on the host. There are no scopes to grant.
One, and both available sources agree on the name. Anthropic's directory lists search_jobs, and ZipRecruiter's own llms.txt independently names search_jobs with the note read only, no auth required. Neither list contains a name the other omits. The connector also ships a widget resource, which is not a tool.
Your query, and your approximate location when you do not supply one. ZipRecruiter's documentation describes a jobs near me prompt returning results within 25 miles of the user's IP location, so the request IP resolves to a place. There is no account, no resume and no profile in this surface because there is no sign-in.
The tool returns structured results regardless, and ZipRecruiter calls the carousel optional. A client that does not implement MCP Apps receives the text results and never renders the widget, which also means it never renders the Apply button. Whether your client shows the carousel is the client's decision, not a setting ZipRecruiter exposes.
ZipRecruiter publishes no price, plan gate or quota for it, and no sign-in exists to attach billing to. We did hit aggressive HTTP 429 rate limiting on the endpoint host during this check, lasting several minutes per block. ZipRecruiter documents no rate limit, so absence of a published limit is not absence of a limit.
Five per call. ZipRecruiter's documentation states the tool returns up to five results per call with pagination via an offset accepting values zero through five. That caps a single conversation at roughly thirty listings before the agent runs out of pages, which matters when you ask it to compare a whole market.
Sources
- ZipRecruiter Job Search MCP documentation (retrieved 2026-08-23). HTTP 200. Content is client-rendered; quotations were read from the inline bundle in that same response. · retrieved 2026-08-23
- ZipRecruiter LLM manifest, naming the MCP endpoint and
search_jobs(retrieved 2026-08-23). HTTP 200, last modified 2026-08-21. · retrieved 2026-08-23 - ZipRecruiter job carousel widget resource (retrieved 2026-08-23). HTTP 200,
content-type: text/html; charset=utf-8; profile=mcp-app. The Apply-button behaviour described above was read from this file. · retrieved 2026-08-23 - ZipRecruiter help centre, how to apply and 1-Click Apply (retrieved 2026-08-23) · retrieved 2026-08-23
- ZipRecruiter help centre, applications cannot be withdrawn (retrieved 2026-08-23) · retrieved 2026-08-23
- ZipRecruiter help centre, Apply Now versus 1-Click Apply (retrieved 2026-08-23) · retrieved 2026-08-23
- ZipRecruiter Global Privacy Policy, effective 2025-08-12 (retrieved 2026-08-23) · retrieved 2025-08-12
- ZipRecruiter robots.txt, naming the LLM manifest (retrieved 2026-08-23). HTTP 200,
Allow: /for ClaudeBot with a path exclusion list. · retrieved 2026-08-23 - ZipRecruiter blog, "ZipRecruiter Launches ChatGPT App for AI-Powered Job Discovery" (retrieved 2026-08-23 by a separate research pass; the host returned HTTP 403 to our own requests) · retrieved 2026-08-23
- Live posture check: an anonymous GET of
https://api.ziprecruiter.com/mcpreturned HTTP 406 with the JSON-RPC error "Not Acceptable: Client must accept text/event-stream" rather than an authentication challenge.https://api.ziprecruiter.com/.well-known/oauth-protected-resource/mcpreturned HTTP 404 with an Express-generated body, as did a control path, so no RFC 9728 descriptor exists (2026-08-23). · retrieved 2026-08-23 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16. Records
is_authlesstrue,auth_posture"no_auth",has_mcp_apptrue and permissions "Read only". · retrieved 2026-08-16 - ZipRecruiter support — <mailto:support@ziprecruiter.com>
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- ZipRecruiter
- Tools
- 1
- Domain
- api.ziprecruiter.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.