Domain To Linkedin Url Resolver

MCP其他

提供方 mambalabsdev

其他 未标注 会话登录 社区 / 第三方 CursorCodexZed

Turns a company domain or name into its LinkedIn company URL with a confidence score, headcount, industry, and HQ. Part of the Mamba Labs signal toolkit.

一句话选型结论

按资料字段整理

Domain To Linkedin Url Resolver 属于其他类 MCP 服务器,传输方式未标注,会话登录,可直接接入 Cursor、Codex、Zed,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类其他 传输方式未标注 鉴权会话登录 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

其他
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

linkedin enrichment firmographics clay apify

支持客户端

适用场景

linkedinenrichmentfirmographics

安装与配置

未标注 会话登录
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
接入外部数据

把外部系统的数据接进对话。

自动化重复操作

把固定步骤交给模型跑。

补充工具能力

给模型补上它原本没有的能力。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Cursor、Codex、Zed,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在其他场景里让模型直接调用外部能力的人。
  • 已经在用 Cursor、Codex 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Domain To Linkedin Url Resolver当前 未标注 未标注 未标注 无 未标注
gemini-cli 未标注 stdio · 本地进程 本地部署 有 2026-04-13
ext-apps 未标注 stdio · 本地进程 本地部署 有 2026-04-19
northcinder 未标注 stdio · 本地进程 本地部署 有 2026-08-23
fastctx 未标注 stdio · 本地进程 本地部署 有 2026-08-23
quickstart-resources 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

其他
字段来自项目仓库与公开索引,中文说明由本站标注
提供方mambalabsdev上游标注的维护方 mambalabsdev
分类其他本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式会话登录远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Cross-platform本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

6.4 KB
来自项目仓库与上游目录的原文,未做删改

Domain to LinkedIn URL Resolver MCP Server

An MCP server that resolves a company domain or name to its LinkedIn company URL. It wraps the Mamba Labs Domain to LinkedIn URL Resolver actor on Apify and returns a Clay-ready flat JSON row to any MCP client.

What's Inside

  • What it does
  • Quick start
  • Prerequisites
  • Example prompts
  • Inputs
  • Output
  • Example output
  • Features
  • Pricing
  • Full actor documentation
  • Mamba Labs GTM Suite
  • License

What it does

Give it a company domain or a company name and it finds the matching LinkedIn company URL in public search results (it never requests a page on LinkedIn), with a confidence of high, medium, or low so you know how much to trust it, plus the company's Facebook, Instagram, X, and YouTube links, all in one flat row. Firmographics (employee count, industry, headquarters, follower count, description) are read from search result snippets when you set includeFirmographics to true; they are off by default and null when off or when no snippet states them. Pass domains to resolve a list in one call ready for Clay, a CRM, or an AI agent workflow. All of the resolution runs on Apify. This package is a thin client that calls the actor and hands back the result.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config:```json
{
"mcpServers": {
"mamba-linkedin-resolver": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-domain-to-linkedin-url-resolver"],
"env": {
"APIFY_TOKEN": "your-apify-token"
}
}
}
}


Get your token at https://console.apify.com/account/integrations, paste it in, and restart Claude Desktop. The `resolve_linkedin_url` tool will be available.

## Prerequisites

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

## Example prompts

- "Find the LinkedIn page for stripe.com."
- "What is the LinkedIn company URL for openai.com? Include the confidence score."
- "Resolve the company named Figma to its LinkedIn URL and firmographics."
- "Get the LinkedIn URL, employee count, and industry for datadoghq.com, with firmographics on."
- "Resolve the LinkedIn pages for stripe.com, notion.so, and figma.com."

## Inputs

- `company_domain` (optional): the bare company domain, no `https://` and no trailing slash. Example: `stripe.com`
- `company_name` (optional): the company name.
- `domains` (optional, array): a list of bare domains resolved in one run, one row per domain.
- `batchSize` (optional, integer): how many domains from the list are resolved at once. 1 to 10. Default 2.
- `includeFirmographics` (optional, boolean): also read `employee_count_approx`, `industry`, `hq_location`, `follower_count`, and `company_description` from search result snippets. No request is sent to LinkedIn. Default false. Those fields are null when it is off or when no snippet states them. The string forms `"true"` and `"false"` are accepted too.
- `skipCache` (optional, boolean): ignore the 7 day cache and resolve again. Default false. The string forms are accepted too.

Provide at least one of `company_domain`, `company_name`, or `domains`. If a domain and a name are both given, the domain takes priority.

## Output

The tool returns the actor's flat JSON row per company: `company_domain`, `company_name`, `linkedin_company_url`, `linkedin_slug`, `resolution_method`, `confidence` (high, medium, or low), `facebook_url`, `instagram_url`, `twitter_url`, `youtube_url`, the firmographic fields `employee_count_approx`, `industry`, `hq_location`, `follower_count`, and `company_description` (null unless `includeFirmographics` is true), `slug_mismatch`, `run_date`, `degraded`, and `degradation_reason`.

## Example output

Run with `includeFirmographics` set to true.```json
{
  "company_domain": "linear.app",
  "company_name": "Linear",
  "linkedin_company_url": "https://www.linkedin.com/company/linear-app",
  "linkedin_slug": "linear-app",
  "resolution_method": "google_search",
  "confidence": "high",
  "industry": "Software Development",
  "employee_count_approx": "201",
  "hq_location": "San Francisco, California, United States",
  "run_date": "2026-05-28"
}

Features

  • Public search results (Brave, then Bing) checked against the slug variants the domain implies. No request is sent to linkedin.com
  • Fixes the LinkedIn URL gaps in Clay native enrichment
  • Confidence scoring (high, medium, low) and resolution_method
  • Social links on every row; firmographics (employee count, industry, HQ) when includeFirmographics is true
  • One domain or a list per call

Pricing

Domain to LinkedIn URL Resolver is pay per event on Apify.

Event Price Fires when
apify-actor-start $0.00005 Once per run, on start, one event per GB of memory (minimum one). Apify's start event.
apify-default-dataset-item $0.006 (FREE tier), down to $0.0051 on GOLD and above Once per row written to the dataset.
max_charge_usd number Optional cost cap in USD for this run. The actor stops before an item that could take its charges past this amount.

The tool starts the actor run and polls it to a finished status, so a long run is not cut off at 300 seconds. A run that does not succeed comes back as an error with its run ID and status.

Full actor documentation

This server is a thin client and holds no resolution logic. For the complete input and output reference, pricing, and run history, see the Apify Store page:

https://apify.com/mambalabs/domain-to-linkedin-url-resolver


Mamba Labs GTM Suite

This server is part of the Mamba Labs GTM Suite, a fleet of twelve specialized MCP servers for go-to-market signal intelligence, each backed by a dedicated Apify actor.

Actor Immutable Actor ID
GTM Hiring Signal Scraper D7O1SA2EqwHGsGr1P
GTM Tech Stack Signal Enrichment qyd7nNyqFPelQViBx
GTM Signals Aggregator xKdRfnfFNkdMpFuNs
Job Board Keyword Signal Scanner 4DvqpvhMR74NLcDDY
Domain to LinkedIn URL Resolver 3HtnSaqPHOg1Qg5gx
ICP Fit Scorer W161DT8W4kW55dMFh
Domain Deliverability Checker 0tVgxI7A6o9jMlxmc
Company Firmographic Enricher YlUtLWjfPpqykmB8g
Company Social Presence Mapper 4k6CCemkgBDz18m2h
Company Identity Resolver lr8fTRAmZCBZmuwwh
Company Change-Event Feed oX44rS0fkEJ3rXLWe
Funding & Press Signal Scanner FS13X6dhQVgX3XOM6

> Built by Mamba Labs · npm · Apify Store

License

MIT

Built by Mamba Labs. https://apify.com/mambalabs

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Domain To Linkedin Url Resolver 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Domain To Linkedin Url Resolver 怎么在 Cursor、Codex、Zed 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Domain To Linkedin Url Resolver 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Domain To Linkedin Url Resolver 需要 API Key 吗?

资料标注需要会话登录认证,使用前准备好对应凭据,并按最小权限配置。

Domain To Linkedin Url Resolver 支持哪些客户端?

资料标注支持 Cursor、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Domain To Linkedin Url Resolver 能提供哪些能力?

资料显示能力标签包括 linkedin、enrichment、firmographics、clay、apify。具体工具清单以官方文档为准。

Domain To Linkedin Url Resolver 需要什么运行环境?

运行时为 Cross-platform。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。