LinkedIn Company Page Mapper MCP Server
Resolves company domains to their LinkedIn pages, providing exact follower counts and public firmographics such as industry, company size band, headquarters, founded year, and specialties.
README
LinkedIn Company Page Mapper MCP Server
MCP server for the Mamba Labs LinkedIn Company Page Mapper actor on Apify.
Resolve a company domain to its LinkedIn page with the exact follower count and public firmographics.
What it does
Resolve a company domain to its LinkedIn company page and return the EXACT follower count, plus the industry, declared company size band, headquarters, founded year and specialties that LinkedIn publishes on the public page. LinkedIn renders every digit, so unlike most social platforms these counts can be summed across a list. Everything comes from the logged out page: no login, no session cookie, no vendor. Employee lists, employee growth and post engagement are NOT reachable logged out and are not returned. A guessed slug that resolves to a different company is reported as identity_mismatch. Read only; requires an APIFY_TOKEN and consumes Apify credits per call.
Quick start
Add this to your MCP client configuration:
{
"mcpServers": {
"mamba-linkedin-company-presence-mapper": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-linkedin-company-presence-mapper"],
"env": { "APIFY_TOKEN": "your-apify-token" }
}
}
}
Prerequisites
- Node.js 18 or newer
- An Apify API token from console.apify.com/account/integrations
The actor is pay per event and consumes Apify credits per call. Pricing is on the actor page.
Example prompts
- "How many LinkedIn followers does gitlab.com have?"
- "Get the LinkedIn industry, size band and headquarters for stripe.com."
- "Rank these domains by LinkedIn follower count: notion.com, figma.com, gitlab.com."
Tool and inputs
Tool: map_linkedin_company_presence
| Input | Type | Meaning |
|---|---|---|
company_domain |
string | Bare company domain, for example shopify.com. Supply this or a handle. With a domain the actor runs full discovery; with a handle it skips straight to |
company_name |
string | Optional. Improves search accuracy and is what the identity gate checks a discovered profile against, so supplying it reduces wrong matches. |
handle |
string | Optional. The company slug from linkedin.com/company/<slug>, for example shopify. Supplying it skips discovery and goes straight to the fetch. |
includeFollowerCounts |
boolean | When "true" (default) the profile page is fetched and the counts are extracted. Set "false" to resolve the profile URL only, which is cheaper and need |
skipCache |
boolean | When "false" (default) a successful lookup is cached for seven days and reused. Set "true" to force a fresh fetch. Sent as a string for Clay compatibi |
includeFirmographics |
boolean | When "true" (default) industry, company size band, headquarters, founded year and website are parsed off the page alongside the follower count. Set "f |
Reading the output
Every row carries a per platform _status field, and it is the field to read
first. The vocabulary is the same across the whole Mamba Labs social family:
| Status | Meaning |
|---|---|
ok |
fetched and parsed, the value is there |
not_found |
we looked and there is no such profile |
not_extractable |
the profile exists and the value is not on the wire to us |
blocked |
the platform refused us, worth retrying later |
identity_mismatch |
we found a real profile and it belongs to someone else |
skipped |
you did not ask for this platform |
false and null are never interchangeable. false means we looked and the
answer is no. null means we could not look. If you filter for companies with no
presence, filter on false, because null rows are unknown rather than absent.
Full actor documentation
apify.com/mambalabs/linkedin-company-presence-mapper
Mamba Labs GTM Suite
Mamba Labs builds a fleet of GTM enrichment actors that share one flat, Clay
ready output convention, so their rows join on company_domain with no cleaning
step. Full fleet: apify.com/mambalabs
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。