Is this an official People Data Labs MCP server?

No. It is Memtro's MCP server with Memtro's People Data Labs connector behind it: the connector reads People Data Labs through its API with the credentials you connect on Dashboard → Connections, and People Data Labs publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in People Data Labs?

Not yet. Today every People Data Labs tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · CRM and sales

People Data Labs MCP server

People Data Labs in any MCP client, through Memtro: People Data Labs does not publish this server. Memtro's People Data Labs connector reads People Data Labs through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

People Data Labs enrichment: look up one person by email, social profile or name and employer, or one company by name, website or ticker, and search PDL's person and company datasets with SQL; each returns work identity only (name, title, level, employer, industry, country), never contact details, addresses, birth dates, social profiles or history. Every lookup except autocomplete spends the customer's PDL credits. Read-only.

Reads

peopledatalabs_enrich_personCOSTS 1 PDL CREDIT PER MATCH (no match is free).
peopledatalabs_identify_personCOSTS 1 PDL CREDIT PER CALL, EVEN WHEN NOTHING MATCHES.
peopledatalabs_enrich_companyCOSTS 1 PDL CREDIT PER MATCH (no match is free).
peopledatalabs_search_peopleCOSTS 1 PDL CREDIT PER PERSON RETURNED (size 10 can spend 10 credits).
peopledatalabs_search_companiesCOSTS 1 PDL CREDIT PER COMPANY RETURNED.
peopledatalabs_autocompleteFree (no credits): People Data Labs' canonical values for a field, ranked by how many records use them, e.g. job titles starting 'head of'…

Connect it

First connect People Data Labs on Dashboard → Connections, then add Memtro to your client once. The People Data Labs tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared People Data Labs connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› What does People Data Labs have on the company at northwind.com?
› Who is priya@bigco.com and what is her role?
› Which UK software companies with more than 50 employees are in PDL?
› How much funding has BigCo raised, and at what stage?
› What job titles does PDL use that start with head of?

Questions

Is this an official People Data Labs MCP server?: No. It is Memtro's MCP server with Memtro's People Data Labs connector behind it: the connector reads People Data Labs through its API with the credentials you connect on Dashboard → Connections, and People Data Labs publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in People Data Labs?: Not yet. Today every People Data Labs tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.