---
title: "OpenAI Dots MCP: connect Leadsets B2B data"
description: "Connect OpenAI Dots to the Leadsets MCP server at mcp.leadsets.ai for B2B search, enrichment and verified work emails, with setup steps and limits."
canonical: https://www.leadsets.ai/integrations/openai-dots
updated: 2026-11-09
---

# Use Leadsets with OpenAI Dots over MCP

Leadsets lists OpenAI Dots as a supported personal agent, connected through its remote MCP server at https://mcp.leadsets.ai plus free GTM skills. Once connected, the agent can call eight tools to search people and companies, enrich contacts, verify work emails, scrape company sites and check usage. Leadsets publishes no Dots-specific setup steps, so the generic MCP setup applies. The free plan includes 1,000 records.

## What Leadsets adds to OpenAI Dots

OpenAI Dots appears on the Leadsets integrations page in the personal agents group, with the connection listed as "MCP server + skills". Leadsets publishes nothing else about OpenAI Dots, so this page covers only what happens on the Leadsets side.

Once the Leadsets MCP server is connected, the agent can call eight tools:

- `search_people`: people by title, function, seniority, location, company size and industry, with a reason for every match
- `search_companies`: 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`: verified, catch-all, unknown or invalid, with a confidence score
- `scrape_company` and `scrape_jobs`: a homepage or careers page turned into structured facts and hiring signals
- `get_usage`: what is left in the current window and week, at no cost

Results come back as structured JSON with match reasons, verification status, confidence and the date each field was last checked, so the agent can decide what to trust. You brief it in plain language, the way you would brief an SDR, for example "Find 50 heads of growth at Series A fintechs in New York with verified emails", and it picks the tools.

## How to connect Leadsets to OpenAI Dots

The Leadsets docs give client-specific steps for Claude, Claude Code, Cursor and ChatGPT, but none specific to OpenAI Dots. The steps below are the generic setup from the [MCP docs](https://www.leadsets.ai/docs/mcp). Use OpenAI Dots' own instructions for where a remote MCP server is added; this page does not describe its menus or settings.

1. **Create a free Leadsets account.** The free plan gives 1,000 records once, with no card. API keys start with `ls_live_` and should be kept server-side.
2. **Add the remote MCP server URL:** `https://mcp.leadsets.ai`. It is a remote server, so nothing is installed or run locally.
3. **Authenticate.** The docs describe two patterns. In Claude on the web and desktop, the connector signs in with OAuth and there is no key to paste. In Cursor, you add an `Authorization` header with `Bearer ls_live_…`. Use whichever method your client supports.
4. **Check the connection.** Ask the agent "What's my Leadsets usage?" If it calls `get_usage` and answers with your remaining balance, you are connected.
5. **Add skills.** Leadsets publishes 50 free, MIT-licensed SKILL.md playbooks that tell an agent which tools to call and in what order. Clone them with `git clone github.com/leadsets/leadsets-skills` or browse the [skills library](https://www.leadsets.ai/skills). The site does not say how OpenAI Dots loads a skill, so follow its own documentation for that step.

**REST instead of MCP.** If a workflow step makes HTTP requests rather than MCP calls, every tool is also a REST endpoint at `https://api.leadsets.ai/v1` with a bearer key:

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

TypeScript and Python SDKs (`npm i @leadsets/sdk`, `pip install leadsets`) add typed responses and automatic retries on 429.

**Getting the list out.** Leadsets exports CSV for any sequencer, works with Instantly and Smartlead through skills and CSV, and can push lists straight into LinkedCamp campaigns. Skills also write to Google Sheets and CRMs such as HubSpot.

## Example: a hiring-signal list for Northwind Analytics

Maya Chen runs revenue operations at Northwind Analytics (northwind.co). She connects Leadsets to OpenAI Dots and asks:

> "Find US B2B SaaS companies with 20 to 200 people that have been hiring SDRs in the last 30 days. Get their revenue leaders with verified work emails, and put catch-alls in a separate list."

A typical run looks like this (illustrative numbers):

1. `get_usage` checks what is left in the five-hour window.
2. `search_companies` finds 86 matching accounts.
3. `scrape_jobs` reads 86 careers pages and confirms 71 are hiring SDRs.
4. `search_people` returns 214 VP-level revenue leaders at those accounts.
5. `enrich_person` returns work emails, already verified; 171 of 214 come back verified, and catch-alls go to a second list.

On a Solo plan, that run uses 300 search records out of 500 per five hours, 214 enrichment records out of 1,000, and at least 86 scrape units from an add-on pack. On the free plan, steps 2, 4 and 5 work, but `scrape_jobs` does not, because scraping is not on Free. Maya then exports the verified list as CSV for her sequencer.

## What to watch for

- **Records and requests.** A record counts only when data comes back, so an empty search uses none. Every call counts as a request, hit or miss; the request limit is five times the record allowance. See [limits and costs](https://www.leadsets.ai/docs/limits).
- **Five-hour and weekly windows.** Paid plans have rolling five-hour limits and a weekly backstop for search and enrichment, listed on the [pricing page](https://www.leadsets.ai/pricing). Over a limit, the API returns 429 with a Retry-After time, and the blocked call counts against nothing. Solo allows 3 concurrent searches, Pro 5, Team and Max 8.
- **Free records run out.** The 1,000 free records are one time, shared across search and enrichment, and do not refill. When they are gone, the API returns 402 `free_records_exhausted`; the agent should ask you to upgrade rather than retry.
- **Verification labels.** Verified means the mailbox accepts mail. [Catch-all](https://www.leadsets.ai/answers/what-is-a-catch-all-email) means the domain accepts everything, so send at lower volume. Unknown means the server gave no clear answer; treat it as unconfirmed. Invalid addresses are never served as contact emails. Standalone `verify_email` calls count toward the enrichment limit.
- **Scraping is metered separately.** One unit is one standard page. Packs cost $9 for 1,000 units, $19 for 5,000 and $49 for 20,000, on any paid plan.

## 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.
- **No sending and no CRM.** Leadsets feeds your sequencer and CRM; it does not send email or store pipeline.
- **Business data only.** No consumer data, no sensitive categories and no personal home addresses. Nothing is scraped from behind a login, and scraping reads public pages only.
- **No SOC 2 report yet.** SOC 2 Type I readiness is underway with a target of Q3 2027. If you need a SOC 2 report today, that rules Leadsets out for now.
- **No Dots-specific documentation.** Leadsets does not publish setup screens or settings for OpenAI Dots, so anything inside the client follows its own documentation.

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

## Questions and answers

### Does Leadsets work with OpenAI Dots?

Yes. The Leadsets integrations page lists OpenAI Dots among personal agents, connected through the remote MCP server at https://mcp.leadsets.ai and the free GTM skills. Leadsets does not publish setup steps specific to OpenAI Dots, so the generic MCP setup applies.

### What is the Leadsets MCP server URL for OpenAI Dots?

The Leadsets MCP server is at https://mcp.leadsets.ai and nothing needs to be installed locally. The same tools are available over REST at https://api.leadsets.ai/v1 with a bearer key.

### Do I need a Leadsets API key to connect OpenAI Dots?

It depends on how the client authenticates. The Leadsets docs describe OAuth sign-in with no key for Claude, and an Authorization header with a bearer key starting ls_live_ for Cursor. Use the method your client supports.

### How do I check that Leadsets is connected?

Ask the agent "What's my Leadsets usage?" If it calls get_usage and answers with your remaining balance, the connection works. get_usage costs nothing to call.

### How much does it cost to use Leadsets through an agent like OpenAI Dots?

Leadsets has a free plan with 1,000 one-time records and no card, then flat monthly plans in USD: Solo $29, Pro $99, Team $399 and Max $999, with no credits. Web scraping is an add-on from $9 for 1,000 units on paid plans.

### Can OpenAI Dots get phone numbers through Leadsets?

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

---

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