---
title: "LeadLists MCP Server: Lead List Tools for AI Agents"
description: "Connect Claude, ChatGPT, Cursor or your own agent to the LeadLists MCP server at leadlists.app/mcp and build verified lead lists of local businesses from a chat."
url: https://leadlists.app/docs/mcp
---

Docs

# LeadLists MCP server

Give Claude, ChatGPT, Cursor or your own agent the LeadLists tools. Ask for "dentists in Austin with the owner's email" in a chat and get the leads back in the same conversation.

## Server URL

https://leadlists.app/mcp

Streamable HTTP. JSON-RPC 2.0, protocol versions 2024-11-05 to 2025-11-25.

Step-by-step setup for Claude, ChatGPT, Cursor, Windsurf, Gemini CLI and n8n is in the [MCP section on the homepage](https://leadlists.app/#mcp). The short versions:

claude mcp add --transport http leadlists https://leadlists.app/mcp

Claude Code

gemini mcp add --transport http leadlists https://leadlists.app/mcp

Gemini CLI

{
  "mcpServers": {
    "leadlists": { "url": "https://leadlists.app/mcp" }
  }
}

Cursor (mcp.json)

POST https://leadlists.app/mcp
Authorization: Bearer ll_your_api_key
Content-Type: application/json

{"jsonrpc":"2.0","id":1,"method":"tools/list"}

Any client with an API key

## Sign-in

Clients that support OAuth open a LeadLists sign-in and consent screen the first time they connect. The server supports OAuth 2.1 with dynamic client registration and PKCE, and advertises itself through [protected resource metadata](https://leadlists.app/.well-known/oauth-protected-resource/mcp). Clients without OAuth send an API key from [Settings, then API](https://app.leadlists.app/settings/api) as `Authorization: Bearer ll_…`. The full flow is in [auth.md](https://leadlists.app/auth.md).

The MCP server is included on the Bespoke Starter and Bespoke Pro plans. See [pricing](https://leadlists.app/pricing).

## Lead tools

| Tool         | What it does                                                                                                                                                                                                                |
| ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| find\_leads  | Build a lead list from a plain request, such as "roofing contractors in Dallas, TX with under 20 reviews". Scans the area, then finds the owner, email and phone for each business. Returns the first leads and a list\_id. |
| create\_list | Scan and estimate without building. Returns the number of matches and how many are likely to have an email. Nothing is charged.                                                                                             |
| build\_leads | Start building a list that has finished scanning, up to max\_leads. Only businesses with an email are charged.                                                                                                              |
| get\_list    | Status and progress of a list: scan results, the estimate and the current build.                                                                                                                                            |
| get\_leads   | The leads in a list: business, owner, email, phone, website, address, category, rating and reviews. Paginate with offset.                                                                                                   |
| list\_lists  | The user's lists, newest first.                                                                                                                                                                                             |
| stop\_list   | Stop a scan or build. Leads already delivered are kept.                                                                                                                                                                     |
| get\_usage   | The user's plan and how many leads are left this month.                                                                                                                                                                     |

The usual call is `find_leads` with one business type and one US city or area, then `get_leads` with the returned `list_id` until the build is done. Each lead with an email uses one lead from the monthly allowance; businesses where no email is found are free.

## Data tools

The same live sources the LeadLists agent uses are available as tools: `google_maps_search`, `google_places_search`, `google_reviews`, `google_search`, `fetch_page`, `yelp_search`, `yelp_place`, `linkedin_company`, `linkedin_jobs`, `indeed_search`, `google_jobs`, `facebook_search_pages`, `instagram_profile`, `google_news`, `reddit_search`, `zillow_search`. Every other source (marketplaces, job boards, app stores, social profiles and more) is reached through `list_data_sources` and `query_data_source`.

## Discovery files

- [MCP server card](https://leadlists.app/mcp/server-card) (also at [/.well-known/mcp/server-card.json](https://leadlists.app/.well-known/mcp/server-card.json))
- [AI catalog](https://leadlists.app/.well-known/ai-catalog.json) and [API catalog](https://leadlists.app/.well-known/api-catalog)
- [Agent skill](https://leadlists.app/.well-known/agent-skills/leadlists/SKILL.md) and [llms.txt](https://leadlists.app/llms.txt)

Building against the REST API instead? See the [LeadLists API docs](https://leadlists.app/docs/api). Stuck? [Contact us](https://leadlists.app/contact).
