Claude Snagajob connectorWhat Claude can find on Snagajob for your job search.
The Claude Snagajob connector exposes 2 tools, both on the reading side. 0 write, 0 undocumented. One searches hourly job postings near a place, the other opens a single posting. Below: what you get in the chat, and the step that still happens on Snagajob.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can search Snagajob
Instead of filling in search boxes and clicking through listings one by one, you tell Claude what kind of hourly work you want and where. Claude queries Snagajob, brings back postings ranked by match, and can open any of them to show pay, schedule and requirements. The listings appear in an interface inside the conversation.
A shortlist for a given place. search_jobs looks for hourly and local postings near a location you name, and returns a ranked list along with breakdowns by industry, company, pay band and employment type, so the next question can narrow things down.
The full picture on one posting. get_job_details opens a single job from those results: description, requirements, benefits, schedule and the link to apply.
A way to the application. The posting that get_job_details brings back carries its apply link, and that link is where the application itself happens, on Snagajob.
What it will not do: the directory sheet lists no tool that applies, saves a job or contacts an employer. Snagajob says so plainly: you head to Snagajob to apply. By default the sheet exposes reading only, which is a floor observed on a public page, not a guarantee. Nothing runs by itself either: no alert fires when a new posting appears. For that kind of hands-off flow, the Integrations hub covers automation tools, which do a different job, and the Claude connectors page lists the others.
Five words before you connect
The vocabulary around this connector, in one minute.
- Connector
- A link you set up once between Claude and an outside service, so Claude can use that service while it answers you.
- Tool
- One named thing a connector lets Claude do. Claude chooses the tools it needs while answering, and the directory sheet names them.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it uses afterwards. Granted once per person, and it can be withdrawn.
- Directory
- The official catalog where each connector has a sheet with its publisher, its purpose and the full list of tools it exposes.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude query an outside service such as Snagajob.
Connect the Claude Snagajob connector in three steps
- 01
Find Snagajob in Claude
Open Claude's settings, go to Customize then Connectors, and look Snagajob up in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector before members can use it.
- 02
Start the connection
Click Connect on its row. If the service opens a window of its own, that window belongs to Snagajob, not to Claude. A link that breaks is fixed by choosing Disconnect, then connecting again.
- 03
Check what you accept
If an authorization screen appears, read it before accepting: the service sets there what the access covers. Then ask Claude for jobs in a town or neighborhood, and the results show up in the conversation.
The 2 tools, both for reading
Snagajob gives Claude 2 tools: 2 that read your account, 0 that change something in it.
Snagajob's server marks both tools as read only. Tool names stay exactly as Claude shows them.
- 2 read
What Claude reads (2)
2 toolsTwo tools that look at public job postings and change nothing on Snagajob.
get_job_details
Opens one posting picked from the search results and brings back its full description, requirements, benefits, schedule and the link that leads to the application.
search_jobs
Looks for hourly and local postings near a location and returns them ranked by match, with breakdowns by industry, company, pay band and employment type that help narrow the next search.
What Claude checks with you first
By default, Claude stops and asks before each action it takes for someone in an outside service. The prompt appears in the conversation when it matters.
On Team and Enterprise workspaces, owners decide whether a member may let some actions through without a prompt each time. They can also limit what a connector may do across the whole organization, for example keeping reading open and closing writing. That setting binds everyone. Claude works with the access of the person who connected and nothing more. Here both listed tools only read postings, so no source describes a confirmation for them.
Which plans include it
None of the 819 sheets in the official directory shows plan availability, so the answer for this connector is published nowhere.
The published rule is general: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organization before members can connect. For the current state of this one, the connector's sheet in the official directory is where to look.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, so no search runs on its own when a new posting goes up.
Everything specific here comes from the publisher, JobGet, through the directory sheet and its server: no Claude help article covers Snagajob. A list showing only reading tools is a floor, not a promise, since an administrator can open actions that appear on no public sheet. The verified badge in the directory is not a security audit, and Anthropic states on every sheet that it neither picks the tools a publisher exposes nor guarantees how they behave.
Need help connecting Snagajob to Claude?
A person reads every message.