Jobo for Docker MCP Catalog
One gateway, every client, live job data.
Docker's MCP Toolkit runs a gateway that sits between your AI clients and the MCP servers in a profile, so a server added once is available to every client connected to it. Jobo's job search server is a remote server: nothing runs in a container, and the gateway forwards to the hosted endpoint after you authorize with your Jobo account. The catalog listing has been prepared and is not live yet; until it is, add the hosted URL to your client directly.
- Type
- Remote server
- Transport
- Streamable HTTP
- Endpoint
- https://jobs-mcp.jobo.world/mcp
- Authentication
- OAuth (sign in with your Jobo account)
- Listing
- Prepared, not live yet
What can you do with the Docker MCP Catalog integration?
Add Jobo's job search server to a Docker MCP Toolkit profile and share it across every client connected to the gateway.
Configured once
A server in a Toolkit profile reaches every client connected to the gateway, so you do not repeat the setup in each editor and assistant.
Nothing to run
The entry is a remote server. There is no image to pull and no container to keep up to date; the gateway connects to Jobo's hosted endpoint.
OAuth through Docker Desktop
You authorize in the browser from the server's configuration tab, and can revoke the connection from the same place.
The same tools as everywhere else
Search, structured search with filters, filter lookups and full job documents: the server is the one every other client on this site connects to.
How do you connect Docker MCP Catalog to Jobo?
One-time setup. After this, the data keeps itself current.
- 1
Turn on the MCP Toolkit
In Docker Desktop, open Settings → Beta features, enable Docker MCP Toolkit and apply.
- 2
Add Jobo to a profile
Open MCP Toolkit → Catalog, select the Jobo server and choose Add to, picking a profile or creating one. This step works once the listing is live.
- 3
Authorize
In the server's Configuration tab, choose the OAuth method and follow the authorization link. Sign in with your Jobo account in the browser.
- 4
Connect a client
Open MCP Toolkit → Clients and select Connect next to your client. Any other client can run the gateway itself over stdio.
bashdocker mcp gateway run --profile <profile-id>
What goes wrong with Docker MCP Catalog, and how do you fix it?
The things people actually hit when running Jobo in Docker MCP Catalog.
- Jobo is not in the catalog yet
- The listing has not been published yet. Until it is, add https://jobs-mcp.jobo.world/mcp to your client directly; the guide for your client is on the integrations page.
- The server is in the profile but tools return an authorization error
- The OAuth connection was not completed or has been revoked. Open the server's Configuration tab in the MCP Toolkit and authorize again.
- 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.
How do you get the most out of Docker MCP Catalog?
- Use the Toolkit when you want one place to manage servers across several clients. For a single client, adding the URL directly is one step shorter.
- Keep result counts small while exploring. Search bills per job returned; reading a single listing is free.
Which other Jobo integrations work alongside Docker MCP Catalog?
Start pulling live jobs into Docker MCP Catalog
One Jobo account covers every integration, and the same job index sits behind all of them.













