MCP server for Domain to LinkedIn URL Resolver. Resolves a company domain or name to its LinkedIn company URL with confidence scoring and firmographics via Apify. Clay-ready output.
Setup
Choose your client, copy the config, then fill in any required environment variables.
claude mcp add domain-to-linkedin-url-resolver --env APIFY_TOKEN='<APIFY_TOKEN>' -- npx -y @mambalabsdev/mcp-domain-to-linkedin-url-resolver~/.codex/config.toml
[mcp_servers.domain-to-linkedin-url-resolver]
command = "npx"
args = ["-y", "@mambalabsdev/mcp-domain-to-linkedin-url-resolver"]
env = { APIFY_TOKEN = "<APIFY_TOKEN>" }
# codex mcp add domain-to-linkedin-url-resolver --env APIFY_TOKEN='<APIFY_TOKEN>' -- npx -y @mambalabsdev/mcp-domain-to-linkedin-url-resolver~/.cursor/mcp.json
{
"mcpServers": {
"domain-to-linkedin-url-resolver": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-domain-to-linkedin-url-resolver"
],
"env": {
"APIFY_TOKEN": "<APIFY_TOKEN>"
}
}
}
}.vscode/mcp.json
{
"servers": {
"domain-to-linkedin-url-resolver": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-domain-to-linkedin-url-resolver"
],
"env": {
"APIFY_TOKEN": "<APIFY_TOKEN>"
}
}
}
}~/.gemini/settings.json
{
"mcpServers": {
"domain-to-linkedin-url-resolver": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-domain-to-linkedin-url-resolver"
],
"env": {
"APIFY_TOKEN": "<APIFY_TOKEN>"
}
}
}
}claude_desktop_config.json
{
"mcpServers": {
"domain-to-linkedin-url-resolver": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-domain-to-linkedin-url-resolver"
],
"env": {
"APIFY_TOKEN": "<APIFY_TOKEN>"
}
}
}
}.trae/mcp.json
{
"mcpServers": {
"domain-to-linkedin-url-resolver": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-domain-to-linkedin-url-resolver"
],
"env": {
"APIFY_TOKEN": "<APIFY_TOKEN>"
}
}
}
}Environment variables
APIFY_TOKEN
Replace the placeholders with your own credentials and keep them out of version control.