Peopledatalabs

What Peopledatalabs does

The Peopledatalabs MCP server exposes People Data Labs enrichment through the Model Context Protocol. Its two primary tools cover individual and company lookups.

pdl_person_enrich accepts at least one person identifier: an email address, LinkedIn URL, name paired with a company, or phone number. The returned profile can include job title, employer, email addresses, phone numbers, location, and skills.

pdl_company_enrich accepts a company name, website, or both. Its result can include company size, employee count, industry, founding year, location, LinkedIn URL, and website.

How it works

You can connect an MCP client to the Pipeworx pack endpoint at https://gateway.pipeworx.io/peopledatalabs/mcp. That endpoint lists the two Peopledatalabs tools along with shared Pipeworx meta-tools. The shared tools include routing and discovery functions such as ask_pipeworx, discover_tools, and search_within; the exact set is reported by the connection's initialize response and can change.

The same gateway also provides a full endpoint at https://gateway.pipeworx.io/mcp. The pack endpoint lists this pack's tools directly, while the full endpoint lists tools from the wider Pipeworx catalog. Either gateway connection can use ask_pipeworx to route a natural-language request across the catalog.

The Peopledatalabs MCP server can also run locally over stdio. In that mode, it answers MCP initialization, tool listing, and tool calls for this pack only, without the gateway's shared meta-tools or gateway round trip.

Setup and configuration

For a gateway connection, add the pack URL to the MCP client's server configuration:

{
  "mcpServers": {
    "peopledatalabs": {
      "url": "https://gateway.pipeworx.io/peopledatalabs/mcp"
    }
  }
}

For local use, configure the npm package as a stdio server:

{
  "mcpServers": {
    "peopledatalabs": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-peopledatalabs"]
    }
  }
}

Each enrichment call requires your own People Data Labs API key in the _apiKey argument. The gateway does not supply the key on your behalf.

Tools and capabilities

• pdl_person_enrich: enrich a person from an email, LinkedIn URL, phone number, or name-and-company combination.
• pdl_company_enrich: enrich a company from its name or website.
• ask_pipeworx: ask the gateway to select and call a suitable catalog tool when using a gateway connection.
• discover_tools and search_within: discover or search available gateway capabilities.

Limitations and notes

A person request must include at least one supported identifier. A company request must include a name, a website, or both. Results depend on the data returned by People Data Labs and may contain the profile fields documented for each tool rather than every possible field.

The gateway pack endpoint always includes shared Pipeworx meta-tools, so its reported tool count is larger than the two pack-specific tools. Use the standalone package if you need only the Peopledatalabs tools. HTTP tool inspection is also available through the gateway, but calling a tool still requires supplying a People Data Labs API key.

The project is distributed under the MIT license.