What tools does the openjobs MCP server provide?

openjobs exposes 6 tools: explain_data_source, explain_filters, get_app_intro, get_index_status, get_job_details, search_jobs. This list was returned by the running server when we connected to it.

Does openjobs require an API key?

No. openjobs answered a tools/list request without credentials.

How do I install openjobs?

Run: claude mcp add --transport http openjobs https://openjobs-3168f222.alpic.live/. One-click install links for Cursor and VS Code are also available on the server's page.

Connection check verified live · 26h ago

openjobs

Find jobs in your own words and apply on the company website — no detours.

Web search & scraping Memory & knowledge Databases & SQL

Install

Remote (HTTP)

claude mcp add --transport http openjobs https://openjobs-3168f222.alpic.live/

Tools 6

GitHub stars —

Installs / wk —

Licence —

Transport streamable-http, sse

Last checked 26h ago

Tools & capabilities

6 tools

Read from the running server on 26h ago.

explain_data_source read-only

Where job listings come from, licensing, and links to the data provider. Use only when the user asks about data source, Feashliaa, license, attribution, or who built OpenJob.

explain_filters read-only

Plain-language search tips for job seekers. Use when the user asks how to search or what they can filter. No technical jargon in the reply.

get_app_intro read-only

Friendly introduction to OpenJob for job seekers. Use when the user is new or asks how this works. Return plain language only.

get_index_status read-only

How much of the job board is loaded and whether search is ready. Explain to the user in simple terms, not technical sync jargon.

get_job_details read-only urlurlssearch_modeuser_intent

Fetch full posting text for job urls from search_jobs. Set search_mode resume_match when fetching postings to compare against the user's resume or background; keyword_search otherw…

search_jobs read-only atslimittitlecompanylocationmin_salary +10

Search open company job listings. Map the user's natural language to filters. Always set search_mode on search_jobs and get_job_details: keyword_search when the user only describes… Search open company job listings. Map the user's natural language to filters. Always set search_mode on search_jobs and get_job_details: keyword_search when the user only describes a role, place, or filters; resume_match when they upload a resume/CV or ask to match jobs to their background or memory. Never show parameter names (role_cluster, skill_level, search_mode, etc.) to the user — speak like a career coach. Do not mention data sources or licenses unless the user asks — use explain_data_source for that. Every job has url and apply_url (company careers page). When you list jobs in a table, bullets, or prose, each row must include at least one clickable markdown link to that url — e.g. linked title [Title](url), linked company name, or a separate Apply / View posting link. Never list a job with no way to click through. After search_jobs, add a structured follow-up in the user's language — the widget shows cards; your text adds coaching. Include: (1) a markdown table Role | Company | Fit (use resume/memory when available; otherwise one-line highlight per row); (2) a numbered priority list for applying (top 3–5 with brief rationale); (3) if the user shared background, one CV positioning sentence they can reuse; (4) related title search variants as inline tags (e.g. Entrepreneur in Residence, Venture Development, GTM Associate, Chief of Staff). When the user has a resume or detailed background, call get_job_details on the best 5–8 urls before ranking. Do not invent match percentages. search_jobs live-checks up to 8 Greenhouse/Ashby/Lever listings per search and drops roles confirmed closed on the company site. For deeper advice on a shortlist, call get_job_details on the best urls (batch up to 10) to load full posting text. Use verifiable_only=true when the user wants only listings we can double-check live (~30% of the board). When the user uploads a resume (curriculum vitae) or asks to match jobs to their background (or ChatGPT memory): (1) extract target titles, seniority, locations, remote preference, title keywords, exclusions; (2) if missing both a role and a place, ask one short question; (3) run 2–4 search_jobs calls with varied strategies and search_mode resume_match; (4) for the best 5–10 results call get_job_details with their urls (batch up to 10) and search_mode resume_match; (5) dedupe, rank using description_text when status is ok, explain top picks in plain language with apply links; do not invent percentage match scores. For role families (founder/founder's/founders associate, chief of staff, product manager) pass the user's words in title — OpenJob normalizes spelling variants automatically; role_cluster is optional. hide_recruiters defaults true (skip recruiting agencies).