Hiring.cafe Job Listings & Salary Filter Scraper: MCP config, n8n workflow and API

Hiring.cafe searches return job titles, employers, salary ranges, workplace arrangements, tech stacks and application links. A job agent comparing remote Python roles can narrow the search to postings with published salary ranges.

No input fields are required; an agent can narrow results with searchQueries, workplaceTypes and locations.

Fastest route, in Claude Code:

claude mcp add --transport http hiring-cafe-job-listings-and-salary-filter-scraper "https://mcp.apify.com/?tools=fetch-actor-details,nimbryxo-studio/hiring-cafe-job-listings-and-salary-filter-scraper"

One click, signs in with Apify on first use:

Any other client, one command (writes the config for 25+ agents, including Windsurf, Zed, Cline and Goose):

npx add-mcp "https://mcp.apify.com/?tools=fetch-actor-details,nimbryxo-studio/hiring-cafe-job-listings-and-salary-filter-scraper" --name hiring-cafe-job-listings-and-salary-filter-scraper

Every file on this page is generated from the Actor's published schema: 51 of 51 checks pass (validated, not run)
  • MCP configs: 7 of 7 (Uses Apify's hosted MCP endpoint over HTTPS; The tools parameter lists exactly the chosen Actors as owner/name; JSON configs parse and use the client's top-level key and the same URL; Codex TOML has a [mcp_servers.<name>] table with url and bearer_token_env_var; CLI commands quote the same URL and use the streamable HTTP transport; One-click install links decode back to the same URL and carry no token; Only placeholders, no real token)
  • n8n workflow: 11 of 11 (It has a nodes array and a connections object; Every node has a name, type, typeVersion, position and parameters; Node names are unique; Every node type is a known n8n core node (or the Apify node); Every node uses a typeVersion that n8n ships; Every connection points at an existing node; At least one trigger starts the workflow; Every working node is reachable from a trigger; Apify calls use POST and a credential for the token; Actor input matches the Actor's published input schema; No token or credential value is embedded)
  • long-run workflow: 11 of 11 (It has a nodes array and a connections object; Every node has a name, type, typeVersion, position and parameters; Node names are unique; Every node type is a known n8n core node (or the Apify node); Every node uses a typeVersion that n8n ships; Every connection points at an existing node; At least one trigger starts the workflow; Every working node is reachable from a trigger; Apify calls use POST and a credential for the token; Actor input matches the Actor's published input schema; No token or credential value is embedded)
  • example input: 5 of 5 (The schema has no required fields; Every input key exists in the published input schema; Every value has the type the schema declares; Every choice field uses one of its published options; Numbers respect the published minimum and maximum)
  • code snippets: 4 of 4 (curl calls the documented run-sync-get-dataset-items endpoint for this Actor; Python (apify-client 3.x typed Run) and JavaScript use the official apify-client call() then read the run's dataset; Multi-line shell commands continue every line with a backslash; Token read from APIFY_TOKEN, none embedded)
  • SKILL.md: 13 of 13 (SKILL.md starts with YAML front matter; name is 1-64 lowercase letters, digits and single hyphens; name matches the skill folder name; description is present, at most 1024 characters and has no angle brackets; front matter uses only spec fields; compatibility is at most 500 characters; body has instructions; field descriptions end on whole sentences; no credential values are embedded; the token is read from APIFY_TOKEN; the run command calls this Actor's run-sync endpoint; the example input is valid JSON; the example input matches the published input schema)

What the checks cover

Good jobs for this Actor

  • Build a shortlist of remote engineering jobs with company names, technical tools and application links.
  • Compare published compensation using salaryMin, salaryMax, salaryCurrency and salaryFrequency.
  • Filter searches to named employers while excluding companies or industries outside the candidate’s preferences.
  • Match roles to experience limits and inspect seniorityLevel and minYearsExperience in the results.

Prompts to try

  • Find remote software engineer jobs on Hiring.cafe that mention Python in their tech stack and publish a salary range.
  • Search Hiring.cafe for data scientist roles in London and return the company, workplace type and application link.
  • Find software engineer postings whose titles contain backend and whose tech tags include Kubernetes, then group them by company.

What a run costs

Every run pays a start fee plus a price per result. On the Free plan this Actor's start fee is $0.40 (the start event, $0.10 per GB, times its default 4 GB of memory), $0.12 on Business; results cost $0.99 per 1,000 results (pay per event). Checked 2026-11-13.

Run cost by number of results
Results in one runStartResultsRun total
10$0.40$0.010$0.41
100$0.40$0.10$0.50
1,000$0.40$0.99$1.39

Plus Apify platform usage for the run, which the caller pays. A smaller memory setting lowers the start fee if the Actor still finishes. Prices can change; the Store pricing tab is the source of truth.

MCP config

One URL works in every client: https://mcp.apify.com/?tools=fetch-actor-details,nimbryxo-studio/hiring-cafe-job-listings-and-salary-filter-scraper. It exposes this Actor as a tool, plus fetch-actor-details so the agent can read the input schema before calling it. Pick your client:

Claude Code configterminal or .mcp.json

claude mcp add --transport http hiring-cafe-job-listings-and-salary-filter-scraper "https://mcp.apify.com/?tools=fetch-actor-details,nimbryxo-studio/hiring-cafe-job-listings-and-salary-filter-scraper"

Run the command in your project folder. Add --scope user to make it available in every project. Full Claude Code setup

Tools your agent gets

Listed by Apify's MCP server 0.21.9 for this exact URL on 2026-11-12 (a tools/list call; nothing was run).

  • fetch-actor-detailsreads the input schema
  • get-actor-runchecks a run's status
  • get-dataset-itemsreads a run's results
  • get-key-value-store-recordreads a stored record such as a file or summary
  • abort-actor-runstops a run that is still going
  • nimbryxo-studio--hiring-cafe-job-listings-and-salary-filter-827druns the Actor and returns its results

n8n workflow

A manual and a daily trigger call the Actor through the HTTP Request node with your Apify token, then hand each record to the destination you pick. The Actor input sits in the request body, already filled with the example below.

Send the records to
  • Run by hand
  • Every day
  • Run Apify Actor

n8n workflowhiring-cafe-job-listings-and-salary-filter-scraper.n8n.json

Actor on Apify
{
  "name": "Hiring.cafe Job Listings & Salary Filter Scraper to n8n only",
  "nodes": [
    {
      "id": "f845ed32-8068-499c-a4e3-c5d1c098a887",
      "name": "Run by hand",
      "type": "n8n-nodes-base.manualTrigger",
      "typeVersion": 1,
      "position": [
        0,
        0
      ],
      "parameters": {}
    },
    {
      "id": "7f503772-fbb4-42ba-ae9f-93e78604648f",
      "name": "Every day",
      "type": "n8n-nodes-base.scheduleTrigger",
      "typeVersion": 1.2,
      "position": [
        0,
        200
      ],
      "parameters": {
        "rule": {
          "interval": [
            {
              "triggerAtHour": 8
            }
          ]
        }
      },
      "notes": "Activate the workflow to run on this schedule."
    },
    {
      "id": "0ef20f4e-9989-4623-aac9-92b258144013",
      "name": "Run Apify Actor",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.2,
      "position": [
        260,
        100
      ],
      "parameters": {
        "method": "POST",
        "url": "https://api.apify.com/v2/actors/nimbryxo-studio~hiring-cafe-job-listings-and-salary-filter-scraper/run-sync-get-dataset-items",
        "authentication": "genericCredentialType",
        "genericAuthType": "httpHeaderAuth",
        "sendBody": true,
        "specifyBody": "json",
        "jsonBody": "{\n  \"searchQueries\": [\n    \"software engineer\"\n  ],\n  \"workplaceTypes\": [\n    \"Remote\",\n    \"Hybrid\",\n    \"Onsite\"\n  ],\n  \"onlyTransparentSalaries\": false,\n  \"maxItems\": 3\n}",
        "options": {
          "timeout": 310000
        }
      },
      "notes": "Actor: nimbryxo-studio/hiring-cafe-job-listings-and-salary-filter-scraper. Select a Header Auth credential: name Authorization, value Bearer + your Apify token. Edit the JSON body to change the input.",
      "notesInFlow": false
    },
    {
      "id": "ff376d1a-5018-4ed6-a8ac-29b710222b3b",
      "name": "Setup",
      "type": "n8n-nodes-base.stickyNote",
      "typeVersion": 1,
      "position": [
        0,
        -370
      ],
      "parameters": {
        "content": "## Hiring.cafe Job Listings & Salary Filter Scraper\n\nSource: [nimbryxo-studio/hiring-cafe-job-listings-and-salary-filter-scraper](https://apify.com/nimbryxo-studio/hiring-cafe-job-listings-and-salary-filter-scraper) on Apify.\n\n1. In **Run Apify Actor**, create a Header Auth credential: name `Authorization`, value `Bearer YOUR_APIFY_TOKEN` with your token.\n2. Click **Execute workflow**. Each record arrives as one n8n item.\n3. Edit the JSON body of **Run Apify Actor** to change the input.\n\nGenerated by recipeforagents.com. Validated, not executed: runs are billed to your Apify account.",
        "height": 340,
        "width": 460,
        "color": 6
      }
    }
  ],
  "connections": {
    "Run by hand": {
      "main": [
        [
          {
            "node": "Run Apify Actor",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Every day": {
      "main": [
        [
          {
            "node": "Run Apify Actor",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "pinData": {},
  "active": false,
  "settings": {
    "executionOrder": "v1"
  },
  "meta": {
    "templateCredsSetupCompleted": false
  },
  "tags": []
}

Import with Workflows, Import from file, or paste into the canvas. Credentials are not included: you select them after import.

All 7 destination variants pass the same checks at build time. Built-in nodes only, at versions n8n has shipped since 1.80: they import on n8n Cloud and older self-hosted instances without community nodes. Prefer Apify's own node? The verified community node @apify/n8n-nodes-apify runs the same Actor with OAuth sign-in on n8n Cloud.

Runs longer than 5 minutes? The synchronous endpoint answers HTTP 408 after 300 seconds. The long-run variant starts the run, checks it every minute until it ends, then reads its dataset (HTTP Request, If and Stop and Error nodes only).

Download the long-run workflow11 of 11 checks pass, not executed

Call it from code

Run the Actor from a script or your own agent framework with the Apify API. The call waits for the run to finish and returns the records. The input is the example below.

curl

API docs on Apify
curl -X POST "https://api.apify.com/v2/actors/nimbryxo-studio~hiring-cafe-job-listings-and-salary-filter-scraper/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"searchQueries":["software engineer"],"workplaceTypes":["Remote","Hybrid","Onsite"],"onlyTransparentSalaries":false,"maxItems":3}'

In an agent framework

The same Actor and input in the frameworks Apify documents: as a LangChain or CrewAI tool, a LlamaIndex document loader, or through the scoped MCP URL in the OpenAI Agents SDK and Mastra. Each snippet is run against the current package before it is shown (stub API, nothing billed). Framework guides

Install: pip install langchain-apify

LangChain

# Reads APIFY_TOKEN from the environment.
from langchain_apify import ApifyActorsTool

tool = ApifyActorsTool("nimbryxo-studio/hiring-cafe-job-listings-and-salary-filter-scraper")
items = tool.invoke({"run_input": {
    "searchQueries": [
        "software engineer",
    ],
    "workplaceTypes": [
        "Remote",
        "Hybrid",
        "Onsite",
    ],
    "onlyTransparentSalaries": False,
    "maxItems": 3,
}})
print(len(items), "records", items[:1])

# Give the same tool to an agent (pip install langchain langchain-openai):
# from langchain.agents import create_agent
# agent = create_agent(ChatOpenAI(model="gpt-5.4-mini"), [tool])

Example input

These values come from the Actor's Store prefill and required defaults. Change the search, URL or limit before your first run.

Actor inputinput.json

{
  "searchQueries": [
    "software engineer"
  ],
  "workplaceTypes": [
    "Remote",
    "Hybrid",
    "Onsite"
  ],
  "onlyTransparentSalaries": false,
  "maxItems": 3
}

Input fields of the example
FieldTypeWhat it does
searchQueries array Keywords to search on hiring.cafe (e.g., 'software engineer', 'data scientist'). Empty array or empty string returns unfiltered results.
workplaceTypes array Filter by workplace type. Defaults to all three.
locations array Filter to jobs in these locations. Pass plain strings like ["San Francisco", "London", "United States"] OR objects with {label, value, countryCode, stateCode, city, lat, lng}. Empty list = global (all locations)…
onlyTransparentSalaries boolean Exclude jobs that dont publish a salary range.
maxItems integer Maximum number of jobs to return across all queries.

21 more optional fields on the Store input tab.

What your agent receives

Each run returns a list of records. The Actor publishes 32 fields, starting with id, objectID, boardToken, applyUrl.

Output fields
FieldWhat it holdsFormat
idIDtext
objectIDSearch index object IDstring
sourceATStext
boardTokenJob board tokenstring
applyUrlApplylink
titleTitletext
descriptionJob description (HTML stripped, truncated)string
coreJobTitleCanonicalized core job titlestring
categoryCategorytext
seniorityLevelSenioritytext
22 more fields
More output fields
FieldWhat it holdsFormat
roleTypeRole Typetext
commitmentCommitmenttext
workplaceTypeWorkplacetext
workplaceCountriesCountriesarray
workplaceStatesState / region namesarray
workplaceCitiesCity namesarray
latitudeLatnumber
longitudeLngnumber
salaryMinMin Salarynumber
salaryMaxMax Salarynumber
salaryCurrencyCurrencytext
salaryFrequencySalary frequency (Yearly, Hourly, etc.)string
technicalToolsToolsarray
minYearsExperienceMin YoEnumber
bachelorsDegreeRequirementBachelor's degree requirement levelstring
companyNameCompanytext
companyWebsiteCompany homepage URLstring
companyIndustriesIndustriesarray
companyEmployeesEmployee count (string since ranges used)string
companyHqCountryHQtext
isExpiredWhether the listing is expiredboolean
scrapedAtScraped Attext

Agent skill

A SKILL.md in the open Agent Skills format. It teaches Claude Code, Codex and other skill-aware agents when to call this Actor, how to build the input and how to read the result, using the API directly.

SKILL.mdhiring-cafe-job-listings-and-salary-filter-scraper/SKILL.md

---
name: hiring-cafe-job-listings-and-salary-filter-scraper
description: "Dataset of hiring.cafe job postings with title, company, workplace type, seniority, salary range, tech stack, and apply URL. Runs the Apify Actor nimbryxo-studio/hiring-cafe-job-listings-and-salary-filter-scraper. Use when the user needs Hiring.cafe Job data with fields such as id, objectID, source, boardToken, applyUrl, title and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
  actor: "nimbryxo-studio/hiring-cafe-job-listings-and-salary-filter-scraper"
  store-url: "https://apify.com/nimbryxo-studio/hiring-cafe-job-listings-and-salary-filter-scraper"
---

# Hiring.cafe Job Listings & Salary Filter Scraper

Use this skill to fetch Hiring.cafe Job data with the Apify Actor `nimbryxo-studio/hiring-cafe-job-listings-and-salary-filter-scraper` and work with the returned rows.

## Before running

1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.

## Input fields

| Field | Type | Meaning |
| --- | --- | --- |
| `searchQueries` | array | Keywords to search on hiring.cafe (e.g., 'software engineer', 'data scientist'). Empty array or empty string returns unfiltered results. |
| `workplaceTypes` | array | Filter by workplace type. Defaults to all three. |
| `locations` | array | Filter to jobs in these locations. Pass plain strings like ["San Francisco", "London", "United States"] OR objects with {label, value, countryCode, stateCode, city, lat, lng}. Empty list = global (all locations). |
| `onlyTransparentSalaries` | boolean | Exclude jobs that dont publish a salary range. |
| `maxItems` | integer | Maximum number of jobs to return across all queries. |

Example `input.json` (the Actor's published prefill):

```json
{
  "searchQueries": [
    "software engineer"
  ],
  "workplaceTypes": [
    "Remote",
    "Hybrid",
    "Onsite"
  ],
  "onlyTransparentSalaries": false,
  "maxItems": 3
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/nimbryxo-studio~hiring-cafe-job-listings-and-salary-filter-scraper/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json > results.json
```

The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/nimbryxo-studio~hiring-cafe-job-listings-and-salary-filter-scraper/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.

## Output

Each item is one record. Published fields include: `id`, `objectID`, `source`, `boardToken`, `applyUrl`, `title`, `description`, `coreJobTitle`, `category`, `seniorityLevel`, `roleType`, `commitment`, `workplaceType`, `workplaceCountries`, `workplaceStates`, `workplaceCities`, `latitude`, `longitude`, `salaryMin`, `salaryMax`.

Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.

  • Claude Code: save it as ~/.claude/skills/hiring-cafe-job-listings-and-salary-filter-scraper/SKILL.md, or .claude/skills/hiring-cafe-job-listings-and-salary-filter-scraper/SKILL.md in a project.
  • Codex and other agents: ~/.agents/skills/hiring-cafe-job-listings-and-salary-filter-scraper/SKILL.md, or .agents/skills/hiring-cafe-job-listings-and-salary-filter-scraper/ in a project.
  • Or let the skills CLI place it for your agent: npx skills add https://recipeforagents.com --skill hiring-cafe-job-listings-and-salary-filter-scraper
  • Set APIFY_TOKEN in the agent's environment.

Troubleshooting

Why does the client say Unauthorized or invalid token?

Every Apify Actor tool needs a signed-in Apify account. Reconnect the server so the OAuth sign-in runs again, or switch to the token variant: an Authorization: Bearer header with an API token from Apify Console, Settings, API and integrations. For a local server the token must be in the server's own env block, not only in your shell.

Source: Apify MCP server README. This fix on its own page

Why did my agent's tool list change after an update?

Without a tools parameter Apify's server loads its default tool set, which changes between releases. The URLs on this site pin the tools with ?tools=, so the agent always gets the same Actor tool plus fetch-actor-details. Apify's README gives the same advice for production.

Source: Apify MCP server README. This fix on its own page

What happens when the agent sends input the Actor rejects?

The server answers with the Actor's input schema, so the agent can fix the arguments and call again. The fetch-actor-details tool in every scoped URL lets it read that schema before the first call.

Source: Apify MCP server README. This fix on its own page

Questions

How can I keep only jobs with published pay?

Set onlyTransparentSalaries to true to exclude postings without a published salary range. Combine minSalary and maxSalary with salaryCurrency and salaryFrequency when applying compensation thresholds.

Can I search titles separately from descriptions and tech tags?

jobTitleQuery matches a phrase in the job title, while jobDescriptionQuery searches the description. technologyKeywordsQuery targets parsed tech tags, and requirementsKeywordsQuery targets parsed requirement bullets.

How do I connect Hiring.cafe Job Listings & Salary Filter Scraper to Claude?

In Claude Code run: claude mcp add --transport http hiring-cafe-job-listings-and-salary-filter-scraper "https://mcp.apify.com/?tools=fetch-actor-details,nimbryxo-studio/hiring-cafe-job-listings-and-salary-filter-scraper". In Claude Desktop or claude.ai add a custom connector with the URL https://mcp.apify.com/?tools=fetch-actor-details,nimbryxo-studio/hiring-cafe-job-listings-and-salary-filter-scraper and sign in to Apify. The agent then gets one tool for this Actor plus a tool that reads its input schema.

What input does Hiring.cafe Job Listings & Salary Filter Scraper need?

No field is required by the published input schema. The example on this page uses the Actor's own Store prefill, so it is a sensible first run.

What does Hiring.cafe Job Listings & Salary Filter Scraper cost to run?

The Apify Store lists $0.99 per 1,000 results (pay per event) for this Actor, checked 2026-11-13. Runs are billed to the Apify account whose token or sign-in the agent uses; Apify platform usage can add to that.

Which tools does the MCP config give my agent?

6 tools: fetch-actor-details, get-actor-run, get-dataset-items, get-key-value-store-record, abort-actor-run, nimbryxo-studio--hiring-cafe-job-listings-and-salary-filter-827d. Apify's MCP server listed them for this exact URL on 2026-11-12.

Made this Actor? Show it is listed

A small badge for your README, docs or Store page that links back here. It is a plain SVG file: no script, no tracking.

Listed on Recipe for AgentsListed on Recipe for Agents, dark version