Jobo for Replit
A job board from a prompt, on live data.
Replit builds an app from a description, and Jobo supplies the jobs. The generated app calls Jobo's REST API from your app's own backend code, with your API key stored in Replit's Secrets so it never reaches the browser. Replit's agent can also connect to Jobo's MCP server, which lets it look at real listings while it builds; that connection is for the agent, not for the published app.
- API
- https://connect.jobo.world
- Auth
- X-Api-Key header
- Key stored in
- Secrets
- Called from
- your app's own backend code
- MCP for the agent
- Supported
What can you do with the Replit integration?
Build a job board or sourcing tool in Replit on live job data, with your API key kept server-side.
Real listings from the first prompt
The app Replit generates shows live jobs collected from employer career sites, not placeholder rows you replace later.
The key stays server-side
Your API key lives in Replit's Secrets and is read by your app's own backend code. The browser calls your app, and your app calls Jobo.
Filters the API already has
Location, work model, employment type, experience level, skills, salary and posting date are request parameters, so the builder wires up filter controls instead of inventing its own matching.
A prompt that carries the contract
The search integration prompt in Jobo's docs spells out the request shape and the mistakes that still return 200, which a builder's agent otherwise gets wrong.
Live job search while you build
Replit's agent can connect to Jobo's MCP server and look at real listings and valid filter values as it writes the app.
How do you connect Replit to Jobo?
One-time setup. After this, the data keeps itself current.
- 1
Create a Jobo API key
Sign up, open Developers → API Keys in the Jobo dashboard and create a key. New accounts start with a $5 balance and need no credit card. A sandbox key returns fictional jobs for free while you build.
- 2
Add the key to Replit's Secrets
Open the project, select Tools and, under Setup, select Secrets. Select New Secret, enter JOBO_API_KEY as the key and your API key as the value, and select Add Secret. The secret reaches your code as an environment variable. Enter credentials in the form, never in the Agent chat.
- 3
Prompt the build
Tell Replit what to build and where the data comes from. The call must run in your app's own backend code, never in browser code. Jobo's docs have a longer prompt that covers filters, facets and error handling.
textAdd job search to this app using the Jobo API. - Call POST https://connect.jobo.world/api/jobs/search from server-side code only. - Send my key from the JOBO_API_KEY secret in the X-Api-Key header. Never expose it to the browser. - Request body: {"queries": ["<keywords>"], "locations": ["<place>"], "page": 1, "page_size": 20}. - The response has a "jobs" array and a "total". Show title, company.name, locations and date_posted, and link each job to its listing_url. - Add keyword and location inputs and pagination. On HTTP 402 show "out of credits" instead of retrying. - 4
Optional: connect Jobo's MCP server to Replit
Open Settings → Integrations → Your integrations, select Add custom, then Add personal MCP server. Enter a display name and the server URL, leave the advanced header settings empty, and click Test & save; Replit walks you through the sign-in. The server URL is https://jobs-mcp.jobo.world/mcp, and you sign in with your Jobo account rather than a key. Whether the custom MCP options appear depends on your account or workspace; if they are missing, ask your workspace administrator.
- 5
Publish
Open Publishing, select Adjust settings and check Production app secrets: secrets set in the editor do not carry over to the published app automatically. Use any deployment type except Static, which cannot read secrets.
What goes wrong with Replit, and how do you fix it?
The things people actually hit when running Jobo in Replit.
- The API key is visible in the browser
- The generated code is calling Jobo from the page. Ask Replit to move the call into your app's own backend code and read the key from Secrets, then create a new key in the Jobo dashboard and delete the exposed one.
- A filter returns no jobs
- Filter values are lowercase, hyphenated and matched exactly, and an unrecognised value is not an error. Check them against the documented values: full-time rather than full_time, onsite rather than on-site.
- Searches start failing with HTTP 402
- The balance cannot cover the request. Search is billed per job returned, so a results page of 20 jobs costs 20 jobs. Top up, or lower page_size.
- The published app cannot use the MCP connection
- That is how Replit documents it: a custom MCP server gives tools to Replit's own agent while it builds, not to the app it generates. The app reads jobs through the REST API.
- The published app says the key is missing, but the editor preview works
- The secret was added in the editor only. Add it under Publishing → Adjust settings → Production app secrets and publish again.
How do you get the most out of Replit?
- Build against a sandbox key first. It returns fictional jobs for free, so a prompt that loops on a broken request costs nothing.
- Keep page_size at what the page shows. Search bills every job returned, not every job displayed.
- Cache results for repeated searches rather than calling the API on every page view.
Which other Jobo integrations work alongside Replit?
Start pulling live jobs into Replit
One API key covers every integration, and the same job index sits behind all of them.













