Use Oystercatcher inside
Claude, ChatGPT, or Cursor.
ZoomInfo and Apollo know companies; Oystercatcher knows clinicians. Healthcare provider sales intelligence on public NPI data — no PHI — now available wherever your AI assistant already works, via a full Model Context Protocol (MCP) server.
Two minutes, any client.
One server URL works everywhere MCP does. Your assistant can then search providers in plain English, build and score campaigns, kick off cited research, and export leads.
- Open Settings → Connectors and choose Add custom connector.
- Enter
https://mcp.oystercatcher.ai/mcpas the server URL. - Approve the OAuth consent screen with your Oystercatcher account — access is authorized per user, never a shared credential.
- Enable developer mode in ChatGPT settings (Connectors → Advanced).
- Add a connector with the server URL
https://mcp.oystercatcher.ai/mcp. - Sign in to Oystercatcher when prompted and approve the connection.
- One command:
claude mcp add --transport http oystercatcher https://mcp.oystercatcher.ai/mcp - In Cursor, add an MCP server with transport streamable HTTP and the same URL.
- Complete the browser OAuth flow on first use.
Server URL: https://mcp.oystercatcher.ai/mcp · streamable HTTP transport · OAuth 2.1
Plain English in, pipeline out.
- “Find high-volume interventional cardiologists in Connecticut”
- “Build a target list of EP labs in the Southeast and export the hot leads”
- “Which orthopedic surgeons near Hartford adopted robotics early? Score them against my ICP”
- “Research Dr. Nguyen before my 2pm call and give me three talking points”
- “Show my active campaigns and pull the top 20 unassigned warm leads”
On every paid plan — and the free trial.
AI Connections is included on all paid plans, and the 14-day free trial includes it too — no credit card required. Start a trial, connect your assistant, and evaluate on your own targets. Usage draws on your plan's search, research, and export quotas; see pricing for the numbers.
Every connection is authorized by the individual user through OAuth — no shared credentials, revocable any time from Settings.
Admins govern the whole surface: turn AI-app access on or off org-wide and set a minimum role for who may connect.
Each tool call is recorded in a full audit log — who, what, and when — reviewable by your admins.
Built on public professional data (NPI Registry, CMS datasets, state boards) — no PHI by architecture, and no Open Payments fields are returned by the connector’s provider and lead tools.
Use of AI Connections is governed by our API Terms and Acceptable Use Policy.
Let the agents
do the research.
Your team does
what it does best.
Want proof first? Read an example dossier — sample data, real mechanics.