Skip to main content
Glama
Person LinkedIn URL Resolver MCP Server

Person LinkedIn URL Resolver MCP Server

Person LinkedIn URL Resolver MCP Server

Glama score MCP Registry npm version npm downloads license mcpservers.org

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

Related MCP server: LinkedIn MCP Server

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.

Input

Type

Description

full_name

string

First and last name

company_domain

string

The company domain; give this or company_name

company_name

string

Optional company name

job_title

string

Optional; a small boost when the headline agrees

location

string

Optional; a small boost when the snippet agrees

keywords

string

Optional extra query words

persons

array

Up to 500 lines as Full Name | company.com | job title

country

string

Google country code. Default us

allow_name_only

string

true searches without a company; never found

max_charge_usd

string

Optional cost cap for the run

Pricing

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

Event

Free plan

Bronze

Silver

Gold

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.

Available Tools

1 tool
resolve_person_linkedin_urlResolve a person's LinkedIn URLA
Read-only

Find a person's LinkedIn profile URL from their name and company domain or company name, read from Google result pages through the Apify Google SERP proxy; LinkedIn itself is never opened. Returns one row per person with linkedin_url, match_status (found at a confidence of 0.8 or more with a clear lead over any other profile, ambiguous with the likely URL, not_found, or blocked), match_confidence from 0 to 1, name_match, company_match (current, former, mentioned, none), the headline, snippet, and follower count Google shows, and the runner up. Batch up to 500 persons in persons. A run that does not succeed is returned as an error with its run ID. Read-only; requires an APIFY_TOKEN; Apify charges one event per person searched (found, ambiguous, or not found); blocked and error rows are free.

Inputs: country, persons, keywords, location, +6 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is no possibility of misselection or overlap with a sibling. Its purpose is stated precisely (name + company → LinkedIn URL via Google SERP), leaving no ambiguity about what it does or does not do.

    Naming Consistency5/5

    The single name resolve_person_linkedin_url follows a clear verb_object convention in snake_case. Nothing else exists to break the pattern, and the name is fully self-describing.

    Tool Count3/5

    The server's scope is deliberately narrow (one resolution operation), so a single tool is defensible and it absorbs volume via the 500-person batch parameter. Still, a one-tool surface is thin, and the run-ID error path hints at lifecycle operations that were folded into the blob rather than exposed as tools.

    Completeness4/5

    The single tool covers the core workflow end to end: batch input, structured output with confidence, match status, matched components, and runner-up, plus explicit blocked/error semantics. The notable gap is that failures return a run ID with no companion tool to retrieve or retry that run, which an agent cannot work around from this surface alone.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An innovative MCP server that transforms LinkedIn API interactions, enabling advanced people search, profile retrieval, and job market intelligence through natural language.
      135 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables searching and scraping of LinkedIn profiles, companies, jobs, and posts using natural language through MCP-compatible AI clients.
      13
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP-capable agents to read and update a LinkedIn profile, check and publish posts through the official LinkedIn API. Includes a built-in quality gate that blocks drafts reading as machine-generated before anything reaches the public feed.
      5
      MIT