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. It runs locally over stdio via the published package.

People connecting social media tools to Claude, Cursor, VS Code, or another MCP client. The project is written in JavaScript.

VERIFIED ACTIVE

LAST COMMIT 2026-08-13 · ★ 2 · #15 OF 46 MAINTAINED SOCIAL MEDIA · VERIFIED 2026-08-25

MIT · JavaScript servers · how we verify → /methodology

01 · Install Domain To Linkedin Url Resolver

before you install - you'll need

APIFY_TOKEN

Environment variables documented in the project's README - it lists which are required and which have defaults.

Claude Code

claude mcp add mambalabsdev-mcp-domain-to-linkedin-url- -- npx -y @mambalabsdev/mcp-domain-to-linkedin-url-resolver

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "mambalabsdev-mcp-domain-to-linkedin-url-": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-domain-to-linkedin-url-resolver"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license MIT - declared in the repository

npm package @mambalabsdev/mcp-domain-to-linkedin-url-resolver - published under the repo owner's npm scope (@mambalabsdev)

registry vendor namespace com.mambabuilt - domain-verified with the official MCP registry

03 · What Domain To Linkedin Url Resolver can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

Latest releases

v1.0.5 · 2026-06-22

Sync release to npm 1.0.5. Refresh GTM Suite footer to full 12-actor fleet; align Official MCP Registry version.

v1.0.4 · 2026-06-02

Stable release v1.0.4. Adds MCP tool annotations (readOnlyHint, destructiveHint:false, idempotentHint, openWorldHint) and richer tool descriptions for better client/registry tool-definition quality. No change to tool…

v1.0.3 · 2026-06-02

Stable release v1.0.3 of @mambalabsdev/mcp-domain-to-linkedin-url-resolver. · Thin MCP server wrapping the Mamba Labs Apify actor; returns flat, Clay-ready JSON. Tools are listed without credentials; an Apify token is…

04 · Who maintains Domain To Linkedin Url Resolver

mcp-domain-to-linkedin-url-resolver is maintained by mambalabsdev. We track 47 MCP servers from mambalabsdev - 47 actively maintained, 11 combined GitHub stars, oldest repo from Jun 2026. Full record: all servers from mambalabsdev.

  1. mcp-job-board-keyword-signal-scanner Scans Greenhouse, Lever, Ashby, Workday, Rippling for roles in any category. Clay-ready. ★ 2
  2. mcp-icp-fit-scorer Scores a company against your ICP with weighted signals. Returns score, tier, and breakdown. ★ 2

05 · Facts

category
social media - ranked #15 of 46 actively-maintained social media servers as of 2026-08-25.
release cadence
3 releases in the last 90 days (latest 2026-06-22)
registry
com.mambabuilt/mcp-domain-to-linkedin-url-resolver (active, first published 2026-06-01 · 3 versions)
packages
npm:@mambalabsdev/mcp-domain-to-linkedin-url-resolver

06 · Domain To Linkedin Url Resolver FAQ

What is Domain To Linkedin Url Resolver?

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. It runs locally over stdio via the published package.

Is Domain To Linkedin Url Resolver still maintained?

Yes - as of 2026-08-25, its last commit was 2026-08-13 and it shipped 3 releases in the last 90 days. We re-verify nightly.

How do I install Domain To Linkedin Url Resolver?

Run `npx -y @mambalabsdev/mcp-domain-to-linkedin-url-resolver`. The README documents one environment variable (APIFY_TOKEN) to set first. You can also paste the ready-made client config above.

Does Domain To Linkedin Url Resolver run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to Domain To Linkedin Url Resolver