# Leadsets MCP server

> Search B2B people and companies, enrich records, verify work emails and scrape company sites and careers pages.

- Listing: https://mcp.tc/i/leadsets
- Connect: use the server's own URL `https://mcp.leadsets.ai` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [CRM, Sales & Support](https://mcp.tc/c/crm-sales)
- Vendor: Leadsets
- Homepage: <https://www.leadsets.ai/docs/mcp>
- Docs: <https://www.leadsets.ai/docs/mcp>

## About

Leadsets is a B2B data API with a remote MCP server for AI agents. It searches people and companies, enriches records, verifies work emails and scrapes company sites and careers pages. Results include match reasons, verification status and last-checked dates.

The server runs as a hosted endpoint at https://mcp.leadsets.ai and works in Claude, Cursor, ChatGPT and other MCP clients. A REST API is also available with an API key. A free plan includes 1,000 records without a card; paid plans have usage limits that the get\_usage tool reports.

## What it can do

- Search people by title, function, seniority, location and company size
- Search companies by domain, headcount, industry, stack and hiring signals
- Enrich a person or company record
- Verify work email addresses
- Scrape job listings and company websites into structured facts
- Check remaining usage before a run

## Example prompts

- "Find US SaaS companies with 20-200 people hiring SDRs in the last 30 days."
- "Get VP-level revenue leaders at those companies with verified work emails."
- "Verify these 50 email addresses and tell me which are catch-all."
- "Scrape example.com and summarize its products and pricing."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http leadsets https://mcp.leadsets.ai
```

2. Start Claude Code, type `/mcp`, pick **leadsets** and choose **Authenticate**. A browser window opens for the Leadsets sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Leadsets** and paste this URL:

```url
https://mcp.leadsets.ai
```

3. Click **Add**, then **Connect**, and sign in when Leadsets asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Leadsets&connectorUrl=https%3A%2F%2Fmcp.leadsets.ai>) (opens connector settings)

2. Check that the URL reads `https://mcp.leadsets.ai` and click **Add**.

3. Click **Connect** and sign in when Leadsets asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://mcp.leadsets.ai` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to Leadsets to sign in.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=leadsets&config=eyJ1cmwiOiJodHRwczovL21jcC5sZWFkc2V0cy5haSJ9>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "leadsets": {
      "url": "https://mcp.leadsets.ai"
    }
  }
}
```

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=leadsets&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.leadsets.ai%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"leadsets","type":"http","url":"https://mcp.leadsets.ai"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "leadsets": {
      "type": "http",
      "url": "https://mcp.leadsets.ai"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "leadsets": {
      "serverUrl": "https://mcp.leadsets.ai"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add leadsets --url https://mcp.leadsets.ai
codex mcp login leadsets
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.leadsets]
url = "https://mcp.leadsets.ai"
```

### Gemini CLI

```bash
gemini mcp add --transport http leadsets https://mcp.leadsets.ai
```

Then, inside Gemini CLI, run `/mcp auth leadsets` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "leadsets": {
      "type": "http",
      "url": "https://mcp.leadsets.ai"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.leadsets.ai`.

## Details

- Last checked: 2026-11-18 (reachable, asks for credentials)
- Listed: 2026-11-17
- Updated: 2026-11-17

---
Source: https://mcp.tc/i/leadsets (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
