MCP Server

Detect company changes across hiring, tech stack, funding, and firmographics. Returns only deltas.

Local serverstdioGo

What is the MCP MCP server?

Most developer tooling work still happens through a UI a human drives. MCP MCP server moves it into the conversation instead. Detect company changes across hiring, tech stack, funding, and firmographics. Returns only deltas.

The short version

Company Change-Event Feed monitors a company domain for changes across hiring, tech stack, funding, firmographics, and social presence, then diffs the current state against your last run and returns only what changed as typed change events. Flat, Clay-ready JSON, one row per company, built for RevOps teams, outbound agencies, Clay users, and AI agents that need delta intelligence on target accounts.

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.

The tools it exposes

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

  • get_company_changes — monitor a company domain for changes across hiring, tech stack, funding, firmographics, and social since the last run. The first run for a domain
  • 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

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.

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 — get_company_changes, 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.

Available tools

ToolWhat it does
get_company_changesmonitor a company domain for changes across hiring, tech stack, funding, firmographics, and social since the last run. The first run for a domain records a clean baseline (no changes); every run after that returns only t
ActorImmutable Actor ID

How to install the MCP MCP server

{
  "mcpServers": {
    "company-change-event-feed": {
      "command": "npx",
      "args": ["-y", "@mambalabsdev/mcp-company-change-event-feed"],
      "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 get company changes.
  • Use MCP to Actor.

Frequently asked questions

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