JobsAPI.dev
Access structured job data from 15+ sources through one developer-friendly API. Normalized schema, source-aware enrichment, and Wellfound company intelligence.
https://jobsapi.dev/Connect straight to this server’s public endpoint.
https://api.jobsapi.dev/mcpWe add this server to your workspace, walk through sign-in once, then open Studio with tools ready to run.
Last probed Sep 14, 2026 · api.jobsapi.dev
6tools discovered
Search jobs
Unified multi-source job search (mirrors GET /jobs/search). Fans a keyword search out across the registered API-native sources and returns one normalized, deduplicated record list. Including "linkedin" in `sources` additionally dispatches a real async scrape job (see submit_scrape_job) and reports its jobId/pollUrl instead of inline records for that source.
Submit a scrape job
Creates a real, billable, asynchronous scrape job (mirrors POST /jobs) -- this is NOT a free lookup, it dispatches real browser/HTTP acquisition against the target URL and consumes the caller's usage quota exactly like the REST endpoint. `url`'s hostname must be within this deployment's allowed-domains list. Poll status with get_job_status, then get_job_result / get_job_records once succeeded.
Get job status
Returns a job's status only (mirrors GET /jobs/:id): jobId, status, timestamps.
Get job result summary
Returns a completed job's safe result summary (mirrors GET /jobs/:id/result): recordCount, pagesVisited, duplicatesSkipped, etc. on success, or a curated error on failure. Returns 409 (via an error result) if the job is still queued/running -- call get_job_status first.
Get job records
Returns the actual scraped records for a succeeded job, paginated (mirrors GET /jobs/:id/records). This is where per-record fields such as salary (salaryRaw/salaryMin/salaryMax/salaryCurrency) appear when the source provides them -- there is no separate salary-only tool.
Get current usage/quota
Returns the authenticated client's current-period usage and remaining quota (mirrors GET /usage): plan, requests/credits/bandwidth used and remaining, rate-limit remaining.
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
Directory coverage for brandsAccess structured job data from 15+ sources through one developer-friendly API. Normalized schema, source-aware enrichment, and Wellfound company intelligence.
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
MCPBundles probed 6 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
JobsAPI.dev may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.
Operate JobsAPI.dev? Verify ownership to take over this directory entry.
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.