---
title: "OpenClaw B2B data: connect Leadsets via MCP and skills"
description: "Use Leadsets with OpenClaw via the remote MCP server and free skills to search people and companies, enrich contacts and verify work emails."
canonical: https://www.leadsets.ai/integrations/openclaw
updated: 2026-11-09
---

# Using Leadsets with OpenClaw for B2B data

OpenClaw connects to Leadsets through the Leadsets remote MCP server at https://mcp.leadsets.ai plus free SKILL.md skills, as listed on the Leadsets integrations page. The agent can search people and companies, enrich contacts, verify work emails and, on paid plans with scrape units, read company sites and careers pages. Leadsets starts with 1,000 free records, and paid plans run from $29 a month.

OpenClaw is listed on the Leadsets [integrations page](https://www.leadsets.ai/integrations) as a personal agent that connects through the **MCP server + skills**. This page covers what that connection gives the agent, how to set it up using the steps Leadsets documents, and where the limits are.

## What OpenClaw can do with Leadsets

Once the Leadsets MCP server is connected, the agent can call eight tools. Each one also exists as a REST endpoint.

- `search_people`: find people by title, function, seniority, location, company size and industry, with a match reason on every result.
- `search_companies`: find accounts by industry, headcount band, technology and location.
- `enrich_person`: current role, company and a verified work email when one exists.
- `enrich_company`: firmographics for a domain, with source and freshness on every field.
- `verify_email`: label an address verified, catch-all, unknown or invalid, with a confidence score.
- `scrape_company`: turn a company homepage into products, positioning, customers named and key links.
- `scrape_jobs`: turn a careers page into open roles with titles and dates, a hiring signal.
- `get_usage`: report what is left in the current window and week, at no cost.

In practice that means the agent can go from a plain-language description of a customer ("RevOps leads at 50 to 200 person fintechs") to a list of people with verified work emails, check an existing list before sending, or research an account before outreach. Every record comes back as structured JSON with match reasons, verification status, confidence and the date each field was last checked.

## How to connect Leadsets to OpenClaw

The Leadsets docs do not publish setup steps specific to OpenClaw. What follows is the generic setup Leadsets documents for any MCP client and for the REST API. Use whatever place OpenClaw provides for adding a remote MCP server or skills; this page does not describe OpenClaw menus or settings.

1. **Get a key.** Create a free Leadsets account and copy your key from the dashboard. Keys start with `ls_live_` and should be kept server-side. The free plan gives 1,000 records once, with no card.
2. **Add the remote MCP server.** The URL is `https://mcp.leadsets.ai`. It is a remote server, so nothing is installed or run locally. Leadsets documents two authentication patterns: Claude signs in with OAuth and needs no key, while clients configured with headers (the docs show Cursor) pass the key as a bearer token. The documented Cursor configuration looks like this:

```
{
  "mcpServers": {
    "leadsets": {
      "url": "https://mcp.leadsets.ai",
      "headers": { "Authorization": "Bearer ls_live_…" }
    }
  }
}
```

3. **Check it works.** Ask the agent "What's my Leadsets usage?" If it calls `get_usage` and answers with your remaining balance, the connection is live. Full details are in [Connect via MCP](https://www.leadsets.ai/docs/mcp).
4. **Add skills.** Leadsets publishes 50 free, MIT-licensed SKILL.md playbooks for any agent that reads the SKILL.md standard. Download a skill folder or clone the library with `git clone github.com/leadsets/leadsets-skills`. Skills work on the free key; those that use `scrape_company` or `scrape_jobs` need scrape units on a paid plan.
5. **Or call REST directly.** If you would rather call Leadsets from code or an HTTP request step, use `https://api.leadsets.ai/v1` with the key as a bearer token. TypeScript and Python SDKs, idempotency keys, cursor pagination and Retry-After headers are available.

```
curl https://api.leadsets.ai/v1/people/search \
 -H "Authorization: Bearer $LEADSETS_KEY" \
 -d '{ "title": ["VP Sales", "Head of Sales"],
       "employees": "20-200",
       "verified_email": true,
       "limit": 25 }'
```

6. **Get the list out.** Leadsets exports CSV for any sequencer, works with Instantly and Smartlead through skills and CSV, pushes lists into LinkedCamp campaigns, and has skills for Google Sheets and for HubSpot, Salesforce, Pipedrive and Attio.

## Example: a RevOps prospect list for Northwind Analytics

Maya Chen runs revenue operations at Northwind Analytics (northwind.co) and uses OpenClaw as her personal agent. She connects the Leadsets MCP server, adds the [build an outbound prospect list](https://www.leadsets.ai/skills/build-outbound-prospect-list) skill, and asks:

> "Build a list of 100 heads of RevOps at US B2B SaaS companies with 50 to 200 people. Export it as a CSV."

Following the skill, the agent:

1. Confirms the ICP and asks one question if anything is ambiguous.
2. Calls `get_usage` to check remaining limits and plan the run.
3. Probes with a 1-record `search_companies` call to sanity-check the filters.
4. Calls `search_people` to find matching people, each with match reasons.
5. Runs `enrich_person` and `verify_email` on each person.
6. Returns a table with catch-all addresses in a separate segment and reports which people it could not confirm.

If Maya later wants to prioritise accounts hiring SDRs, the agent can add `scrape_jobs`, which needs a paid plan and scrape units.

## What to watch for: records, limits and email labels

- **Records count only when data comes back.** Search and enrichment each use 1 record per record returned. An empty search uses 0 records but still counts as 1 request.
- **Free records are one time.** The 1,000 free records are shared across search and enrichment and do not refill. When they run out, the API returns `402 free_records_exhausted`; the agent should ask you to upgrade rather than retry.
- **Paid plans have fair-use windows.** Solo ($29 a month) allows 1,000 enrichments and 500 search records per rolling five hours; Pro ($99) 15,000 and 7,500; Team ($399) 150,000 and 75,000; Max ($999) 225,000 and 112,500, each with a weekly limit too. Over a limit, Leadsets returns `429` with a Retry-After time and the blocked call counts against nothing. See [limits and costs](https://www.leadsets.ai/docs/limits) and [pricing](https://www.leadsets.ai/pricing).
- **Concurrency.** Solo allows 3 concurrent searches, Pro 5, Team and Max 8. Extra searches get `429 too_many_concurrent`.
- **Verification labels.** Emails from `enrich_person` are already verified at no extra charge. Standalone `verify_email` counts toward the enrichment limit. Verified means the mailbox accepts mail; catch-all means the domain accepts everything, so send at lower volume (see [what a catch-all email is](https://www.leadsets.ai/answers/what-is-a-catch-all-email)); unknown means no clear answer; invalid addresses are never served as contact emails.
- **Scraping is separate.** `scrape_company` and `scrape_jobs` use scrape units (1 unit per standard page), sold in packs of $9 for 1,000, $19 for 5,000 and $49 for 20,000 on paid plans. They are not on Free.

## What this integration does not do

- **No phone numbers.** Leadsets returns work emails, US personal emails on paid plans, roles and company data. Phone numbers are not offered yet.
- **Not a CRM or a sending tool.** Leadsets feeds your CRM and sequencer through skills, the API and CSV; it does not send email.
- **Business data only.** No consumer data, no sensitive categories and no personal home addresses. Nothing is scraped from behind a login.
- **No SOC 2 report yet.** SOC 2 Type I readiness is underway with a target of Q3 2027. Leadsets runs a GDPR-aligned program and offers a DPA today.
- **No OpenClaw-specific documentation.** Leadsets documents the generic MCP and REST setup above; it does not publish OpenClaw-specific steps.

You remain responsible for the outreach laws that apply to you, such as CAN-SPAM, GDPR and CASL.

## Questions and answers

### Does Leadsets work with OpenClaw?

Yes. The Leadsets integrations page lists OpenClaw as a personal agent that connects through the Leadsets MCP server and skills. Leadsets does not publish OpenClaw-specific setup steps, so you use the generic remote MCP setup from its docs.

### What is the Leadsets MCP server URL for OpenClaw?

The Leadsets remote MCP server is at https://mcp.leadsets.ai and exposes eight tools, including search_people, enrich_person and verify_email. It is remote, so nothing is installed or run locally.

### Do I need a Leadsets API key to connect OpenClaw?

It depends on how the client authenticates. Leadsets documents OAuth sign-in for Claude and a bearer key (starting with ls_live_) in an Authorization header for clients configured with headers, such as Cursor. The REST API at https://api.leadsets.ai/v1 always uses a bearer key.

### How much does it cost to use Leadsets from OpenClaw?

Leadsets has a free plan with 1,000 one-time records and no card. Paid plans are flat monthly prices in USD: Solo $29, Pro $99, Team $399 and Max $999, with fair-use limits per five hours and per week. Web scraping is an add-on from $9 for 1,000 units.

### Can my OpenClaw agent get phone numbers from Leadsets?

No. Leadsets does not offer phone numbers yet. It returns work emails, US personal emails on paid plans, roles and company data.

### What do the Leadsets email statuses mean?

Verified means the mailbox accepts mail, catch-all means the domain accepts everything so no one can confirm it, and unknown means the server gave no clear answer. Invalid addresses bounce and are never served as contact emails.

---

Leadsets · https://www.leadsets.ai · Site index: https://www.leadsets.ai/llms.txt