# Leadmagic [Health: Active]

**Category:** 💬 Communication  
**Repository:** https://github.com/pipeworx-io/mcp-leadmagic  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/leadmagic

## Description
LeadMagic MCP — wraps the LeadMagic B2B email-finder API (leadmagic.io)

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "leadmagic": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-leadmagic"]
  }
}
```

## Documentation

## What the Leadmagic MCP server does

The Leadmagic MCP server exposes LeadMagic's email-finder endpoint through the Model Context Protocol. It is designed for looking up a professional email address from three identifying inputs: a person's first name, last name, and company domain. The integration is unofficial and is not affiliated with, endorsed by, or published by LeadMagic.

The primary operation is `leadmagic_find_email`. A successful match can include the email address, a `valid` status, employment verification, company name, company industry, MX provider, a message, and the number of credits consumed. LeadMagic reports returned email addresses as SMTP-validated. When no match is found, the response can contain `email: null` with zero credits consumed; the integration treats the email field as the match indicator rather than relying on the response envelope.

## How it works

The Leadmagic MCP server sends requests to LeadMagic's `/v1/people/email-finder` API endpoint. The API key is supplied for the individual tool call as `_apiKey`, and the gateway forwards it using the `X-API-Key` header. LeadMagic also documents bearer authorization as an accepted form, but this package uses `X-API-Key`.

You can connect through the hosted Pipeworx MCP endpoint or run the package locally over standard input and output. The hosted endpoint includes this pack's tool along with shared Pipeworx tools such as discovery, routing, and memory operations. A local process exposes only the LeadMagic pack's tools. Both connection styles use the same underlying integration and require your own LeadMagic credentials.

## Setup and configuration

For a hosted connection, add the following MCP server URL to a compatible client:

```json
{
  "mcpServers": {
    "leadmagic": {
      "url": "https://gateway.pipeworx.io/leadmagic/mcp"
    }
  }
}
```

The Leadmagic MCP server can also run without a Pipeworx account by using the npm package as a local stdio process:

```json
{
  "mcpServers": {
    "leadmagic": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-leadmagic"]
    }
  }
}
```

In either mode, provide a valid LeadMagic API key through the `_apiKey` argument when invoking `leadmagic_find_email`. The README does not specify an environment variable configuration. The hosted service also provides HTTP endpoints for inspecting a tool and searching available packs.

## Tools and capabilities

The Leadmagic MCP server currently documents one pack-specific tool:

- `leadmagic_find_email(first_name, last_name, domain, _apiKey)`: looks up a work email and returns available employment and company fields.

The hosted pack endpoint additionally lists shared Pipeworx meta-tools. Its exact tool set can change, and the endpoint's `initialize` response is the authoritative source for the current scope. The local stdio package does not add those shared gateway tools.

## Limitations and notes

This integration requires a LeadMagic API key supplied by the user; the platform does not provide one. A lookup needs a person's name and a company domain, so it is not documented as a general company or contact search tool. The available material confirms the `valid` status example but does not establish the complete set of possible status values. It also does not confirm how malformed domains are handled.

The response structure is based on LeadMagic's vendor documentation, while the authentication header and live endpoint behavior were confirmed separately. A no-match result is represented as a populated HTTP 200 response with a null email, not necessarily as an error. The package is MIT licensed and is an independent Pipeworx integration.

_Full upstream README: https://allmcps.com/mcp/leadmagic/readme_