Enrow MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ENROW_API_KEY | Yes | Your Enrow API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_emailA | Find a professional email address from a name and a company domain or name. At least one of company_domain or company_name is required. Asynchronous: returns a search id, then poll get_email_result. |
| get_email_resultA | Retrieve the result of a previously launched email search |
| find_emails_bulkA | Find multiple email addresses in bulk (up to 5,000 per batch). Asynchronous: returns a batch id, then poll get_emails_bulk_result. |
| get_emails_bulk_resultB | Retrieve results of a bulk email search |
| verify_emailA | Verify if an email address is deliverable. Works on catch-all domains. Asynchronous: returns a verification id, then poll get_verification_result. |
| get_verification_resultA | Retrieve the result of a previously launched email verification |
| verify_emails_bulkA | Verify multiple email addresses in bulk (up to 5,000 per batch). Asynchronous: returns a batch id, then poll get_verifications_bulk_result. |
| get_verifications_bulk_resultB | Retrieve results of a bulk email verification |
| find_phoneA | Find a mobile phone number from a LinkedIn URL (recommended) or first name + last name + company. Asynchronous: returns a search id, then poll get_phone_result. |
| get_phone_resultA | Retrieve the result of a previously launched phone search |
| find_phones_bulkA | Find multiple phone numbers in bulk (up to 3,000 per batch). Asynchronous: returns a batch id, then poll get_phones_bulk_result. |
| get_phones_bulk_resultA | Retrieve results of a bulk phone search |
| get_account_infoA | Get your Enrow account info (credit balance and registered webhooks) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Every tool targets a distinct operation: find versus result retrieval, single versus bulk, email versus phone versus verification. There is no meaningful overlap between tool purposes.
Tool names follow a consistent verb_noun pattern: find_/verify_/get_ combined with clear resource names. Bulk variants consistently use _bulk, and result pollers consistently use get_*_result.
13 tools is well-scoped for the domain: single and bulk email finding, email verification, phone finding, async result polling, and account info. Each tool has a clear role.
The tool surface covers the full lifecycle of each async operation: launch a search, retrieve its result, and support bulk batches. Account info provides the necessary operational context. No obvious dead ends or missing core operations.