Lusha MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Customize log level (e.g., DEBUG, INFO, WARN, ERROR, FATAL) | INFO |
| DISABLE_SSL | No | Disable SSL certificate verification (useful for development with self-signed certificates) | false |
| LUSHA_API_KEY | Yes | Your Lusha API key | |
| LUSHA_TIMEOUT | No | Timeout for Lusha API requests in milliseconds | 45000 |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| personBulkLookupA | Look up multiple or single persons information from Lusha API. REQUIREMENTS: Each person body must have a combination of: 1. LinkedIn URL, 2. full name + company domain/name, or 3. email address. IMPORTANT: Only use revealEmails or revealPhones parameters when specifically requested by the user for email-only or phone-only results. |
| companyBulkLookupA | Look up multiple or single companies information from Lusha API. REQUIREMENTS: Each company must provide at least one of: 1. Company name, 2. Company domain, 3. Fully qualified domain name (fqdn), or 4. Lusha companyId. Each company must have a unique 'id' field for identification in the response. |
| contactSearchA | Search for contacts using various filters in Lusha API. This is step 2 of the prospecting process. IMPORTANT: - After returning search results, ALWAYS ask the user if they want to enrich specific contacts - MCP sets page size to 25 by default (API's default is 20 if not specified) - Page/offset index starts from 0 - always use contactFilters tool to get the requirement filters for the contact search" - IMPORTANT:
|
| contactEnrichA | Enrich contacts from search results. This is step 3 of the prospecting process. IMPORTANT: - The requestId parameter MUST be the exact UUID received from the contactSearch response - ALWAYS ask the user which specific contacts they want to enrich before proceeding - revealEmails and revealPhones parameters are only available to customers on the Unified Credits pricing plan - Attempting to use these parameters on other plans will result in a 403 Unauthorized error - When neither parameter is used, the API returns both email addresses and phone numbers if available - IMPORTANT:
|
| contactFiltersA | Get available filter values for contact search. Supports: 1. departments - List of available departments 2. seniority - List of available seniority levels 3. existing_data_points - List of available data points 4. all_countries - List of available countries 5. locations - Search for locations by text (requires locationSearchText parameter) |
| companySearchA | Search for companies using advanced filters via Lusha's Prospecting API. This tool implements company search only.
|
| companyEnrichA | Get detailed company information from search results. WARNING: CHARGES CREDITS - always ask user first!
|
| companyFiltersA | Get available filter options for company prospecting. No credits charged. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/lusha-oss/lusha-public-api-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server