MCP Server

Scans Greenhouse, Lever, Ashby, Workday, Rippling for roles in any category. Clay-ready.

Local serverstdioGo

What is the MCP MCP server?

Scans Greenhouse, Lever, Ashby, Workday, Rippling for roles in any category. Clay-ready. That is what the mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

An MCP server that scans a company's job board for the roles you care about. It wraps the Mamba Labs Job Board Keyword Signal Scanner actor on Apify and returns a Clay-ready flat JSON row to any MCP client.

The tools it exposes

The server publishes 3 tools. What each one is for:

  • User — defined keyword arrays for custom scanning
  • Per — category counts via roles_by_category, with category-level signal scoring
  • Actor — Immutable Actor ID

What it needs from you

Configuration is passed through the environment: APIFY_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Node.js 18 or newer - An Apify account with an API token

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP's toolset — User, Per, Actor — is a fair guide to whether it matches your workflow. It is maintained by com.mambabuilt; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
Userdefined keyword arrays for custom scanning
Percategory counts via roles_by_category, with category-level signal scoring
ActorImmutable Actor ID

How to install the MCP MCP server

{
  "mcpServers": {
    "mamba-job-board-scanner": {
      "command": "npx",
      "args": ["-y", "@mambalabsdev/mcp-job-board-keyword-signal-scanner"],
      "env": {
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

  • Node.js 18 or newer - An Apify account with an API token
VariableDescriptionRequired
APIFY_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use MCP to User.
  • Use MCP to Per.
  • Use MCP to Actor.

Frequently asked questions

It connects MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (User, Per, Actor) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP directly.