mambalabsdev/mcp-job-change-tracker

An MCP server for the Mamba Labs Job Change Tracker actor on Apify. Send the contacts in your CRM. Get one row back per person: where they work now, their title, when they started, their role history, and whether they left the company you know them at, landed somewhere new, or moved up inside the same company. Every row says how the person was matched, which source the answer came from, and how old that source is.
## What's Inside
What it does
Quick start
Prerequisites
Example prompts
Tool
Inputs
Pricing
Your keys
Full actor documentation
License
## What it does
Check whether one contact, or a list of contacts, still works at the company your records hold. Returns one flat, Clay-ready JSON row per person: current employer, title, start month, role history, status (left, landed, promoted, or still there), how the person was matched, the source of the answer, and that source's date, with a namesake check. Runs on data you send (knownhistory) and on your own Serper or SerpApi, Prospeo, and BounceBan keys passed as inputs; this tool never fetches LinkedIn and holds no key of its own. Provide personname with companydomain or companyname, or a people list. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFYTOKEN and consumes Apify credits per call.
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 (claudedesktopconfig.json), Cursor, or any MCP client:
json
"mcpServers": {
"mamba-job-change-tracker": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-job-change-tracker"
],
"env": {
"APIFYTOKEN": "your-apify-token"
Restart the client. The trackjobchange tool appears.
## Prerequisites
Node.js 18 or newer.
An Apify API token from console.apify.com/account/integrations, set as APIFYTOKEN. The server lists its tool without a token; a call needs one.
## Example prompts
"Check whether Jane Doe still works at example.com and where she went if she left."
"Run these 20 contacts and tell me who changed jobs in the last 6 months."
## Tool
trackjobchange. One tool. Example arguments:
json
"personname": "Jane Doe",
"companydomain": "example.com",
"companyname": "Example Inc"
## Inputs
Every buyer facing input of the live actor, unchanged. Omitted inputs take the actor's own defaults.
| Input | Type | Required | Description |
| personname | string | no | Full name of the person to check. |
| companydomain | string | no | Website domain of the company your records place this person at, for example microsoft.com. Left, landed, and promoted are worked out against this company. |
| companyname | string | no | Name of that company. Used with or instead of the domain to match roles in the person's history. |
| lastknowntitle | string | no | The title your records hold. Echoed on the row as inputtitle. |
| profileurl | string | no | Optional. The person's LinkedIn profile URL, used as the identity. This actor never opens it. Without it, the run looks the profile up with your search key and charges profileresolved when it finds and accepts one. |