Sales & Customer Support · Icypeas + Claude
Icypeas MCP with Claude: Faster Lead Research and Verified Work Email Addresses
The short answer
Claude works with Icypeas through the Model Context Protocol, an open standard that lets Claude securely use software on your behalf. Once connected with an API key, Claude can request email discovery and verification, enrich lead records, and prepare outreach, with your team approving consequential actions before anything is sent.
What is Icypeas?
Icypeas is an email discovery and verification service used by sales professionals, recruiters, marketers and business development teams. It helps users find work email addresses for people at a company and check whether those addresses are likely to be valid before outreach. Teams use it to build cleaner prospect lists, reduce bounced messages and keep contact records accurate. It is typically used alongside a CRM or outreach tool.
How Claude connects to Icypeas through MCP
The Model Context Protocol, usually called MCP, is an open standard that lets Claude securely use other software. Think of it as a universal adapter between Claude and a tool. Through it, Claude can read information from Icypeas and take defined actions, with permissions your organisation controls.
Once connected, Claude can typically ask Icypeas to discover a work email address from a name and company, verify whether an address looks deliverable, and enrich a lead with the details your team needs. Claude can then summarise results or pass them to your other systems in the format you choose.
Permissions and approvals keep your people in charge. Access is limited to what the workflow needs, and an approval step can be set so that a person reviews contact lists or outreach drafts before any message goes out. Every request is logged, so your team can see what was done and when.
What you can automate
Prospect list building for sales reps
A sales rep supplies a list of target accounts and decision-makers. Claude asks Icypeas to find work email addresses for each contact, flags results that could not be verified, and returns a clean list ready for review. Reps spend their time on conversations rather than manual searching.
Lead enrichment before CRM import
Before new leads enter the CRM, Claude can check incoming records for missing or unverified email addresses and request verification through Icypeas. The enriched records are then prepared for import, so sales operations teams start with fewer gaps and fewer bounced messages.
Recruiter candidate and hiring contact outreach
Recruiters often need to reach hiring managers or referral contacts at specific companies. Claude can request email discovery for each named contact, verify the results, and draft a short personalised note for the recruiter to approve before sending.
Customer support account contact clean-up
Support teams often hold outdated contact details for account holders. Claude can review a list of accounts, ask Icypeas to verify current addresses, and produce a report of which records need updating. A support lead decides which changes to make in the helpdesk.
Event and webinar follow-up
After an event, marketing teams have attendee names and companies but incomplete emails. Claude can request discovery and verification for those attendees and group the verified contacts into a follow-up list segmented by interest, ready for the marketing team to approve.
An end-to-end workflow: New trade-show lead to verified CRM contact
TriggerA sales representative uploads a list of 200 badge-scan leads from a trade show to a shared folder.
Claude reads the list and identifies leads with a name and company but no email address.
Claude asks Icypeas to discover work email addresses for those leads and verify each result.
Claude separates verified addresses from unverified ones and adds a confidence note to each record.
The sales operations lead reviews the summary and approves the records to proceed.
Approved contacts are written to the CRM with their verification status, and unverified leads are placed in a manual research queue.
OutcomeSales teams typically start follow-up sooner, with a cleaner CRM and fewer bounced emails, while the team keeps control over which contacts are used.
How we set it up
Free automation audit
We review how your sales, recruiting and support teams find and maintain contacts today, and identify the workflows where Claude and Icypeas would save the most time. The audit is free and there is no obligation.
Secure connection using your API key
We connect Claude to Icypeas using your API key, stored in a secure credential vault rather than in shared documents. Access is limited to the actions your workflows require.
Workflow design with approvals
We design the end-to-end process across Icypeas and your other systems such as your CRM or Microsoft 365, and set the points where a person must approve contact lists or outreach.
Testing on real past cases
We test the workflow against past lead lists and contact records to confirm the results are accurate and that the approval steps behave as intended. Any issues are fixed before launch.
Launch, monitoring and team training
We launch with monitoring and audit logs, then train your team on how to use Claude with Icypeas day to day and how to review its output. Support continues after launch so the workflow can be refined.
Who benefits
- Sales development representatives
- Spend less time hunting for email addresses and more time on qualified conversations.
- Sales operations managers
- Keep the CRM cleaner with verified contacts and fewer bounced messages.
- Recruitment leads
- Reach hiring managers and referral contacts faster with checked addresses.
- Customer support and account managers
- Keep account contact details current with a clear review step before changes are made.
Security and control
- Access uses an API key stored in a secure credential vault, with permissions limited to the actions each workflow needs.
- People approve contact lists and outreach before anything is sent or written to your systems.
- Every request is logged in an audit trail so your team can review what was done and when.
- Outreach is designed around your organisation's own consent and anti-spam obligations, which remain your responsibility.
- Results are presented with verification status so reps know which addresses are uncertain.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom are typically subject to data and marketing communication rules that govern how contact data is collected and used, and we design workflows to support those obligations. In India, the Digital Personal Data Protection Act, 2023 shapes how personal data is processed, and in the UAE and Saudi Arabia local data protection laws apply to contact records. We can host the Claude application in India, the United States, the United Kingdom or the European Union, chosen to meet your requirements.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Icypeas MCP server do?
The Model Context Protocol server lets Claude use Icypeas through a defined set of actions. Typically this includes requesting work email discovery, verifying addresses and retrieving enrichment results. It acts as a secure bridge, so Claude works with Icypeas in the same way your team would, but through a controlled connection.
Is connecting Icypeas to Claude secure?
Security depends on how the connection is set up. We store your API key in a secure credential vault, limit access to the actions each workflow needs, require approvals for consequential steps and keep audit logs. Your security team can review the design before launch.
What can Claude do with Icypeas once connected?
Claude can typically request email discovery from a name and company, verify addresses, enrich lead records and summarise results. It can also prepare outreach drafts for review. Claude does not send messages on its own unless you configure and approve that step.
How long does setup take?
Many straightforward connections can be set up in a few weeks, including design, testing and team training. More complex workflows that span several systems take longer. The free automation audit gives you a realistic timeline for your situation.
What access do I need to use it?
Access is granted through an Icypeas API key, which your account administrator can provide according to your Icypeas plan and permissions. Your plan determines the volume of requests you can make, so we check this during the audit before designing your workflow.