Jobo for Rovo Dev CLI
Live job data without leaving your coding agent.
Jobo's job search server is a remote MCP server, and Rovo Dev CLI can connect to it directly. Once it is added, the agent in Rovo Dev CLI 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. Rovo Dev CLI reaches the server through the mcp-remote bridge, which runs locally and carries the browser sign-in.
{
"mcpServers": {
"jobo-job-search": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://jobs-mcp.jobo.world/mcp"
],
"transport": "stdio"
}
}
}What can you do with the Rovo Dev CLI integration?
Give the agent in Rovo Dev CLI 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
Rovo Dev CLI 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 Rovo Dev CLI to Jobo?
One-time setup. After this, the data keeps itself current.
- 1
Add the server to Rovo Dev CLI
Add this entry to ~/.rovodev/mcp.json. If the file already lists other servers, add the jobo-job-search entry alongside them.
json{ "mcpServers": { "jobo-job-search": { "command": "npx", "args": [ "-y", "mcp-remote", "https://jobs-mcp.jobo.world/mcp" ], "transport": "stdio" } } } - 2
Sign in to Jobo
The first time the server starts, the mcp-remote bridge opens the Jobo sign-in page in your default browser. Approve access there; the bridge caches the tokens and later starts are silent.
- 3
Check the tools loaded
Run acli rovodev run, then /mcp, and confirm jobo-job-search is listed as enabled with its tools.
- 4
Ask for jobs
“Use Jobo to find 20 remote senior backend roles posted this week and write them to seed.json in my app's job schema.” The agent picks the filters, runs the search and works with real listings instead of invented fixtures.
What goes wrong with Rovo Dev CLI, and how do you fix it?
The things people actually hit when running Jobo in Rovo Dev CLI.
- The server fails to start
- This setup runs the mcp-remote bridge through npx, which needs Node.js installed and on the PATH that the client launches processes with. Run the npx command from the config in a terminal to see the actual error.
- Rovo Dev CLI 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 Rovo Dev CLI?
- acli rovodev mcp opens the file in your editor.
- Rovo Dev CLI uses a transport key where most clients use type.
- 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 Rovo Dev CLI?
Start pulling live jobs into Rovo Dev CLI
One Jobo account covers every integration, and the same job index sits behind all of them.













