Skip to main content
Glama
mambalabsdev

LinkedIn Company Page Mapper MCP Server

by mambalabsdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to LinkedIn Company Page Mapper MCP Server

No user-submitted related servers found.

    Related Servers

    • Company Firmographic Enricher

      mambalabsdev
      A
      license
      A
      quality
      A
      maintenance
      Enables enriching company domains into structured firmographics including employee band, industry, HQ, founded year, revenue estimate, logo, and description, with source provenance and data completeness scoring.
      1
      82 npm
      1
      MIT

    • mcp-meta-brand-presence-mapper

      mambalabsdev
      A
      license
      A
      quality
      A
      maintenance
      Enables resolving a company domain to its Instagram, Threads, and Facebook accounts with follower and post counts.
      1
      90 npm
      MIT

    • Company Identity Resolver MCP

      mambalabsdev
      A
      license
      A
      quality
      A
      maintenance
      Resolves any combination of company name, domain, or LinkedIn URL into the canonical company identity (name, domain, LinkedIn URL) with confidence scores and match method.
      1
      66 npm
      MIT

    • LinkedIn Company API MCP

      johnisanerd
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to extract structured firmographic data from public LinkedIn company URLs, returning fields like name, industry, size, and headquarters.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no risk of selecting between overlapping operations. Its purpose—domain-to-LinkedIn-page mapping—is unmistakable.

    Naming Consistency5/5

    The single tool name uses snake_case with a clear verb_noun structure: map_linkedin_company_presence. With only one tool, consistency is trivially satisfied.

    Tool Count4/5

    A single focused tool is reasonable for this narrow read-only mapping service, but it sits below the typical 3-15 range and offers no batch or alternative operations. Not a mismatch, just slightly thin.

    Completeness4/5

    The tool covers the core domain-to-page resolution workflow, including verification and limited follower count. Batch mapping or reverse lookup would round out the surface, but no critical lifecycle operation is missing for a read-only mapper.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources