Curve Compliance MCP: Ask AI About Your Ad Results
Curve MCP connects Claude, ChatGPT, Cursor and any MCP client to your campaign and conversion results. Patient-level data never leaves Curve Compliance.
Browse practical guidance on privacy-safe healthcare advertising, analytics, patient acquisition, and marketing compliance.
Curve MCP connects Claude, ChatGPT, Cursor and any MCP client to your campaign and conversion results. Patient-level data never leaves Curve Compliance.
Curve Compliance records sessions and builds heatmaps for healthcare websites under the same BAA as your conversion tracking, tied to your conversions.
A weekly agency reporting routine for clinic clients: completed-week KPIs per client, platform vs server-side conversions, anomaly rules, an AI draft and human
Approve an MCP connector only on a written record: BAAs for every hop, a tool-output inventory, the de-identification method, access, logs, incidents and a
Connect Claude to Google's read-only Google Ads MCP with no PHI: clean lead forms and Customer Match first, use a Read-only Google user, allowlist GAQL, log
A three-tier policy for connecting Claude to clinic ad data: what to allow, what to allow only under conditions, what to never connect, and how Curve MCP
Trustworthy cost per conversion by campaign: platform spend over one deduplicated count, one stated model and lookback, small counts withheld. Prompts for
Use Curve MCP for rounded weekly campaign numbers in your own AI client, and Curve Analyst in the app for people, revenue, breakdowns and this week's data.
De-identified MCP answers withhold small groups, round counts and block subtraction. How k-anonymity, completed weeks and HIPAA de-identification apply to ad
Set up the GoHighLevel MCP in a clinic: one sub-account per token, no contact or conversation scopes, counts not records, campaign questions to Curve.
No. No BAA covers Amazon Ads, its MCP server can create, edit and launch campaigns, and Amazon bars health-based targeting. Here is what to lock down.
No. Google's GA4 MCP server is read-only and runs locally, but Google signs no BAA for GA4 and the server moves page paths into an AI model's context.
No. In a clinic account the GoHighLevel MCP hands contacts, conversations, calendars and tags (all PHI) to an AI vendor that HighLevel's BAA does not cover.
No. Google's Ads MCP is a read-only connector with no BAA behind it, so clinic safety depends on what the ad account holds and which AI client reads it.
No. HubSpot has not named its MCP server or Claude connector as BAA-covered, and clinic contacts and notes are PHI. Keep HubSpot as CRM and use Curve for ad
No. Meta's Ads MCP has no BAA and can write to your ad account. What Claude sees, where health signals hide in Meta, and the safer pattern for clinics.
An MCP token for health data should belong to one person, reach one client, carry read-only scopes and expire in days. OAuth, personal tokens, rotation and
Log who called, which client and token, which tool and arguments, exactly what came back, and when. Keep records of what left for six years, and review them.
Before connecting AI over MCP, a clinic needs plain answers on host, reads, writes, AI vendor, BAAs, logs and revocation. Most ad connectors have no BAA, so
Agencies running clinic accounts through one AI client need per-client credentials and conversations, a BAA chain that reaches the AI vendor, and written
PHI leaks from an MCP round trip at six points: tool arguments, tool results, vendor logs, chat history, chained connectors and exports. Controls for each hop.
With MCP a model, not a developer, picks the ad data query at runtime, so PHI risk shifts to open-ended reads, the model vendor hop, injection and audit gaps.
Meta Ads MCP set up read-only for clinics: a view-only identity, Meta's agent rules locked to read-only, write tools blocked, clinical names cleaned out.
Meta and Google count different windows, view-throughs and modeled conversions, so both claim the same booking. Reconcile each against one first-party ledger.