Jobo for Zed
Live job data inside your editor.
Jobo's job search server is a remote MCP server, and Zed can connect to it directly. Once it is added, the agent in Zed can search a live index of jobs collected from employer career sites, look up valid filter values, and read full listings — useful when you are building a job board, a sourcing tool or anything else that needs real job data to develop against. You sign in with a Jobo account instead of pasting an API key.
{
"context_servers": {
"jobo-job-search": {
"url": "https://jobs-mcp.jobo.world/mcp"
}
}
}What can you do with the Zed integration?
Give the agent in Zed live job search over MCP, with OAuth sign-in and no API key.
Real listings to build against
Seed a database, fill a fixture file or design a results page with live jobs instead of lorem-ipsum roles. Every result carries its listing URL.
OAuth, not API keys
Zed 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 Zed to Jobo?
One-time setup. After this, the data keeps itself current.
- 1
Add the server to Zed
Add this entry to Zed's settings.json. If the file already lists other servers, add the jobo-job-search entry alongside them.
json{ "context_servers": { "jobo-job-search": { "url": "https://jobs-mcp.jobo.world/mcp" } } } - 2
Sign in to Jobo
Because the entry has no Authorization header, Zed prompts you to authenticate. Follow the prompt and finish the Jobo sign-in in the browser.
- 3
Check the tools loaded
Open Settings → AI → MCP Servers. The indicator next to jobo-job-search is green when the server is active.
- 4
Ask for jobs
“Use Jobo to pull ten live data-engineering roles in Berlin and build the job card component against them.” The agent picks the filters, runs the search and designs against real listings.
What goes wrong with Zed, and how do you fix it?
The things people actually hit when running Jobo in Zed.
- Zed 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 Zed?
- Open the file with the zed: open settings file action.
- The key is context_servers, not mcpServers. Merge the entry into your existing settings rather than replacing the file.
- Or use the UI: Settings → AI → MCP Servers → Add Server → Add Remote Server.
- 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 production code, call the REST API or an SDK with an API key. The MCP server is for the agent's own lookups while you build.
Which other Jobo integrations work alongside Zed?
Start pulling live jobs into Zed
One Jobo account covers every integration, and the same job index sits behind all of them.













