---
ref: tool:lemlist/search-people
name: Search people
company: company:lemlist
workflows: []
access: [mcp, cli, api]
tags: [capability:build-audience, category:sales-engagement, has:api, has:cli, has:mcp]
docs: https://developer.lemlist.com/api-reference/endpoints/people-database/search-people-database
updated: 2026-09-27
---

# Search people

Returns people from lemlist's B2B database who match filters such as country, job title or department, with their LinkedIn profile and current company but no email address.

Send `filters`, each a `filterId` with `in` and `out` value lists
(`GET /database/filters` lists the filter ids), and optionally a free-text
`search`.
Pages hold up to 100 people (`size`), and searches are limited to a number of
queries every 24 hours, reported in the response's `limitation`. Enrich the
people you keep to get their emails.

## Set up

Use the first option your agent supports.

### MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

```json
{ "mcpServers": { "lemlist": { "url": "https://app.lemlist.com/mcp" } } }
```

Call the MCP tool `lemleads_search`.

Server URL: https://app.lemlist.com/mcp

### CLI (official)

Install the command, then confirm it runs.

```sh
npm install -g @lemlist-official/cli
lemlist --version
```

Run `lemlist api POST /database/people`.

### API (official)

- Base URL: https://api.lemlist.com/api
- Endpoint: `POST /database/people`
- Auth: send the header `Authorization: Basic $LEMLIST_API_KEY`
- Get a key: https://app.lemlist.com/settings/integrations
- Docs: https://developer.lemlist.com/api-reference/getting-started/authentication

Before doing anything else, make one read-only call to confirm access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data.
- Never print API keys.