Coding agent

Jobo for Goose

Live job data without leaving your coding agent.

Jobo's job search server is a remote MCP server, and Goose can connect to it directly. Once it is added, the agent in Goose 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.

Goose logoGooseAdd to ~/.config/goose/config.yaml
yaml
extensions:
  jobo-job-search:
    name: jobo-job-search
    type: streamable_http
    uri: https://jobs-mcp.jobo.world/mcp
    enabled: true
    timeout: 300

What can you do with the Goose integration?

Give the agent in Goose live job search over MCP, with OAuth sign-in and no API key.

01

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.

02

OAuth, not API keys

Goose signs in with your Jobo account. There is no key to copy into a config file, commit by accident, or rotate by hand.

03

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.

04

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.

05

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 Goose to Jobo?

One-time setup. After this, the data keeps itself current.

  1. 1

    Add the server to Goose

    Add this entry to ~/.config/goose/config.yaml. If the file already lists other servers, add the jobo-job-search entry alongside them.

    yaml
    extensions:
      jobo-job-search:
        name: jobo-job-search
        type: streamable_http
        uri: https://jobs-mcp.jobo.world/mcp
        enabled: true
        timeout: 300
  2. 2

    Sign in to Jobo

    Goose registers itself with the server automatically and opens an OAuth window in your browser. Approve access there.

  3. 3

    Check the tools loaded

    Check that the extension is listed and enabled under goose configure → Toggle Extensions, or in the Extensions list in goose Desktop.

  4. 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 Goose, and how do you fix it?

The things people actually hit when running Jobo in Goose.

Goose 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 Goose?

  • The endpoint key is uri, not url, and the type is streamable_http.
  • Prefer a wizard? Run goose configure, select Add Extension, choose Remote Extension (Streamable HTTP) and enter the same URL.
  • 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.

Start pulling live jobs into Goose

One Jobo account covers every integration, and the same job index sits behind all of them.