Skip to main content
Glama
LinkedIn Jobs Feed MCP Server

LinkedIn Jobs Feed MCP Server

LinkedIn Jobs Feed MCP Server

Glama score MCP Registry npm version npm downloads license mcpservers.org

An MCP server for the Mamba Labs LinkedIn Jobs Feed actor on Apify. Give it job searches and locations. It returns one row per job from LinkedIn's public job search, with the employer's own website domain attached.

What's Inside

Related MCP server: LinkedIn Jobs MCP Server

What it does

  • Source: LinkedIn's public guest job search and job posting pages only. No login, no cookie, no profile or company page reads.

  • Employer domain: a company name autocomplete, then a web search, once per employer and cached; returned only when the domain clearly matches the company name (domain_status resolved), otherwise empty and labeled.

  • Rows: one job row per job with the posting details, and one free search row per search and location with jobs_found and jobs_returned.

  • Filters and schedules: posted within, workplace type, experience level, job type, excluded companies, and only_new with a state_key.

All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:

{
  "mcpServers": {
    "mamba-linkedin-jobs-feed": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-linkedin-jobs-feed"
      ],
      "env": {
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}

Restart the client. The search_linkedin_jobs tool appears.

Prerequisites

Example prompts

  • "Find account executive jobs posted in Germany this week and give me the hiring companies' domains."

  • "Which companies in London posted a head of sales or SDR manager job in the last 24 hours?"

  • "Every morning, list new remote RevOps jobs in the United States with the company domain."

Tool

search_linkedin_jobs. One tool. Example arguments:

{
  "keywords": [
    "account executive"
  ],
  "locations": [
    "Germany"
  ],
  "max_jobs_per_search": "5"
}

Inputs

Every buyer facing input of the actor, unchanged. Omitted inputs take the actor's own defaults. Numbers and booleans are sent as strings.

Input

Type

Description

keywords

array

One job search per line, as you would type it in LinkedIn's job search, for example account executive, or sdr manager saas. Up to 50 searches per run (keywords times locations)

locations

array

Optional. One location per line, as LinkedIn's job search takes it: a country (Germany), a city (London, England, United Kingdom), or a region (European Union). Each search runs once per location. Empty searches worldwide

posted_within

string

Only jobs posted in this window, as LinkedIn dates them

workplace_types

array

Optional. Any of: on_site, remote, hybrid

experience_levels

array

Optional. Any of: internship, entry, associate, mid_senior, director, executive

job_types

array

Optional. Any of: full_time, part_time, contract, temporary, internship, volunteer, other

max_jobs_per_search

string

Job rows returned per search, newest first. Default 100, up to 1000 (LinkedIn shows guests about 1,000 results per search)

exclude_companies

array

Optional. Drop jobs whose company name contains one of these, ignoring case, for example staffing agencies you do not want

include_details

string

true reads each job's public posting page. No extra charge

find_company_domain

string

true looks up each employer's own website domain by name with a web search, and returns it only when the domain clearly matches the name. No extra charge

only_new

string

true returns only jobs that an earlier run with the same state key did not return. The first run returns every job in the window

state_key

string

Names the saved state for only new jobs. Use one key per schedule, for example ae-germany-daily

reset_state

string

true forgets the saved state for this state key

max_charge_usd

string

Optional. The run stops before it would charge more than this

Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

Event

Free plan

Bronze

Silver

Gold

job-row, one job returned, with details and the employer domain

$0.0015

$0.001425

$0.00135

$0.001275

apify-actor-start, per run start

$0.001

$0.001

$0.001

$0.001

Search rows and the row for a refused input are free. Posting details and the domain lookup carry no extra charge.

Your keys

The actor needs no key and no LinkedIn account. It reads public job pages and a public search results page and holds no key of any kind. Mamba Labs pays the platform and proxy costs of the run.

Full actor documentation

apify.com/mambalabs/linkedin-jobs-feed

License

MIT. See LICENSE.

Available Tools

1 tool
search_linkedin_jobsSearch LinkedIn jobs with the employer domainA
Read-only

Search LinkedIn jobs by keywords and location and return one row per job with the employer's own website domain attached. Reads only LinkedIn's public guest job search and job posting pages, with no login. Each job row carries title, company, company page, location, posting date, job link, and by default the description, seniority level, employment type, job function, industries, and applicant count. The employer domain comes from a public company name autocomplete, then a web search, and is returned only when it clearly matches (domain_status resolved). Filters: posted within 24h, week, or month; workplace type; experience level; job type; excluded companies. only_new with a state_key returns only jobs earlier runs did not return. One free search row per search and location gives the counts. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges per job row returned and once per run start; search rows are free.

Inputs: keywords, only_new, job_types, locations, +10 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool there is no possibility of misselection; its purpose (keyword+location LinkedIn job search with employer domain enrichment) is stated unambiguously. An agent cannot confuse it with anything else in the set.

    Naming Consistency5/5

    The single name `search_linkedin_jobs` follows a clean snake_case verb_noun pattern with a clear platform qualifier. There is no competing convention to clash with.

    Tool Count3/5

    One tool is thin for a server, even though the tool itself is extremely feature-dense (filters, dedup state, enrichment). The scope is narrow enough that a single entry point is defensible, but it sits at the borderline of 'too few tools'.

    Completeness3/5

    Search covers a lot of ground, but the surface is a single operation: there is no fetch-by-job-id for detail refresh, no company/employer lookup tool, and no way to page or resume beyond the coarse only_new state. Agents can work around this, but the lifecycle is not fully covered.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides tools for automating LinkedIn job post search and management. Job opportunities often appear in LinkedIn posts first, before they're posted on traditional job boards. By monitoring LinkedIn posts, you can discover opportunities earlier and get a competitive advantage in your job search.
      20 npm
      7
      ISC
    • A
      license
      A
      quality
      D
      maintenance
      Enables users to search LinkedIn's public job listings with advanced filters like location, salary, and experience level. It allows MCP-compatible clients to retrieve real-time job opportunities without requiring LinkedIn authentication or API keys.
      1
      2
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables job search on LinkedIn through MCP tools, including keyword and location search, filtering by remote, easy apply, experience level, job type, and date, and retrieving job details.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Searches LinkedIn for job posts, filters out non-vacancies and out-of-market roles, and provides a local dashboard to triage and rate the remaining openings.
      1
      ISC