You get a one-page brief on the person you are about to meet: a specific opener, talking points tied to their career, questions that cannot be Googled, and advice matched to their seniority. Claude writes it in the chat. LeadOcean supplies the facts through its hosted MCP server, so no key is pasted and nothing runs on your machine. This recipe needs a free LeadOcean account and a Claude plan with custom connectors: Free (one custom connector), Pro, Max, Team or Enterprise (Claude Help Center, October 2026).
How it works
- Connect LeadOcean to Claude. Open Customize, Connectors. Click + Add, then Add custom connector. Name it, paste
https://api.leadocean.io/mcp, click Continue and then Add. On Team and Enterprise an Owner adds it first. You sign in to LeadOcean with OAuth 2.1 (LeadOcean MCP docs, September 2026). - Save the brief as a standing instruction. Paste the prompt below into a Claude Project or a skill. It fixes the structure, so every brief looks the same.
- Trigger it. Send "Meeting with Jane Doe, Acme, in 30 minutes" or a LinkedIn URL or an email. Claude asks two questions: meeting type and your goal.
- Claude calls LeadOcean. It runs
leadocean_get_leadfor the person andleadocean_get_companyfor the employer. For a name without an identifier, it searches by company domain first, then enriches by person ID. - Read the brief. The result lands in the chat. Copy it into your notes or calendar invite.
Person enrich returns career history since 17 October 2026: past roles, education, certifications and awards. Past employers carry no company ID yet, so Claude matches them by name.
Configuration
The instruction text is the whole recipe. Adjust the sections to your meeting types.
You prepare meeting briefs. Ask for meeting type (sales, partner, investor,
customer, hiring) and my goal, then call leadocean_get_lead with reveal_email
false and leadocean_get_company. Write: 1) an opener that cites one specific
past role, 2) three talking points from career history, 3) three questions
not answerable from a web search, 4) tone advice for their seniority,
5) one risk. If a field is missing, say so. Never guess.The same two calls work over HTTP if you build your own agent. Test them from a terminal first.
curl -X POST "https://api.leadocean.io/v1/people/enrich" \
-H "x-api-key: $LEADOCEAN_API_KEY" \
-H "content-type: application/json" \
-d '{"linkedin_url":"https://www.linkedin.com/in/jane-doe"}'
curl -X POST "https://api.leadocean.io/v1/companies/enrich" \
-H "x-api-key: $LEADOCEAN_API_KEY" \
-H "content-type: application/json" \
-d '{"domain":"acme.com"}'Field mapping
| LeadOcean field | Brief section | Note |
|---|---|---|
contact_current_experiences[].job_title | Who they are | First entry is the current role. |
contact_current_experiences[].company_name | Who they are | Same entry as the title. |
resume_data.experiences[] | Opener, talking points | Past titles, companies and dates. |
resume_data.educations[] | Talking points | Present only when LeadOcean holds it. |
resume_data.certifications[], awards[] | Opener | Good for a specific, checkable compliment. |
| Company name, industry, size | Context | From leadocean_get_company. |
contact_emails[].status | Not in the brief | Skip the email unless you plan to follow up. |
Cost at 10,000 rows
10,000 briefs cost LeadOcean about 20,000 records: one person and one company each. A lookup that finds nothing is a 404 and costs nothing (LeadOcean docs, September 2026).
LeadOcean. Free is $0 for 1,000 records, for life, with no card. That covers about 500 briefs. Solo is $97 a month with 10k enrichments every 5 hours and 50k a week, so 10,000 briefs fit inside a week. Agency is $497 a month for teams (LeadOcean pricing).
Claude. The connector adds no LeadOcean charge, and you pay for your Claude plan as usual. On Claude Free, LeadOcean would be your one custom connector (Claude Help Center, October 2026).
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| Connector shows no tools | OAuth sign-in not finished | Disconnect, reconnect and approve on the LeadOcean page. |
| Claude says it found nobody | LeadOcean holds nothing for that identifier | Try the LinkedIn URL, then the email. A miss is free. |
| Brief has no past roles | Career history is held only when present | Claude should say so. Keep "never guess" in the instructions. |
| 402 after many briefs | The 1,000 free records are spent | Move to Solo or Agency. |
| Wrong person on a common name | Name matched without a company | Give the company domain or LinkedIn URL. |
FAQ
Do I need a skill, or is a Project enough?
A Project with the instruction text works. See the call prep brief skill and the meeting prep skill.
Does it work in ChatGPT or Cursor?
Yes. The MCP URL is the same. In ChatGPT, add it as a custom MCP server at chatgpt.com/plugins, then type @ in a chat to select it. See LeadOcean in ChatGPT and the MCP overview.
Can it pull a phone number for the meeting?
Yes, through leadocean_find_phone, which costs one record. Add it only when you need to dial in.
I want a ready-made prompt for discovery calls.
Use the discovery call prep prompt. It runs in any MCP client.
Back to all integrations. See pricing.
Prep your next meeting on real data. Start free.
Free to start. No credit card. 1,000 records to spend whenever you like.
Get your free API key →