Person LinkedIn URL Resolver MCP Server
Resolve a person’s LinkedIn profile URL from a name plus company domain or company name, using Google result pages through Apify without opening LinkedIn.
Look up one person or batch up to 500 people with
resolve_person_linkedin_url.Return LinkedIn profile URLs only from
/in/pages, filtering out posts, articles, and directories.Provide match details:
linkedin_url,match_status(found,ambiguous,not_found,blocked), confidence, name match, company match (current,former,mentioned,none), headline, snippet, follower count, and runner-up.Accept optional inputs such as job title, location, keywords, country code, name-only search, and a max charge cap.
Run read-only searches through an Apify actor, requiring an
APIFY_TOKEN, with billing per person searched on Apify.
Allows resolving LinkedIn profile URLs by searching Google result pages through an Apify Google SERP proxy, returning profile URL, headline, follower count, and match confidence for each person.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Person LinkedIn URL Resolver MCP Server Find the LinkedIn profile of Armon Dadgar at hashicorp.com"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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
Related MCP server: LinkedIn MCP Server
What it does
match_statusisfoundat a confidence of 0.8 or more with a clear lead over every other profile,ambiguous(the likely URL),not_found, orblocked.company_matchsays whether the company iscurrent(headline or a present role),former(marked prev, ex, or former), or onlymentioned.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
Node.js 18 or newer.
An Apify API token from console.apify.com/account/integrations, set as
APIFY_TOKEN. The server lists its tool without a token; a call needs one.
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 |
| string | First and last name |
| string | The company domain; give this or |
| string | Optional company name |
| string | Optional; a small boost when the headline agrees |
| string | Optional; a small boost when the snippet agrees |
| string | Optional extra query words |
| array | Up to 500 lines as |
| string | Google country code. Default us |
| string | true searches without a company; never |
| 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 |
| $0.035 | $0.03325 | $0.0315 | $0.02975 |
| $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 toolresolve_person_linkedin_urlResolve a person's LinkedIn URLARead-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
Scored across 1 tool
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.
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.
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.
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
Related MCP Connectors
Company employee lists from LinkedIn public pages, by job title and city, via a hosted MCP server.
Public LinkedIn profiles as JSON: headline, company, experience, and education, via hosted MCP.
Search people and companies, enrich profiles, and find email and phone over MCP.
Real-time B2B professional profiles, company intelligence & jobs hosted MCP. OAuth or API key.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceAn innovative MCP server that transforms LinkedIn API interactions, enabling advanced people search, profile retrieval, and job market intelligence through natural language.135 npmMIT
- AlicenseAqualityDmaintenanceEnables searching and scraping of LinkedIn profiles, companies, jobs, and posts using natural language through MCP-compatible AI clients.13MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI-powered LinkedIn content creation, profile and company analytics, lead generation, and connection request automation through MCP tools.-
- AlicenseAqualityCmaintenanceEnables 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.5MIT