English Français العربية

Jobo Job Search

Official registry Search and web

Search a live index of millions of open jobs from employer career sites and 100+ ATS platforms.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http jobo-job-search 'https://jobs-mcp.jobo.world/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "jobo-job-search": {
            "type": "http",
            "url": "https://jobs-mcp.jobo.world/mcp"
        }
    }
}
NPM package jobo-job-search-mcp
Claude Code 
claude mcp add jobo-job-search -e 'PORT=<PORT>' -- npx -y jobo-job-search-mcp@1.1.0
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "jobo-job-search": {
            "command": "npx",
            "args": [
                "-y",
                "jobo-job-search-mcp@1.1.0"
            ],
            "env": {
                "PORT": "<PORT>"
            }
        }
    }
}

Environment variables

  • PORT Port for the local HTTP server (default 3002).

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Jobo Job Search MCP Server
  2. Self-hosting
  3. Why this is a separate server
  4. Tools
  5. Auth model
  6. Stateless by design
  7. Configuration
  8. Development
  9. Registry listing

Jobo Job Search MCP Server

Remote MCP server exposing Jobo's live job index — millions of listings collected from employer career sites and 150+ applicant tracking systems — to LLM clients.

Full client setup (Claude, ChatGPT, Cursor, Codex CLI) and the tool reference: jobo.world/docs/connectors/mcp.

  • Transport: Streamable HTTP, single /mcp endpoint, stateless. Serves MCP spec 2026-07-28 natively and every 2025-era client through the built-in legacy fallback (SDK v2 createMcpHandler, one factory for both eras).
  • Auth: OAuth 2.1. This is a Resource Server; the Authorization Server is the Jobo API. Clients log in with their Jobo account — no API key copy-paste. Required scope: jobs:read.

Self-hosting

The hosted deployment is https://jobs-mcp.jobo.world. To run your own copy instead:

npx jobo-job-search-mcp

Starts the Streamable HTTP server on $PORT (default 3002); point your client at http://localhost:3002/mcp. This changes where the gateway runs, not its auth model — it's still an OAuth resource server gated on Jobo account sign-in, since the upstream API validates every request against the Authorization Server regardless of which copy of the gateway forwarded it. Set MCP_RESOURCE_URL to match whatever host you actually serve it from — see Configuration below.

Why this is a separate server

Jobo.Enterprise/Jobo.Enterprise.Mcp was deliberately re-scoped to analytics-only in v4, which removed search_jobs, get_job_details, list_filters, search and fetch. Adding job tools back there would undo that decision, so this is a second server against the same External API.

The /api/mcp/jobs/* endpoints were never removed — McpController.cs still serves them, and its own comment notes the GET search is "convenient for the canonical ChatGPT search(query) tool". This server is a thin OAuth-forwarding gateway in front of endpoints that were built for it.

The immediate payoff: search + fetch restore Deep Research compatibility. Without that canonical pair a server cannot be used as a ChatGPT Deep Research connector at all.

Tools

ToolPurpose
searchCanonical Deep Research contract: {query} → {results: [{id, title, url}]}.
fetchCanonical Deep Research contract: {id} → {id, title, text, url, metadata}.
search_jobsStructured search — location, work model, employment type, experience level, source, skills, industries, salary, date, facets, paging.
get_job_detailsFull listing for clients not using the Deep Research contract.
list_filtersAccepted values for every filter, with live counts.

search/fetch deliberately take the minimum arguments the contract allows. Anything with structure should go through search_jobs, where filters are real parameters rather than hopeful free text.

What fetch returns

text is self-contained prose, because Deep Research reads it and never opens the URL. It is built from the AI-extracted fields (responsibilities, qualifications, benefits, compensation) in preference to the raw employer HTML, which is boilerplate-heavy and frequently longer than it is useful. The raw description is available via get_job_details with include_description: true.

Auth model

The server is a gateway, not the cryptographic authority. The C# External API validates the JWT with OpenIddict against the same issuer, audience and jobs:read scope; verifying the signature a second time here would only let the two validators drift. So this does the minimum a gateway must:

  1. Require a Bearer token; absent → 401 with the resource-metadata challenge, starting the OAuth flow.
  2. Cheaply reject an already-expired token (decode exp, no signature check) so long-lived clients refresh rather than forwarding a dead token.
  3. Attach the raw current-request token to req.auth, so every tool call forwards the token the client just sent — never one captured at session-initialize.

Stateless by design

No session map. That map lived in process memory, so every restart or redeploy stranded clients with "No active session", and it pinned the deployment to a single replica. Redis cannot back it either: the value is a live transport object holding open streams. Each POST is served by a fresh server and transport with no mcp-session-id issued.

Configuration

VariableDefaultNotes
JOBO_API_URLhttps://connect.jobo.worldUpstream External API.
MCP_RESOURCE_URLhttps://jobs-mcp.jobo.worldOAuth audience. Must differ from the analytics server's mcp.jobo.world.
OAUTH_AUTH_SERVER_URLhttps://enterprise.jobo.worldAuthorization Server.
PORT3002Analytics server uses 3001.

Development

npm install && npm run build && npm test
npm run dev
Verifying without credentials

node --test dist/format.test.js covers the mapping logic, including that search and fetch return exactly the shapes Deep Research requires. For the wire path, point the server at a stub:

JOBO_API_URL=http://localhost:3098 PORT=3097 MCP_RESOURCE_URL=http://localhost:3097 node dist/index.js

Then tools/list and tools/call over HTTP with any JWT-shaped bearer whose exp is in the future — the gateway forwards it and the stub answers. A real token is only needed against the live API.

Registry listing

Published to the official MCP Registry as world.jobo/job-search (the mcpName in package.json; server.json in this directory is the registry manifest). Publishing is automated: the mcp-v* tag workflow publishes npm first, then pushes server.json to the registry under the DNS-TXT-verified world.jobo/* namespace — see ../RELEASING.md. There is no review queue and aggregators poll roughly hourly. Note the official registry has no per-server web page by design — it is a metadata API for aggregators. The downstream surfaces differ: PulseMCP emits a dofollow link, Glama and mcp.so are nofollow. Manual directory submissions (Claude, ChatGPT, aggregator claims) live in ../MCP-DISTRIBUTION.md.

Frequently asked questions

What is Jobo Job Search?

Search a live index of millions of open jobs from employer career sites and 100+ ATS platforms.

How do I install Jobo Job Search?

It runs as a remote server. In Claude Code: claude mcp add --transport http jobo-job-search 'https://jobs-mcp.jobo.world/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Jobo Job Search need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Jobo Job Search open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Jobo Job Search?

It is published by JoboAI. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.