Productivity & Project Management · Wiza + Claude
Wiza MCP with Claude: Faster, Verified Lead Lists From LinkedIn
The short answer
Claude works with Wiza through the Model Context Protocol, an open standard that gives Claude secure, permissioned access to the tool. Once connected with an API key, Claude can search LinkedIn contacts, enrich prospect records and export verified emails and phone numbers, all from plain-language instructions. Your team reviews and approves each export before it reaches your CRM.
What is Wiza?
Wiza is a prospecting tool that extracts verified contact data from LinkedIn. It helps sales development teams, recruiters, founders and marketing staff build lead lists with accurate emails and phone numbers. Instead of copying profiles by hand, users search for the people they want to reach and export the contact details they need. It is widely used by teams that run outbound campaigns and need reliable, up-to-date prospect information.
How Claude connects to Wiza through MCP
The Model Context Protocol, or MCP, is an open standard that lets Claude use other software securely. Think of it as a universal adapter between Claude and a tool like Wiza. It lets Claude read information and take actions, with permissions your organisation controls.
Once Wiza is connected, Claude can search LinkedIn contacts by role, company, location or industry, enrich partial prospect records, and export verified emails and phone numbers. You describe what you need in ordinary language, such as asking for regional operations directors at mid-sized logistics firms, and Claude carries out the search and returns the results in a structured form.
Access is set up with least-privilege permissions, so Claude only does what your team allows. Consequential actions, such as bulk exports or pushing contacts into your CRM, can require a person's approval before they run. Audit logs record each step, so you can see what was searched, enriched and exported.
What you can automate
Targeted prospect list building
A sales development representative describes an ideal customer profile in plain language, for example finance directors at healthcare companies with 200 to 1,000 staff. Claude searches Wiza, filters the results and returns a clean list of matching contacts. The rep reviews the list before any export, saving hours that would otherwise go on manual searching.
Enriching existing lead records
Marketing teams often hold lists with names and company names but no verified email addresses. Claude can take these partial records, look up each person through Wiza and fill in missing details. Staff then check the enriched records for accuracy before they are used in a campaign.
Recruiter sourcing support
Recruiters can ask Claude to find candidates with a given skill set and seniority in a chosen region. Claude pulls matching profiles and contact details through Wiza and summarises the shortlist by experience. The recruiter decides who to contact and keeps full control of outreach.
Account expansion research
Customer success managers can use Claude to find additional decision makers within existing client accounts. Claude searches by department and job title, lists new contacts and notes which roles have not yet been engaged. This helps teams widen relationships beyond a single champion.
Weekly lead refresh
Sales operations teams can schedule a regular review of key target accounts. Claude checks for new contacts or changed job titles, updates the lead list and flags material changes for the account owner. Staff approve updates before they reach the CRM, keeping data current without constant manual effort.
An end-to-end workflow: Outbound campaign list to CRM
TriggerA sales manager approves a new target segment for the quarter.
Claude receives the ideal customer profile and searches LinkedIn contacts through Wiza.
Claude enriches each prospect record and removes duplicates already held in the CRM.
Claude scores the list against agreed criteria such as company size and seniority.
The sales manager reviews a summary and approves the export of the final list.
Approved verified contacts are pushed into the CRM, with source and date recorded.
The sales team receives a notification and begins outreach.
OutcomeTypically, the team builds a campaign-ready, de-duplicated list in a fraction of the time manual research takes, with every contact traceable to its source and approved before use.
How we set it up
Free automation audit
We review how your sales, recruiting or marketing teams currently build lead lists, and identify the steps worth automating with Wiza and Claude.
Secure connection
We connect Claude to Wiza using your API key, stored securely and granted only the permissions the workflow needs. Where a direct API route is preferred, we set that up instead.
Workflow design
We design the end-to-end flow across Wiza and your other systems such as Microsoft 365, your CRM or your ticketing tool, with clear approval points for exports and CRM updates.
Testing with real cases
We test the workflow against past prospecting requests and compare results with your current process, adjusting filters and checks until the output is reliable.
Launch and team training
We launch with monitoring and audit logs in place, then train your team on writing requests, reviewing results and approving exports.
Who benefits
- Sales development leaders
- Faster, more consistent prospect lists that match agreed targeting criteria.
- Sales representatives
- Less time searching profiles and more time spent on conversations with buyers.
- Recruiters and talent teams
- Quicker sourcing of candidate shortlists with contact details ready for review.
- Revenue operations and IT leaders
- Controlled, auditable access to prospect data that fits existing security policies.
Security and control
- Access uses least-privilege permissions, so Claude can only perform the actions your team has approved.
- Bulk exports and CRM updates require human approval before they run.
- Audit logs record each search, enrichment and export for review.
- Your API key is stored securely and can be rotated or revoked at any time.
- Outreach decisions remain with your people, and staff should follow applicable marketing and privacy rules before contacting anyone.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom must follow their respective marketing and privacy rules, including opt-out and consent requirements for outreach. In India, the Digital Personal Data Protection Act, 2023 governs how personal data is processed. Companies in the UAE and Saudi Arabia must meet their own data protection laws when handling contact information. We choose the hosting region for any custom application to help meet these 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 Wiza MCP server do?
The Wiza MCP server acts as a connector between Claude and Wiza. It lets Claude search LinkedIn contacts, enrich prospect data and export verified contact details when your team asks. Capabilities are set by the permissions you choose, and the connector runs only the actions your workflow requires.
Is connecting Wiza to Claude secure?
Security depends on how the connection is configured. We use least-privilege access, store your API key securely, require approval for bulk exports and keep audit logs of every action. This gives your team visibility and control, though no setup can remove all risk, so we also review your data handling rules together.
What can Claude do with Wiza once connected?
Typically, Claude can search contacts by role, company and location, enrich partial records, and export verified emails and phone numbers. It can also summarise results and help prepare lists for your CRM. The exact actions available depend on the workflow we design with you.
How long does setup take?
Many organisations complete a first working workflow within a few weeks, depending on how many systems are involved and how complex the approval process is. The free automation audit gives a clearer timeline for your situation before any work begins.
What Wiza plan or permissions do I need?
Generally, you need a Wiza account that supports API key access and the level of data access your workflow requires. Your administrator should confirm which permissions apply to your account. We check these details during the audit so the setup matches what your account allows.