Pyrsonalize ships an MCP server. Add it once as a connector and your assistant can run real lead-finding jobs — 5, 10, 20, 50 or 100 leads — read the results back with names, roles, companies and verified emails, and send follow-ups from your own connected inbox.
Works with Claude Code, Claude Desktop, claude.ai and ChatGPT.
Once the connector is on, these are ordinary chat messages. Your assistant picks the right tool, runs the job on Pyrsonalize, and reads the results back to you.
Find me 20 leads — I sell SEO services to hair salon owners in Chicago.
Get me 100 leads for my bookkeeping service, targeting e-commerce founders. Business emails only.
Show me the top 5 leads from my last search and draft a first-touch email to each.
Send that email to Dana from my Gmail — keep it under 90 words.
Seven tools, grouped into lead finding and email.
| Tool | What it does |
|---|---|
find_leads |
Starts a lead search from what you sell and who you sell to. Pick 5, 10, 20, 50 or 100 leads — the job stops as soon as it hits your number. |
check_lead_search |
Reports progress while the search runs, and how many leads are in so far. |
get_leads |
Returns the lead details: name, role, company, location, ICP match score, notes and email address. |
list_lead_searches |
Lists your recent searches so the assistant can pick up an earlier one. |
cancel_lead_search |
Stops a running search. Anything already found stays available. |
list_email_accounts |
Shows which of your mailboxes are connected and how many sends you have left today. |
send_email |
Sends a real email from your own connected Gmail or SMTP account, logged to your Pyrsonalize inbox with open and click tracking. |
Your quotas still apply. Email reveals draw on your daily lead-reveal allowance and sends draw on each mailbox's daily send limit — exactly as they do in the dashboard. An assistant can't spend more than you could yourself.
You'll need a paid Pyrsonalize plan and a paid Claude or ChatGPT plan (custom connectors are a paid feature on both).
Open Dashboard → AI Connector
and hit Generate key. That page then shows every command below
with your key already filled in — so you can copy one and paste it straight into your
assistant, with nothing to edit. The snippets on this page use a
YOUR_KEY placeholder instead.
Pick your assistant below and follow the steps.
Run this in your terminal, swapping in your key. Claude Code supports custom headers, which is the cleanest way to pass it:
Then confirm it connected:
You should see pyrsonalize listed as
connected. Inside a session, /mcp
shows its status and tools.
Add --scope user to the add command to
make the connector available in every project instead of just the current one.
That's it. Try this in a fresh chat:
A search normally takes one to a few minutes. Your assistant will start the job, check on it, and read the leads back once they're in. Larger counts take longer.
The send_email tool delivers through
the mailbox you connected — your Gmail via OAuth, or your own SMTP server. Nothing goes out from a
shared Pyrsonalize address, so replies land in your inbox and your domain keeps its reputation.
Sends are immediate and permanent. The tool is described to your assistant as an action that needs your explicit go-ahead, and both Claude and ChatGPT will ask you to approve the call — but always read the recipient, subject and body before you confirm.
That's almost always the key. Confirm you replaced YOUR_KEY
with the real value, that the key hasn't been revoked on the
AI Connector page, and that your
Pyrsonalize plan is active — the connector is premium-only.
Only one search runs per account at a time. Ask your assistant to check the running search, or to cancel it, and then start the new one.
You've used today's email-reveal allowance. It resets at midnight, or you can move to a plan with a bigger daily allowance. The leads themselves stay in your account either way.
Your Gmail authorisation expired. Reconnect the mailbox at Dashboard → Integrations and try again.
It's the only option in connector UIs that don't accept custom headers, and the request is always
over HTTPS. Treat the URL like a password: don't share it or paste it into a screenshot. Use the
Authorization header wherever your client supports
it, generate a separate key per assistant, and revoke any key you no longer use.
Yes. Your keys stay visible on the AI Connector page — click Show next to a key, or just copy the ready-made command. Because of that, treat access to your Pyrsonalize account as access to your keys: if anyone else has signed in, revoke and regenerate.
Still stuck?
Contact supportGenerate a key, paste one URL, and ask for leads in plain English.
Generate my API key