com.mambabuilt/mcp-person-linkedin-url-resolver

Registre officiel Marketing et ventes

Find a person's LinkedIn profile URL from name and company, with a match confidence.

Que pouvez-vous faire avec com.mambabuilt/mcp-person-linkedin-url-resolver ?

  • match_status is found at a confidence of 0.8 or more with a clear lead over every other profile, ambiguous (the likely URL), not_found, or blocked.
  • company_match says whether the company is current (headline or a present role), former (marked prev, ex, or former), or only mentioned.
  • Posts, articles, and directory pages are dropped; only /in/ profile URLs are returned.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package @mambalabsdev/mcp-person-linkedin-url-resolver
Claude Code
claude mcp add mcp-person-linkedin-url-resolver -e 'APIFY_TOKEN=<your apify_token>' -- npx -y @mambalabsdev/mcp-person-linkedin-url-resolver@1.0.0
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "mcp-person-linkedin-url-resolver": {
            "command": "npx",
            "args": [
                "-y",
                "@mambalabsdev/mcp-person-linkedin-url-resolver@1.0.0"
            ],
            "env": {
                "APIFY_TOKEN": "<your apify_token>"
            }
        }
    }
}

Variables d'environnement

  • APIFY_TOKEN obligatoire secret Apify API token from https://console.apify.com/account/integrations

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. Person LinkedIn URL Resolver MCP Server
  2. What's Inside
  3. What it does
  4. Quick start
  5. Prerequisites
  6. Example prompts
  7. Tool
  8. Inputs
  9. Pricing
  10. Your keys
  11. Full actor documentation
  12. License

Person LinkedIn URL Resolver MCP Server

Give it a person's name and company domain (or company name). Each run reads Google result pages through the Apify Google SERP proxy and returns one row per person with the LinkedIn profile URL, the headline and follower count Google shows, and a match confidence. It never opens LinkedIn and needs no LinkedIn account.

What's Inside

What it does

  • match_status is found at a confidence of 0.8 or more with a clear lead over every other profile, ambiguous (the likely URL), not_found, or blocked.
  • company_match says whether the company is current (headline or a present role), former (marked prev, ex, or former), or only mentioned.
  • Posts, articles, and directory pages are dropped; only /in/ profile URLs are returned.

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-person-linkedin-url-resolver": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-person-linkedin-url-resolver"
      ],
      "env": {
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}

Restart the client. The resolve_person_linkedin_url tool appears.

Prerequisites

Example prompts

  • "Find the LinkedIn profile of Armon Dadgar at hashicorp.com."
  • "Here are 20 names and company domains from my CRM. Find each LinkedIn URL and tell me which ones are certain."

Tool

resolve_person_linkedin_url. One tool. Example arguments:

{ "full_name": "Armon Dadgar", "company_domain": "hashicorp.com" }

Inputs

Every buyer facing input of the actor, unchanged. Omitted inputs take the actor's own defaults.

InputTypeDescription
full_namestringFirst and last name
company_domainstringThe company domain; give this or company_name
company_namestringOptional company name
job_titlestringOptional; a small boost when the headline agrees
locationstringOptional; a small boost when the snippet agrees
keywordsstringOptional extra query words
personsarrayUp to 500 lines as `Full Name \company.com \job title`
countrystringGoogle country code. Default us
allow_name_onlystringtrue searches without a company; never found
max_charge_usdstringOptional cost cap for the run

Pricing

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

EventFree planBronzeSilverGold
person-searched, per input person$0.035$0.03325$0.0315$0.02975
apify-actor-start, per run start$0.0005$0.0005$0.0005$0.0005

found, ambiguous, and not_found rows each cost one person-searched. blocked and error rows are free. The actor reads at most 2 Google result pages per person.

Your keys

The actor needs no key and holds none. Mamba Labs pays the platform costs of the run, Google SERP proxy traffic included.

Full actor documentation

apify.com/mambalabs/person-linkedin-url-resolver

License

MIT. See LICENSE.

Questions fréquentes

Qu'est-ce que com.mambabuilt/mcp-person-linkedin-url-resolver ?

Find a person's LinkedIn profile URL from name and company, with a match confidence.

Comment installer com.mambabuilt/mcp-person-linkedin-url-resolver ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add mcp-person-linkedin-url-resolver -e 'APIFY_TOKEN=<your apify_token>' -- npx -y @mambalabsdev/mcp-person-linkedin-url-resolver@1.0.0. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour com.mambabuilt/mcp-person-linkedin-url-resolver ?

Oui. Il attend APIFY_TOKEN, à renseigner dans sa configuration.

com.mambabuilt/mcp-person-linkedin-url-resolver est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient com.mambabuilt/mcp-person-linkedin-url-resolver ?

Il est publié par mambalabsdev. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.