MCP

Connect A-Leads' B2B contact database, real-time enrichment engine, and people & company search directly to your AI tool. Then run end-to-end prospecting, all from a single conversation.

With A-Leads MCP, you can search for people and companies, find professional emails, verify email deliverability, retrieve direct phone numbers, review your saved searches, and check your credit usage — all from a natural-language conversation.

A-Leads MCP connects to any MCP-compatible client that supports remote servers over Streamable HTTP and OAuth 2.0 — including Cursor, Claude Code, OpenAI Codex, Claude Desktop, and VS Code with GitHub Copilot.

🚧
Private by default
Before you connect A-Leads MCP to any AI client, confirm that model training is turned off in your AI account or client settings. Don't use A-Leads MCP with clients that train models on your data.

Endpoint

Use the following endpoint to connect to the A-Leads MCP server:

https://mcp.a-leads.co

Setting	Value
Endpoint	https://mcp.a-leads.co
Transport	Streamable HTTP
Authentication	OAuth 2.0
Local install required	No
API key required	No

When you connect, your MCP client opens a browser-based OAuth flow. Sign in to A-Leads and authorize access to your workspace, then you're ready to use A-Leads with your AI tool.

Permissions and access

A-Leads MCP reflects your A-Leads account permissions, plan, and available credits. The AI assistant can only perform actions that your A-Leads user account, plan, and credit balance allow.

For example:

If your subscription is inactive or expired, your AI assistant can't run searches or enrichment.
If your workspace doesn't have enough credits for an enrichment action, your assistant can't complete the action.
Access is scoped to the A-Leads user who authorizes the connection.

A-Leads plan limits, credit limits, and feature availability all apply to MCP usage.

Before you start

Make sure you have:

An active A-Leads account with a valid subscription.
Available credits for search, enrichment, and verification actions.
An MCP-compatible client that supports remote MCP servers over Streamable HTTP with OAuth.
A browser for the one-time OAuth sign-in.
Model training turned off in your AI account or client settings.

Connect A-Leads MCP

Add the A-Leads MCP endpoint to your MCP-compatible client:

https://mcp.a-leads.co

If your client asks for a transport type, choose Streamable HTTP. Some clients may label this as HTTP or Streaming HTTP.

After you save the server, complete the OAuth flow in your browser to connect your A-Leads account. A-Leads uses OAuth 2.0 with the authorization code flow and PKCE (S256), and supports refresh tokens so your client stays connected.

Client setup examples

The following examples show common MCP client configurations.

Cursor

Open Cursor settings and add a new MCP server. Use the following configuration:

{
  "mcpServers": {
    "a-leads": {
      "url": "https://mcp.a-leads.co"
    }
  }
}

Save the configuration and restart Cursor. When you use an A-Leads tool for the first time, complete the OAuth flow to connect your A-Leads workspace.

Claude Code

Run the following command:

claude mcp add --transport http a-leads https://mcp.a-leads.co

Then run the following command in Claude Code and complete the OAuth flow:

/mcp

OpenAI Codex

Add A-Leads MCP to your Codex configuration at ~/.codex/config.toml:

[mcp_servers.a-leads]
url = "https://mcp.a-leads.co"

Then authenticate:

codex mcp login a-leads

Complete the OAuth flow to connect your A-Leads account.

VS Code with GitHub Copilot

Create a .vscode/mcp.json file in your workspace:

{
  "servers": {
    "a-leads": {
      "type": "http",
      "url": "https://mcp.a-leads.co"
    }
  }
}

Open the Command Palette and run:

MCP: List Servers

Start the A-Leads server and complete the OAuth flow when prompted.

Claude Desktop

Open Claude Desktop settings and go to Connectors. Add a connector with the following URL:

https://mcp.a-leads.co

Complete the OAuth flow to connect your A-Leads workspace.

Other MCP-compatible clients

For any other MCP-compatible client, add the A-Leads MCP endpoint as a remote server:

https://mcp.a-leads.co

Use Streamable HTTP as the transport and OAuth 2.0 for authentication.

Available actions

Most clients let you set each action to Always allow, Approval required, or Blocked. A-Leads recommends Approval required for any action that consumes credits.

Action	Tool	Description	Credit cost
Advanced people search	`aleads_advanced_search`	Turn a natural-language people/company query into structured filters and run the search. Supports 60+ filters across role, seniority, location, company firmographics, technologies, funding, job postings, and web traffic.	1 credit per search that returns results
Company search	`aleads_company_search`	Search the company-only index with structured firmographic, technology, funding, and hiring filters.	1 credit per search that returns results
Find email	`aleads_find_email`	Find a professional email for a single person from their name and company website.	1 credit per successful find
Bulk find email	`aleads_bulk_find_email`	Find professional emails for up to 10 people in one call from names and company websites.	1 credit per successful find
Verify email	`aleads_verify_email`	Check whether a single email address is valid and deliverable, with a quality score.	1 credit per valid email
Bulk verify email	`aleads_bulk_verify_email`	Verify up to 10 email addresses in one call.	1 credit per valid email
Find phone	`aleads_find_phone`	Retrieve a direct phone number for a person from their LinkedIn username.	15 credits per successful find
Get saved searches	`aleads_get_saved_searches`	List your saved advanced searches (paginated, 25 per page, up to 50 pages).	No
Get user details	`aleads_get_user_details`	Return your profile (email, team status) and, optionally, remaining credits and credit usage.	No

📘
Credits are only charged on success
Search tools charge only when results are returned. Find and verify tools charge only when a valid email is found or a verified result is returned — there's no charge for a "not found" or invalid result.

📌
Missing an action?
If an action isn't working or doesn't appear in your AI client, try disconnecting and reconnecting A-Leads MCP.

Sample queries

Search and prospect

Search for people and companies using natural language.

Find VP-level marketing leaders at SaaS companies with 201–500 employees in the United States.

Search for engineering managers at healthcare companies that use Salesforce.

Find Series B fintech companies headquartered in London that are actively hiring for sales roles.

📘
Search returns profile data only
People search returns profile and firmographic data. To retrieve an email or phone number, use a find or enrichment action on the result rows.

Find and verify emails

Use the find and verify tools to retrieve and validate contact data.

Find the professional email for Jane Smith at acme.com.

Verify whether [email protected] is valid and deliverable.

Here are 8 contacts (name + company website). Find emails for all of them, then verify each one.

🚧
Confirm bulk actions before running them
Bulk find and bulk verify accept up to 10 rows per call and consume credits. Your assistant will state the exact number of rows and the maximum credit cost, then ask you to confirm before running.

Retrieve phone numbers

Find the direct phone number for the LinkedIn profile linkedin.com/in/janesmith.

❗️
Phone lookups are credit-intensive
aleads_find_phone costs 15 credits per successful lookup. Approve these requests carefully.

Research companies

Find computer-software companies with 51–200 employees that offer a free trial.

Search for cybersecurity companies in Germany that raised a Series A and use AWS.

Manage saved searches and credits

Show me my saved searches.

How many credits do I have left, and how have I used them?

Best practices

Be specific with filters. Include job titles, seniority, location, industry, company size, technologies, and funding stage when relevant — the advanced search supports all of these.

Use company domains when finding emails. A domain (e.g. acme.com) usually improves match accuracy compared to a company name alone.

Search before you enrich. People search doesn't return emails or phone numbers. Use find/verify only on the rows you actually want to unlock.

Verify after you find. Pair aleads_find_email (or the bulk variant) with aleads_verify_email to confirm deliverability before you reach out.

Review credit-consuming actions before approving them. Most MCP clients let you require approval before specific tools run. A-Leads recommends approval for search, find, verify, and phone actions.

Mind the bulk limit. Bulk find and bulk verify accept at most 10 rows per call. For larger lists, split the work into batches.

Pricing and credits

There's no additional cost to connect to A-Leads MCP. Your A-Leads plan, permissions, and credits still apply.

Credit costs per action:

Action	Credit cost
Advanced search	1 credit per search with results
Company search	1 credit per search with results
Find email	1 credit per successful find
Bulk find email	1 credit per successful find (max 10 rows)
Verify email	1 credit per valid email
Bulk verify email	1 credit per valid email (max 10 rows)
Find phone	15 credits per successful find
Get saved searches	Free
Get user details	Free

Limitations

A-Leads MCP has the following limitations:

Search results don't include emails or phone numbers — use the find tools to retrieve contact details.
Bulk find and bulk verify accept a maximum of 10 rows per call.
Saved searches are paginated at 25 records per page, up to a maximum of 50 pages (1,250 records).
aleads_advanced_search and aleads_company_search always run a total search and return a trimmed set of fields per row.
Tool availability depends on your A-Leads plan, permissions, subscription status, and credit balance.

Privacy and security

A-Leads MCP uses OAuth 2.0 authentication with the authorization code flow and PKCE (S256). Your MCP client doesn't need an A-Leads API key for the standalone server setup.

Access is scoped to the A-Leads user who authorizes the connection. The assistant can only access data and perform actions that the authorized A-Leads user can access and perform.

You can revoke access from your A-Leads account settings at any time.

Before connecting A-Leads MCP to an AI client, review that client's privacy and data controls. If your client uses model training, turn it off before using A-Leads MCP.

Troubleshooting

Issue	What to do
A-Leads tools don't appear in my client	Confirm that your client supports remote MCP servers over Streamable HTTP with OAuth. Then disconnect and reconnect the A-Leads MCP server.
Authorization failed	Restart the OAuth flow, confirm you're signing in with the correct A-Leads account, and make sure your account is active.
"Invalid or expired subscription"	Confirm your A-Leads subscription is active. Search and enrichment require a valid subscription.
"Insufficient credits"	Search, find, verify, and phone actions consume credits. Check your credit balance with "How many credits do I have left?" or in your A-Leads account.
Search returns no results	Broaden your filters, remove overly specific criteria, or check spelling for names, domains, locations, and titles.
Find returns no email	A-Leads may not have a match. Provide more identifying details, such as full name plus the correct company domain.
Bulk action rejected	Bulk find and bulk verify accept at most 10 rows per call. Split larger lists into batches of 10.
A tool is missing from my client	Disconnect and reconnect A-Leads MCP. If the tool still doesn't appear, confirm the action is supported for your plan and client.

📘
Need help?
Contact A-Leads support at [email protected].