LeadMarina plugs into Claude as a custom connector — Anthropic's mechanism for adding remote tools to Claude over the Model Context Protocol (MCP). Once connected, you run lead generation from a chat: search local businesses by niche and city, inspect fully verified contact data, and push results to your CRM without leaving the conversation. The server lives at https://leadmarina.com/api/mcp (streamable HTTP) and authenticates with OAuth 2.1 using dynamic client registration, or with a LeadMarina API key as a bearer header. Its tools include search_leads, get_search_results, enrich_domains, query_leads, export_leads, list_searches, get_balance, list_views, list_integrations, and four automation tools (list_automations, create_automation, update_automation, delete_automation).

Custom connectors work on every Claude plan — Free, Pro, Max, Team, and Enterprise — with one caveat: Free Claude accounts are limited to one custom connector.

Connect on claude.ai

• Open Customize > Connectors in Claude's settings.
• Click +, then Add custom connector.
• Enter a name and the server URL: https://leadmarina.com/api/mcp.
• Leave Advanced settings empty — LeadMarina supports OAuth 2.1 with dynamic client registration, so no client ID or secret is needed.
• Click Add and complete the LeadMarina sign-in when prompted.

On Team and Enterprise plans, an Owner adds the connector first under Organization settings > Connectors; each member then connects their own LeadMarina account, so Claude only ever spends that member's credits and uses their export destinations.

In a chat, enable LeadMarina from the + button in the input area, under Connectors, and toggle individual tools on or off per conversation. Connectors added on claude.ai or Claude Desktop are also available in the Claude mobile app.

Connect in Claude Code

Add the server with one command: claude mcp add --transport http leadmarina https://leadmarina.com/api/mcp

Run /mcp inside a session to complete the OAuth sign-in; the panel shows the server as connected with its tools. For headless or scripted use, pass an API key instead — keys are available on every LeadMarina plan, including free: claude mcp add --transport http leadmarina https://leadmarina.com/api/mcp --header "Authorization: Bearer YOUR_LEADMARINA_API_KEY"

Add --scope user to make the server available across all your projects.

The workflow

• Search. "Find plumbing companies in Austin, Dallas, and Houston." Claude calls search_leads with your niche and cities — each call searches one city, within your plan's daily city budget (the web app's bulk search covers many cities in one run).
• Retrieve. search_leads usually hands back the first batch at once, and Claude pulls the rest with get_search_results, polling until enrichment is complete. Each verified lead carries up to 3 emails SMTP-checked and labeled safe/risky/invalid, up to 3 phones with line type (mobile/landline/VoIP/toll-free) and carrier, the owner's name where identifiable, social profiles (Facebook, Instagram, LinkedIn, X, YouTube, TikTok, Yelp), ratings, reviews, and the full business profile.
• Qualify. Ask follow-ups — "keep only leads with a safe email and a mobile number, sorted by rating." Claude answers with query_leads, which is free: filtering, sorting (by rating, review count, and other columns, ascending or descending), and re-querying delivered leads never spends credits — across everything you've collected, or inside one search by its search_id. For a shareable shortlist, ask Claude to render the results as an artifact — a table or report in the panel beside the chat you can iterate on. list_searches reviews past searches. And when you already have target websites, enrich_domains takes up to 10 website domains per call, runs each through the full verification pipeline at a cost of 1 lead per domain, and returns a search_id to poll with get_search_results — exactly like a regular search.
• Export. "Send these to Close." Claude calls export_leads with the same search_id and filters, so only the shortlist goes across — destinations are Close, GoHighLevel, Google Sheets, or a CSV/Excel/JSON file.

Keep prospecting inside a Claude Project: put your ICP, disqualifiers, and outreach rules in the project's knowledge and instructions, and every chat in that project qualifies leads by your rules without re-explaining them. On Team and Enterprise plans, share the project with your team.

Billing is a single meter: 1 lead = 1 delivered, fully verified business — enrich_domains draws from the same meter at 1 lead per domain. The LeadMarina free plan includes 100 leads; paid plans are 15,000, 65,000 or 240,000 leads per month, and Unlimited has no monthly quota at all — up to 210,000 leads a week. Ask "what's my balance?" any time — get_balance reports it.

Updates and dedupe

• Close and GoHighLevel are update-in-place, matched on a stable Google business identifier: re-exporting a search — from chat or a schedule — updates existing records and never creates duplicates. Google Sheets works the same way when the export goes into a spreadsheet LeadMarina created earlier. A CSV, Excel or JSON file, or a new spreadsheet, is a fresh copy every time.
• User-created data is never touched: notes, activities, custom field values, extra rows, and formatting survive updates. In GoHighLevel, tags are additive-only.
• Close: connection is via OAuth. Exports from Claude use your saved field mapping — run one manual Export → Close in the LeadMarina web app first to create it. That first export opens a field-mapping dialog: native fields map to Close built-ins; everything else maps to custom fields LeadMarina auto-creates, named after its columns. The mapping is saved and tracked by Close field ID, so renaming a field in Close doesn't break it.
• Google Sheets: exports go to a new spreadsheet or one LeadMarina created earlier. All columns export; columns you hide arrive hidden but keep updating. Row identity lives in a hidden column.

Automation

Any search can repeat once, daily, weekly, monthly, or yearly with any export destination, and Claude can set one up for you with create_automation — "run this search weekly and keep the Google Sheet updated." With Close, GoHighLevel or a spreadsheet LeadMarina created earlier as the destination, a scheduled search becomes a self-refreshing lead list. Every run spends leads. In Claude Code the same tools are scriptable for pipelines, and the REST API is available on every plan.

Troubleshooting

• Claude isn't calling LeadMarina. Confirm the connector is enabled for this conversation via the + button, and name LeadMarina or "local business leads" explicitly.
• A teammate can't add the connector. On Team/Enterprise, only an Owner can add custom connectors; members connect after the Owner adds it.
• Custom connector limit on Claude Free. Free accounts get one custom connector — remove another or upgrade.
• 401 in Claude Code. Run /mcp and re-authenticate, or check your API key header.
• Worried about re-export duplicates? In Close, GoHighLevel and a spreadsheet LeadMarina created earlier there are none — matching on the stable Google identifier means re-exports update, never duplicate. A file export is a new file each time.