ATS Job Listings (Apify) by Dataset Works

dev.datasetworksPublished by datasetworks.devv1.0.0Updated Nov 17, 2026

Open jobs at any company from Greenhouse, Lever, Ashby, Personio and Recruitee boards.

The publisher's own server: Apify MCP Server

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Remote Apify-hosted MCP server that lets an assistant look up open job postings at companies using Greenhouse, Lever, Ashby, Personio or Recruitee boards.

What you can do
  • Retrieve open job listings for a company from its applicant tracking system board
  • Cover boards hosted on Greenhouse, Lever, Ashby, Personio and Recruitee
  • Surface hiring data for research or comparison across companies
When to use it
Useful when you want an assistant to pull current job openings for a specific company, or to compare hiring activity across companies that use these ATS platforms, without scraping the boards yourself.
Requirements
A remote MCP endpoint at mcp.apify.com over streamable HTTP. Authentication is required: either an Apify API token sent in the Authorization header as a Bearer token, or an OAuth sign-in to Apify when the header is left unset. An Apify account is implied.
Before you install
The connection is authenticated with an Apify credential; the Authorization header carries an API token, so treat it as a secret. Usage runs through Apify, which may involve account quotas or billing. Job data comes from third-party boards and may be incomplete or out of date.

Installation

In SourceWeft

  1. Open ATS Job Listings (Apify) by Dataset Works in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.datasetworks%2Fcompany-jobs/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "ats-job-listings-apify-by-dataset-works": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=datasetworks/company-jobs"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 17, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Apify integrations