How to integrate Peopledatalabs MCP with LangChain

This guide walks you through connecting Peopledatalabs to LangChain using the Composio tool router. By the end, you'll have a working Peopledatalabs agent that can enrich this email with full person profile, standardize and clean this company name, get detailed info for the skill 'python' through natural language commands. This guide will help you understand how to give your LangChain agent real control over a Peopledatalabs account through Composio's Peopledatalabs MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Peopledatalabs logoPeopledatalabs
Api Key

Peopledatalabs delivers B2B data enrichment and identity resolution APIs. Supercharge your apps with accurate, up-to-date business and contact data.

24 Tools

Introduction

This guide walks you through connecting Peopledatalabs to LangChain using the Composio tool router. By the end, you'll have a working Peopledatalabs agent that can enrich this email with full person profile, standardize and clean this company name, get detailed info for the skill 'python' through natural language commands.

This guide will help you understand how to give your LangChain agent real control over a Peopledatalabs account through Composio's Peopledatalabs MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Peopledatalabs with

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Connect your Peopledatalabs project to Composio
  • Create a Tool Router MCP session for Peopledatalabs
  • Initialize an MCP client and retrieve Peopledatalabs tools
  • Build a LangChain agent that can interact with Peopledatalabs
  • Set up an interactive chat interface for testing

What is LangChain?

LangChain is a framework for developing applications powered by language models. It provides tools and abstractions for building agents that can reason, use tools, and maintain conversation context.

Key features include:

  • Agent Framework: Build agents that can use tools and make decisions
  • MCP Integration: Connect to external services through Model Context Protocol adapters
  • Memory Management: Maintain conversation history across interactions
  • Multi-Provider Support: Works with OpenAI, Anthropic, and other LLM providers

What is the Peopledatalabs MCP server, and what's possible with it?

The Peopledatalabs MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Peopledatalabs account. It provides structured and secure access to rich B2B data, so your agent can enrich profiles, standardize company details, validate customer information, and perform advanced searches with ease.

  • Comprehensive person data enrichment: Automatically enhance individual profiles using identifiers like email, phone, or full name combined with company or location data.
  • Company data validation and enrichment: Instantly verify and enrich company details with firmographics, employee counts, and standardized fields to power your workflows.
  • Advanced person search and filtering: Leverage Elasticsearch-powered queries to find the exact professional profiles you need using job title, skills, experience, and more.
  • Data cleaning and standardization: Cleanse and structure raw company, school, or location data to maintain high-quality records in your systems.
  • Skill and job title enrichment: Provide context and standardized information for job titles or professional skills to improve analytics and targeting.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS
1

Prerequisites

Before starting this tutorial, make sure you have:
  • Python 3.10 or higher installed on your system
  • A Composio account with an API key
  • An OpenAI API key
  • Basic familiarity with Python and async programming
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

npm install @composio/langchain @langchain/core @langchain/openai @langchain/mcp-adapters dotenv

Install the required packages for LangChain with MCP support.

What's happening:

  • @composio/langchain provides Composio integration for LangChain
  • @langchain/mcp-adapters enables MCP client connections
  • @langchain/core is the core agent framework
  • dotenv/config loads environment variables
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_composio_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio's API
  • COMPOSIO_USER_ID identifies the user for session management
  • OPENAI_API_KEY enables access to OpenAI's language models
5

Import dependencies

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

dotenv.config();
What's happening:
  • We're importing LangChain's MCP adapter and Composio SDK
  • The dotenv/config import loads environment variables from your .env file
  • This setup prepares the foundation for connecting LangChain with Peopledatalabs functionality through MCP
6

Initialize Composio client

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });
What's happening:
  • We're loading the COMPOSIO_API_KEY from environment variables and validating it exists
  • Creating a Composio instance that will manage our connection to Peopledatalabs tools
  • Validating that COMPOSIO_USER_ID is also set before proceeding
7

Create a Tool Router session

const session = await composio.create(
    userId as string,
    {
        toolkits: ['peopledatalabs']
    }
);

const url = session.mcp.url;
What's happening:
  • We're creating a Tool Router session that gives your agent access to Peopledatalabs tools
  • The create method takes the user ID and specifies which toolkits should be available
  • The returned session.mcp.url is the MCP server URL that your agent will use
  • This approach allows the agent to dynamically load and use Peopledatalabs tools as needed
8

Configure the agent with the MCP URL

const client = new MultiServerMCPClient({
    "peopledatalabs-agent": {
        transport: "http",
        url: url,
        headers: {
            "x-api-key": process.env.COMPOSIO_API_KEY
        }
    }
});

const tools = await client.getTools();

const agent = createAgent({ model: "gpt-5", tools });
What's happening:
  • We're creating a MultiServerMCPClient that connects to our Peopledatalabs MCP server via HTTP
  • The client is configured with a name and the URL from our Tool Router session
  • getTools() retrieves all available Peopledatalabs tools that the agent can use
  • We're creating a LangChain agent using the GPT-5 model
9

Set up interactive chat interface

let conversationHistory: any[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
console.log("Ask any Peopledatalabs related question or task to the agent.\n");

const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: 'You: '
});

rl.prompt();

rl.on('line', async (userInput: string) => {
    const trimmedInput = userInput.trim();

    if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
        console.log("\nGoodbye!");
        rl.close();
        process.exit(0);
    }

    if (!trimmedInput) {
        rl.prompt();
        return;
    }

    conversationHistory.push({ role: "user", content: trimmedInput });
    console.log("\nAgent is thinking...\n");

    const response = await agent.invoke({ messages: conversationHistory });
    conversationHistory = response.messages;

    const finalResponse = response.messages[response.messages.length - 1]?.content;
    console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\n👋 Session ended.');
        process.exit(0);
    });
What's happening:
  • We initialize an empty conversationHistory list to maintain context across interactions
  • A readline interface is used to continuously accept user input from the command line
  • When a user types a message, it's added to the conversation history and sent to the agent
  • The agent processes the request using the invoke() method with the full conversation history
  • Users can type 'exit', 'quit', or 'bye' to end the chat session gracefully
10

Run the application

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});
What's happening:
  • We call the main() function to start the application

Complete Code

Here's the complete code to get you started with Peopledatalabs and LangChain:

import { Composio } from '@composio/core';
import { LangchainProvider } from '@composio/langchain';
import { MultiServerMCPClient } from "@langchain/mcp-adapters";  
import { createAgent } from "langchain";
import * as readline from 'readline';
import 'dotenv/config';

const composioApiKey = process.env.COMPOSIO_API_KEY;
const userId = process.env.COMPOSIO_USER_ID;

if (!composioApiKey) throw new Error('COMPOSIO_API_KEY is not set');
if (!userId) throw new Error('COMPOSIO_USER_ID is not set');

async function main() {
    const composio = new Composio({
        apiKey: composioApiKey as string,
        provider: new LangchainProvider()
    });

    const session = await composio.create(
        userId as string,
        {
            toolkits: ['peopledatalabs']
        }
    );

    const url = session.mcp.url;
    
    const client = new MultiServerMCPClient({
        "peopledatalabs-agent": {
            transport: "http",
            url: url,
            headers: {
                "x-api-key": process.env.COMPOSIO_API_KEY
            }
        }
    });
    
    const tools = await client.getTools();
  
    const agent = createAgent({ model: "gpt-5", tools });
    
    let conversationHistory: any[] = [];
    
    console.log("Chat started! Type 'exit' or 'quit' to end the conversation.\n");
    console.log("Ask any Peopledatalabs related question or task to the agent.\n");
    
    const rl = readline.createInterface({
        input: process.stdin,
        output: process.stdout,
        prompt: 'You: '
    });

    rl.prompt();

    rl.on('line', async (userInput: string) => {
        const trimmedInput = userInput.trim();
        
        if (['exit', 'quit', 'bye'].includes(trimmedInput.toLowerCase())) {
            console.log("\nGoodbye!");
            rl.close();
            process.exit(0);
        }
        
        if (!trimmedInput) {
            rl.prompt();
            return;
        }
        
        conversationHistory.push({ role: "user", content: trimmedInput });
        console.log("\nAgent is thinking...\n");
        
        const response = await agent.invoke({ messages: conversationHistory });
        conversationHistory = response.messages;
        
        const finalResponse = response.messages[response.messages.length - 1]?.content;
        console.log(`Agent: ${finalResponse}\n`);
        
        rl.prompt();
    });

    rl.on('close', () => {
        console.log('\nSession ended.');
        process.exit(0);
    });
}

main().catch((err) => {
    console.error('Fatal error:', err);
    process.exit(1);
});

Conclusion

You've successfully built a LangChain agent that can interact with Peopledatalabs through Composio's Tool Router.

Key features of this implementation:

  • Dynamic tool loading through Composio's Tool Router
  • Conversation history maintenance for context-aware responses
  • Async Python provides clean, efficient execution of agent workflows
You can extend this further by adding error handling, implementing specific business logic, or integrating additional Composio toolkits to create multi-app workflows.
TOOLS

Supported Tools

Every Peopledatalabs action and event your agent gets out of the box.

Clean company data

Cleans and standardizes company information based on a name, website, or profile URL; providing at least one of these inputs is highly recommended for meaningful results.

Clean company data (POST)

Tool to clean and standardize company data using POST method.

Clean location data

Cleans and standardizes a raw, unformatted location string into a structured representation, provided the input is a recognizable geographical place.

Clean location data (POST)

Tool to clean and standardize location data using POST method.

Clean school data

Cleans and standardizes school information; provide at least one of the school's name, website, or profile for optimal results.

Clean school data (POST)

Tool to clean and standardize school data using POST method.

Enrich Bulk Company Data

Tool to enrich up to 100 companies in a single request using the Bulk Company Enrichment API.

Enrich bulk person data

Tool to enrich up to 100 person profiles in a single API request using the Bulk Person Enrichment API.

Enrich Company Data

Enriches company data from People Data Labs with details like firmographics and employee counts.

Enrich IP Data

Enriches an IP address with company, location, metadata, and person data from People Data Labs.

Enrich job title data

Enhances a job title by providing additional contextual information and details.

Enrich person data

Enriches person data using various identifiers; requires a primary ID (profile, email, phone, email_hash, lid, pdl_id) OR a name (full, or first and last) combined with another demographic detail (e.

Enrich skill data

Retrieves detailed, standardized information for a given skill by querying the People Data Labs Skill Enrichment API; for best results, provide a recognized professional skill or area of expertise.

Generate Search Query

Converts natural language queries into structured PDL Elasticsearch queries for people or company searches; generates optimized query structure without executing the search.

Autocomplete field suggestions

Provides autocompletion suggestions for a specific field (e.

Get autocomplete suggestions (POST)

Tool to get autocompletion suggestions using POST method for complex query parameters.

Get column details

Retrieves predefined enum values for a column name from `enum_mappings.

Get schema

Retrieves the schema, including field names, descriptions, and data types, for 'person' or 'company' entity types.

Get subject requests

Tool to retrieve subject access requests for data privacy compliance.

Identify person data

Retrieves detailed profile information for an individual from People Data Labs (PDL), requiring at least one identifier such as email, phone, or profile URL.

People Search with Elasticsearch

Searches for person profiles in the People Data Labs (PDL) database using an Elasticsearch Domain Specific Language (DSL) query.

Query person changelog

Tool to query the changelog of person records between two consecutive dataset versions.

Company Search with Elasticsearch

Performs a search for company profiles within People Data Labs using a custom Elasticsearch Domain Specific Language (DSL) query.

Search Company Records (POST)

Tool to search and filter company records from the full Company Dataset using Elasticsearch or SQL queries via POST method.

FAQ

Frequently asked questions

With a standalone Peopledatalabs MCP server, the agents and LLMs can only access a fixed set of Peopledatalabs tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Peopledatalabs and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. LangChain fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Peopledatalabs tools.

Yes, absolutely. You can configure which Peopledatalabs scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Peopledatalabs data and credentials are handled as safely as possible.

Start with Peopledatalabs.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Peopledatalabs tool your agent needs.Free to start.

Start building