Jobo for Claude
Let the assistant search the job market directly.
Jobo's job search server is a remote MCP server, and Claude can connect to it as a custom connector. Once it is added, Claude searches a live index of jobs collected from employer career sites and reads full listings (responsibilities, qualifications, compensation, company context) so it can cite them. You sign in with a Jobo account instead of pasting an API key.
- Server URL
- https://jobs-mcp.jobo.world/mcp
- Transport
- Streamable HTTP
- Authentication
- OAuth (sign in with your Jobo account)
- API key
- None
What can you do with the Claude integration?
Add Jobo as a connector in Claude and it searches and cites live job listings.
Search and fetch, the canonical pair
The server implements the search and fetch tools that research-style connectors expect, alongside a richer filtered search for questions with structure to them.
OAuth, not API keys
Claude signs in with your Jobo account. There is no key to copy into a config file, commit by accident, or rotate by hand.
Filters as real parameters
Work model, employment type, experience level, source, skills, industries, salary and date are structured filters, not hints buried in a text query.
Filter discovery built in
Lookup tools return the accepted values for every filter with live job counts, so the model uses real values instead of guessing at spellings.
Self-contained job documents
Fetching a job returns responsibilities, qualifications, benefits, compensation and company context as readable prose, so the model can quote it without opening the page.
How do you connect Claude to Jobo?
One-time setup. After this, the data keeps itself current.
- 1
Add the server in Claude
Open Connectors at claude.ai/customize/connectors. Select Add, then Add custom connector. Enter a name and the server URL below, then click Continue. Keep the detected authentication options and click Add. The server URL is https://jobs-mcp.jobo.world/mcp.
bashhttps://jobs-mcp.jobo.world/mcp - 2
Sign in to Jobo
Click Connect on the connector and complete the Jobo sign-in in the browser.
- 3
Check the tools loaded
In a chat, click + and check the connector is switched on under Connectors.
- 4
Ask for jobs
“Find senior Rust roles in Europe that pay over $150k and list the employer, location and link for each.” The assistant picks the filters, runs the search, and cites the listings it used.
What goes wrong with Claude, and how do you fix it?
The things people actually hit when running Jobo in Claude.
- Claude keeps asking to authenticate
- The access token expired and was not refreshed. Remove the server and add it again; the server issues a standard OAuth challenge and the sign-in starts over.
- A search returns a credits message instead of jobs
- Searches are billed per job returned, against your plan's included jobs first and then your wallet. When neither covers the request nothing is billed, and the tool returns the amount needed with a top-up link.
- The model invents job listings
- Ask it to include the listing URL for each role. Every real result has one, so a role without a URL did not come from a tool call.
How do you get the most out of Claude?
- Custom connectors are available on every plan. The Free plan allows one.
- On Team and Enterprise, an Owner adds the connector under Organization settings → Connectors, and members then click Connect.
- The connector is account-level: once added it works in claude.ai, Claude Desktop and the mobile apps.
- Name the filters you care about — location, seniority, work model, salary floor. The model maps them onto real parameters, which is far more accurate than free text.
- Keep result counts small while exploring. Search bills per job returned; reading a single listing is free.
- For bulk export rather than research, use the Feed API. An assistant is the wrong tool for moving thousands of rows.
Which other Jobo integrations work alongside Claude?
Start pulling live jobs into Claude
One Jobo account covers every integration, and the same job index sits behind all of them.













