MCP Server

Resolve company name, domain, or LinkedIn into one canonical identity with confidence scores.

Local serverstdioGo

What is the MCP MCP server?

Resolve company name, domain, or LinkedIn into one canonical identity with confidence scores. The mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.

What it actually does

An MCP server that exposes the Mamba Labs Company Identity Resolver as a single tool. Install one package and give your MCP client a way to turn any combination of company name, domain, or LinkedIn URL into one canonical company identity tuple with confidence scores, wrapping the Mamba Labs actor on Apify and returning Clay-ready flat JSON.

Adding it to your client

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.

Its toolset

Everything the assistant can do here goes through one of these:

  • resolve_company_identity — resolve any combination of company name, domain, or LinkedIn URL into the canonical name, primary domain, and LinkedIn company URL, each with a 0-100
  • Actor — Immutable Actor ID

Configuration

You will need one environment variable: APIFY_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

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

Caveats

  • 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.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mcp mcp server does with a few real requests.

When to reach for it

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 — resolve_company_identity, 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
resolve_company_identityresolve any combination of company name, domain, or LinkedIn URL into the canonical name, primary domain, and LinkedIn company URL, each with a 0-100 confidence score plus an overall score and a match method. It cross-ch
ActorImmutable Actor ID

How to install the MCP MCP server

{
  "mcpServers": {
    "company-identity-resolver": {
      "command": "npx",
      "args": ["-y", "@mambalabsdev/mcp-company-identity-resolver"],
      "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 resolve company identity.
  • Use MCP to Actor.

Frequently asked questions

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