LeadOcean + Gamma: build a deck from a website domain and enrich who to send it to

You give Claude a domain and a one-line offer. It reads the company, builds a Gamma deck that names the account, finds the buyer in LeadOcean and returns the deck link with a work email and its email_status. It runs inside Claude with two MCP servers connected: the LeadOcean MCP server and the Gamma MCP server. It handles one account per run. LeadOcean needs a free key's worth of records, no card.

The FullEnrich template does the same job with a downloadable skill and about 11 credits per contact (FullEnrich template, September 2026). This recipe swaps the contact step for LeadOcean.

How it works

1. Connect LeadOcean MCP. Add https://api.leadocean.io/mcp as a custom connector in Claude. Sign in with OAuth. No key is pasted.
2. Connect Gamma MCP. Add https://mcp.gamma.app/mcp. Gamma says MCP clients with OAuth and dynamic client registration can use it on any plan (Gamma developer docs, September 2026).
3. Give Claude the domain and the offer. Example: "Build a deck pitching our onboarding tool to acme.com and find the VP of Sales." Claude runs a few web searches to learn what Acme does.
4. Search the buyer by domain. Claude calls leadocean_search_leads with domain and a job level or function, limit 3. Each person returned is one record.
5. Pick one and enrich. Claude shows the candidates. You choose. It calls leadocean_get_lead with the person id to get the work email and its status.
6. Generate the deck. Claude sends the research and offer to Gamma, which builds a deck that names Acme on its slides.
7. Read the package. Claude returns the deck link, name, title and email. Check email_status before you send.

Configuration

Claude calls the MCP tools for you. The same two calls over HTTP, first search then enrich, suit a script or an n8n workflow:

curl -X POST https://api.leadocean.io/v1/people/search \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"domain": ["acme.com"], "jobLevel": ["VP"], "jobFunction": ["Sales & Business Development"], "limit": 3}'

curl -X POST https://api.leadocean.io/v1/people/enrich \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"person_id": "PERSON_ID_FROM_STEP_1", "reveal_email": true}'

Enum values are exact strings. List them free with leadocean_list_enum_values. There is no name plus domain lookup, so you search by domain first, then enrich by person_id.

Field mapping

Cost at 10,000 rows

10,000 targets cost 10,000 enrichments plus the search candidates, so about 40,000 records at 3 candidates each. Free gives 1,000 records for life, so about 250 targets. Solo at $97 a month covers 10,000 enrichments every 5 hours, so the run fits one plan, with no per-record bill (LeadOcean pricing).

The FullEnrich route costs about 11 credits a contact for email and mobile (FullEnrich template, September 2026). That is 110,000 credits. FullEnrich's price table stops at 100,000 credits a month and says contact sales above it (FullEnrich pricing, September 2026). For work email only at 1 credit (FullEnrich credits, September 2026), 10,000 credits is $499 a month, or $454 a month billed yearly (same pricing source).

Gamma's cost is a separate line. Gamma meters credits per slide and per image and publishes no fixed cost per deck (Gamma help, October 2026). Each API generation reports credits.deducted, so run 10 decks and multiply. An API key needs a paid Gamma plan; the MCP connector does not (Gamma developer docs, September 2026).

Troubleshooting

FAQ