LinkedIn Data MCP

1. Open Customize → Connectors → + → Add custom connector, or use this direct link.
2. Enter these values, then click Add:
   • Name: EnvoAPI
   • Remote MCP server URL: https://api.envoapi.com/mcp
3. Claude sends you to EnvoAPI. Sign in and approve the connector.
4. In a chat, open + → Connectors and switch EnvoAPI on.

Connectors you add on the web also appear in the desktop and mobile apps. On Team and Enterprise plans, an owner may need to add the connector for the organization first.

Use this only if you can't use the connector flow above. It needs Node.js 18+, because Claude Desktop reaches the server through the mcp-remote bridge.

Open Settings → Developer → Edit Config and add:

{
  "mcpServers": {
    "envoapi": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.envoapi.com/mcp",
        "--header",
        "Authorization:${ENVO_AUTH_HEADER}"
      ],
      "env": {
        "ENVO_AUTH_HEADER": "Bearer YOUR_ENVO_API_KEY"
      }
    }
  }
}

The config file lives at ~/Library/Application Support/Claude/claude_desktop_config.json on macOS and %APPDATA%\Claude\claude_desktop_config.json on Windows. Restart Claude Desktop afterwards.

1. Turn on developer mode once per account: Settings → Security and login → Developer mode. The Create MCP App option stays hidden until you do.
2. Open ChatGPT plugins and choose Add → Create MCP App.
3. Fill in the form:
   • Name: EnvoAPI
   • Connection: https://api.envoapi.com/mcp
   • Authentication: OAuth
4. Tick I understand and want to continue, then click Create.
5. Sign in to EnvoAPI, approve access, and enable EnvoAPI in your conversation.

Custom remote connectors are available on Perplexity's paid plans, on web and desktop.

1. Open Settings → Connectors and click + Custom connector, then choose Remote.
2. Fill in the form:
   • Name: EnvoAPI
   • MCP server URL: https://api.envoapi.com/mcp
   • Authentication: OAuth
   • Transport: Streamable HTTP
3. Accept the notice and save. Then click the EnvoAPI card to sign in and approve.
4. In a thread, open + → Connectors and sources and tick EnvoAPI.

On Enterprise, an admin may need to turn on Allow members to add custom connectors first.

claude mcp add --transport http envoapi https://api.envoapi.com/mcp

Start Claude Code, run /mcp, select envoapi and approve in your browser. Check it with claude mcp list. The tools appear as mcp__envoapi__*.

With an API key:

claude mcp add --transport http envoapi https://api.envoapi.com/mcp \
  --header "Authorization: Bearer $ENVO_API_KEY"

Add --scope user to make EnvoAPI available in every project.

codex mcp add envoapi --url https://api.envoapi.com/mcp
codex mcp login envoapi

Approve in the browser, then run /mcp in Codex to check the connection.

With an API key, add this to ~/.codex/config.toml and export ENVO_API_KEY in your shell:

[mcp_servers.envoapi]
url = "https://api.envoapi.com/mcp"
bearer_token_env_var = "ENVO_API_KEY"

gemini mcp add --transport http envoapi https://api.envoapi.com/mcp

Then, inside Gemini CLI, run /mcp auth envoapi to sign in.

With an API key, use ~/.gemini/settings.json:

{
  "mcpServers": {
    "envoapi": {
      "httpUrl": "https://api.envoapi.com/mcp",
      "headers": {
        "Authorization": "Bearer $ENVO_API_KEY"
      }
    }
  }
}

Add this to opencode.json in your project, or to ~/.config/opencode/opencode.json for all projects:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "envoapi": {
      "type": "remote",
      "url": "https://api.envoapi.com/mcp",
      "enabled": true
    }
  }
}

Sign-in opens on the first tool call. If it doesn't, run opencode mcp auth envoapi, then check with opencode mcp list.

With an API key, add "headers": { "Authorization": "Bearer {env:ENVO_API_KEY}" } to the envoapi entry.

Click to install, or merge this into ~/.cursor/mcp.json (global) or .cursor/mcp.json (project):

{
  "mcpServers": {
    "envoapi": {
      "url": "https://api.envoapi.com/mcp"
    }
  }
}

Enable envoapi in Cursor's MCP settings and sign in when prompted.

With an API key:

{
  "mcpServers": {
    "envoapi": {
      "url": "https://api.envoapi.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:ENVO_API_KEY}"
      }
    }
  }
}

Click to install, run

code --add-mcp '{"name":"envoapi","type":"http","url":"https://api.envoapi.com/mcp"}'

or merge this into .vscode/mcp.json:

{
  "servers": {
    "envoapi": {
      "type": "http",
      "url": "https://api.envoapi.com/mcp"
    }
  }
}

Run MCP: List Servers from the Command Palette, start envoapi and sign in.

With an API key. VS Code prompts for the key once and stores it securely:

{
  "inputs": [
    { "type": "promptString", "id": "envo-api-key", "description": "EnvoAPI API key", "password": true }
  ],
  "servers": {
    "envoapi": {
      "type": "http",
      "url": "https://api.envoapi.com/mcp",
      "headers": { "Authorization": "Bearer ${input:envo-api-key}" }
    }
  }
}

Add this to ~/.codeium/windsurf/mcp_config.json, then click Refresh in the MCP panel:

{
  "mcpServers": {
    "envoapi": {
      "serverUrl": "https://api.envoapi.com/mcp"
    }
  }
}

With an API key, add "headers": { "Authorization": "Bearer ${env:ENVO_API_KEY}" } next to serverUrl.

Add this to your Zed settings.json. Zed starts the OAuth sign-in when no Authorization header is set:

{
  "context_servers": {
    "envoapi": {
      "url": "https://api.envoapi.com/mcp"
    }
  }
}

With an API key, add "headers": { "Authorization": "Bearer YOUR_ENVO_API_KEY" }.

Open Cline's MCP Servers panel, choose Configure MCP Servers and add:

{
  "mcpServers": {
    "envoapi": {
      "type": "streamableHttp",
      "url": "https://api.envoapi.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ENVO_API_KEY"
      }
    }
  }
}

Open the Program tab in the right sidebar, choose Install → Edit mcp.json and add:

{
  "mcpServers": {
    "envoapi": {
      "url": "https://api.envoapi.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ENVO_API_KEY"
      }
    }
  }
}

1. In your AI Agent node, add the tool MCP Client Tool.
2. Set Endpoint to https://api.envoapi.com/mcp and Server Transport to HTTP Streamable.
3. Set Authentication to Bearer Auth and create a credential with your EnvoAPI API key.
4. Under Tools to Include, pick All or just the tools your workflow needs.

Add https://api.envoapi.com/mcp as a remote server over Streamable HTTP.

• If the client supports OAuth, leave auth empty and it will open the EnvoAPI sign-in.
• If it doesn't, send the header Authorization: Bearer <ENVO_API_KEY>.
• For a client that only supports local (stdio) servers, bridge it with npx -y mcp-remote https://api.envoapi.com/mcp --header "Authorization:Bearer <ENVO_API_KEY>".

They return the same data at the same prices. MCP suits lookups from chat and editors. The REST API and the SDKs for Python, TypeScript and Go suit scheduled jobs, bulk work and product code. For a side-by-side guide, read MCP vs REST API for B2B data enrichment.

No. EnvoAPI is an independent service that returns public LinkedIn data. You sign in to EnvoAPI, not to LinkedIn, so you never connect your own LinkedIn account. Read LinkedIn API: official vs unofficial to see how the options compare.

No. OAuth clients only need an EnvoAPI account. You sign in once and approve. The API key is for clients that can't do OAuth.

It works on company domains. Yahoo-family addresses can't be checked, so those calls are refunded. Catch-all domains are charged but return no address.

No. All 40 tools are read-only.