# Hilead MCP Server

> A remote MCP server at https://api.app.hilead.co/mcp, over Streamable HTTP, published in the official MCP registry as co.hilead/hilead. It exposes signal-based lead discovery, the lead pool, campaign drafting and campaign results. Canonical HTML page: https://hilead.co/mcp

Hilead speaks MCP, so an assistant can do your prospecting research where you already work. Point any MCP client at one URL, sign in with your Hilead account, and ask it to find accounts showing buying signals, read what a campaign is doing, or pull the thread of a reply.

## Connecting

Authentication is OAuth 2.1 with PKCE and dynamic client registration. You sign in on Hilead, not in the client, and the client only ever receives a token. Two scopes exist: read, and read_write for the tools that create or change something. You can revoke a client at any time.

1. **Add the server** — Give your MCP client the endpoint https://api.app.hilead.co/mcp. Most clients ask for nothing else: the transport, the scopes and the client registration are all discovered from the URL.
2. **Sign in once** — The client opens Hilead in your browser and asks you to authorize it. You approve the scopes you want to grant. No API key to copy, no password to paste anywhere.
3. **Ask for what you need** — The assistant sees your workspaces, audiences and campaigns. Ask it to discover leads on a signal, summarise a campaign report, or find every conversation waiting on a reply.

## What an assistant can do

### Discovery on buying signals

Run a fresh people search against the live discovery provider, filtered on firmographics and on signals such as funding rounds, key hires, hiring activity, expansion and technology changes.

- "Find heads of sales at French SaaS companies that raised in the last 90 days"
- "Which of these companies have open roles right now?"
- "Check what discovery quota I have left this month"

### Audiences and the lead pool

Browse and search the leads already in the workspace, inspect a single lead or company, create an audience and re-run its matching.

- "Search my pool for CTOs at companies over 200 people"
- "Build an audience from the results of that search"
- "Show me everything we know about this company"

### Campaign drafting

Read a campaign, draft or revise its sequence, validate a draft against the contract, import leads and include or exclude prospects. Content writes stay in draft.

- "Draft a four-step sequence with a LinkedIn invite before the first email"
- "Validate this draft before I open it in the app"
- "Exclude the prospects who already replied"

### Results and replies

Read campaign reports and activity, per-signal engagement, analytics, booked meetings, sender status and the full text of conversations.

- "Summarise last week across every running campaign"
- "Which signal produced the best reply rate?"
- "Show me the threads waiting on an answer from us"

## What it deliberately cannot do

Enforced by the server, not by a prompt, so no instruction can talk it into them.

- **It cannot send a message** — No email, no LinkedIn message, no reply. An assistant can draft and you send, never the other way round.
- **It cannot launch a campaign** — A campaign created or edited over MCP stays a draft until you open it in Hilead and start it yourself.
- **It cannot spend your credits** — Contact enrichment is not exposed at all, so an assistant cannot reveal an email or a phone number, and cannot burn a credit trying.
- **It can pause a campaign** — The one write that reaches a live campaign, and it only ever stops things. Useful when you spot a problem from the chat.

## Hard limits

- Profiles per discovery call: 25 by default, 100 maximum
- Discovery results added to an audience: 5,000 per call
- Leads imported into a campaign: 500 per call
- Conversation messages returned: 200 per page
- Steps in a sequence: 200, nested up to 12 deep
- A/B variants per step: 10

## Plan

MCP access is included on every paid plan, from STARTER at $49 a month. The 7-day trial includes it too, and a card is required to start.

## Frequently asked questions

### What is the Hilead MCP server?

It is a remote MCP server at https://api.app.hilead.co/mcp, over Streamable HTTP. MCP is the open protocol assistants use to reach outside tools, so any client that speaks it can use Hilead: discovery on buying signals, the lead pool, campaign drafting and campaign results.

### Which clients can connect to it?

Any MCP client that supports remote servers with OAuth. That covers Claude, and the growing list of editors and assistants that added MCP support. Nothing is client-specific on our side: the same endpoint serves all of them.

### Can an assistant send emails on my behalf?

No. Message sending is switched off at the server, along with campaign launching and contact enrichment. An assistant can draft a sequence and you review and start it in Hilead. The only write that touches a running campaign is pausing it.

### Does it cost credits to use?

Enrichment credits cannot be spent over MCP, because enrichment is not exposed. Lead discovery does consume your workspace discovery quota, the same quota the app uses, and it is capped per call and per workspace.

### Do I need a paid plan?

MCP access is included on every paid plan, from STARTER at $49 a month. The 7-day trial includes it too, and a card is required to start.

### How do I revoke an assistant's access?

Hilead is its own authorization server, so access is revoked on our side and takes effect immediately, without depending on the client. Authorize with the scope you actually need: read is enough for research and reporting.

### Is the server listed in the official MCP registry?

Yes, under co.hilead/hilead. That is the registry the community directories read from, so the listing propagates to them without a separate submission.
