A
licenseNot graded
qualityD
maintenanceDomain -> company intelligence for AI agents. Look up company name, country, contacts, and social profiles from any MCP-compatible client.
6
MIT
Company Social Presence Mapper MCP Server
by mambalabsdev
This server maps a company's official social media presence across major platforms using just a domain or company name. It provides a single tool — map_company_social_presence — with the following capabilities:
Discover social media profiles across LinkedIn, X (Twitter), Instagram, Facebook, and YouTube by providing a
company_domain(e.g.,stripe.com) orcompany_nameRetrieve follower counts for discovered profiles where publicly available (Instagram and Facebook are best-effort; X/Twitter returns URL only)
Target specific platforms by selecting a subset of the five supported platforms instead of mapping all of them
Optimize for cost by setting
includeFollowerCounts: falseto retrieve URLs only, using fewer API creditsControl caching by using
skipCacheto force a fresh lookup and bypass the 7-day result cacheReturn Clay-ready flat JSON output suitable for GTM and enrichment workflows
Underlying mechanism: Profiles are discovered via homepage link scraping, web search fallback, and pattern guessing — then validated against the company before results are returned.
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., "@Company Social Presence Mapper MCP ServerMap social presence for stripe.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.
Company Social Presence Mapper MCP Server
An MCP server that exposes the Mamba Labs Company Social Presence Mapper as a single tool. Install one package and give your MCP client a way to turn a company domain into its official social media URLs and follower counts, wrapping the Mamba Labs actor on Apify and returning Clay-ready flat JSON.
What's Inside
Related MCP server: mcp-gtm-hiring-signal-scraper
What it does
This server gives an AI client one tool:
map_company_social_presence: map a company domain to its official LinkedIn, X, Instagram, Facebook, and YouTube URLs plus follower counts. Profiles are discovered from the company's own homepage links, a web search fallback, and pattern guessing, then validated against the company. Follower counts are extracted where public.
All of the work runs on Apify. This package is a thin client that routes the tool call to 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:
{
"mcpServers": {
"company-social-presence-mapper": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-company-social-presence-mapper"],
"env": {
"APIFY_TOKEN": "your-apify-token"
}
}
}
}Get your token at https://console.apify.com/account/integrations, paste it in, and restart Claude Desktop. The tool will be available.
Prerequisites
Node.js 18 or newer
An Apify account with an API token
Example prompts
"Map the social presence of stripe.com across LinkedIn, X, Instagram, Facebook, and YouTube."
"Find the official social profiles and follower counts for gitlab.com."
"What are Notion's LinkedIn and YouTube follower counts?"
"Map only the LinkedIn and X profiles for twilio.com."
Tool and inputs
map_company_social_presence:
company_domain(string): bare company domain, e.g. stripe.com. Provide this orcompany_name.company_name(string): optional company name. Improves search accuracy and disambiguation. Provide this orcompany_domain.platforms(array): which platforms to map, any oflinkedin,x,instagram,facebook,youtube. Defaults to all five.includeFollowerCounts(boolean): fetch profile pages to extract follower counts (default true). Set false for URLs only, which is cheaper.skipCache(boolean): force a fresh lookup and ignore the 7 day result cache.
Notes on coverage: X / Twitter returns the profile URL only; its follower count requires authentication, which this server does not use. Instagram and Facebook follower counts are best-effort and may be null when the page hides them.
Full actor documentation
For the complete input and output reference, pricing, and run history, see the Company Social Presence Mapper actor on the Apify Store (canonical immutable Actor ID URL):
https://apify.com/mambalabs/4k6CCemkgBDz18m2h
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 |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
|
Built by Mamba Labs | npm | Apify Store
License
MIT
Built by Mamba Labs. https://apify.com/mambalabs
Available Tools
1 toolmap_company_social_presenceMap Company Social PresenceARead-onlyIdempotent
Map a company's social media presence across LinkedIn, X, Instagram, Facebook, and YouTube. Returns profile URLs and follower counts in flat Clay-ready JSON. Profiles are discovered from the company's own homepage links, a web search fallback, and pattern guessing, then validated against the company. Follower counts are extracted where public; X is URL-only (its count needs login) and Instagram and Facebook counts are best-effort. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| company_domain | No | Bare company domain, e.g. stripe.com. Provide this or company_name. | |
| company_name | No | Optional company name. Improves search accuracy and disambiguation. Provide this or company_domain. | |
| platforms | No | Which platforms to map. Defaults to all five. | |
| includeFollowerCounts | No | Fetch profile pages to extract follower counts (default true). Set false for URLs only, which is cheaper. | |
| skipCache | No | Force a fresh lookup and ignore the 7 day result cache. |
TDQS
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description expands significantly on annotations by detailing discovery methods (homepage links, web search, pattern guessing, validation), follower count extraction limitations (X URL-only, Instagram/Facebook best-effort), and caching behavior (7-day cache, skipCache parameter). This fully discloses behavior beyond readOnlyHint and idempotentHint.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise paragraphs, front-loaded with the primary action and output. Every sentence provides value—no filler. It efficiently covers purpose, platforms, discovery, limitations, and requirements.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Despite no output schema, the description fully explains the return format ('flat Clay-ready JSON with URLs and follower counts') and all key behaviors. It addresses all five parameters, cost, caching, and fallback logic, making it complete for an AI agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With 100% schema coverage, baseline is 3. The description adds operational context: company_name improves disambiguation, includeFollowerCounts affects cost, skipCache overrides cache. This enriches parameter semantics beyond the schema descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool maps a company's social media presence across LinkedIn, X, Instagram, Facebook, and YouTube, returning profile URLs and follower counts. It specifies the exact platforms and outputs, making its purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description notes that the tool is read-only, requires an APIFY_TOKEN, and consumes credits. While no sibling tools are listed, it implicitly advises use for social presence mapping without alternatives. The caveats about X, Instagram, and Facebook counts provide usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
map_company_social_presence
TDQS
A4.5/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined, so an agent can unambiguously select it for the task of mapping social presence.
Naming Consistency5/5
The single tool name, map_company_social_presence, uses clear and descriptive snake_case. There are no other tools to compare, so no inconsistency exists.
Tool Count3/5
One tool for the domain of social presence mapping is borderline. While the tool is comprehensive, a single tool covering all platforms may be seen as too coarse. The count is acceptable but not ideal.
Completeness3/5
The tool covers the core functionality of discovering profiles and fetching follower counts, but with noted limitations (e.g., X follower count missing, Instagram and Facebook counts best-effort). For the stated purpose, it is mostly complete but has gaps.
Maintenance
ActivityMaintained
ResponsivenessNo issues
Related MCP Connectors
Company & brand data by domain or ticker/ISIN: industry, headcount, HQ, social, colors, logos.
Search social media, news, forums and Google Maps: LinkedIn, X, Reddit, TikTok, YouTube.
Company intelligence for AI agents: a five-layer domain dossier in one sniff_domain call.
Turn a company domain into a structured B2B sales brief from their public website.
Related MCP Servers
- AlicenseAqualityAmaintenanceDetects hiring intent signals by scanning job boards for specific companies. Returns structured role data for outbound sales targeting.1129 npm1MIT
- AlicenseAqualityAmaintenanceDetects a company's technology stack from its public web presence. Returns structured tech signals for sales targeting and competitive analysis.197 npm1MIT
- AlicenseAqualityAmaintenanceResolves a company domain to its LinkedIn company page URL. Lightweight enrichment tool for sales and prospecting workflows.1114 npm2MIT