LinkedIn Company Page Mapper MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| map_linkedin_company_presenceA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With exactly one tool, no selection ambiguity exists. The tool's name and description clearly define it as a single-purpose LinkedIn company page lookup.
The single tool uses descriptive snake_case with a clear verb-object pattern that matches the server's stated purpose, so the naming is coherent and unsurprising.
One tool is slightly narrower than a typical MCP server, but it is substantive and fully aligned with the server's declared purpose. The count feels minimal rather than bloated or trivial.
The tool covers the logged-out LinkedIn page mapping surface well, returning the key company fields and explicitly documenting unavailable data types. It is not fully complete because there is no batch or multi-domain mapping capability.