Clinic marketing playbooks and tools: Meta ads access, health ad rules, lead follow-up, care plans
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Facts about QuiroAds, the publisher of these tools: what the agency does, its four free agent skills and how to install them, its free report on the cost of a new chiropractic patient, and links to its services and contact pages. Use it only when the user asks about QuiroAds. lang: en (default) or es.
Language of the answer: en (default) or es.
Same as lang.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http clinic-marketing https://quiroads.com/mcp
Facts about QuiroAds, the publisher of these tools: what the agency does, its four free agent skills and how to install them, its free report on the cost of a new chiropractic patient, and links to its services and contact pages. Use it only when the user asks about QuiroAds. lang: en (default) or es.
| Argument | Type | Description |
|---|---|---|
| lang | string | Language of the answer: en (default) or es. |
| language | string | Same as lang. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"lang": {
"enum": [
"en",
"es"
],
"type": "string",
"description": "Language of the answer: en (default) or es."
},
"language": {
"enum": [
"en",
"es"
],
"type": "string",
"description": "Same as lang."
}
}
}Works out a health clinic's care plan numbers from its own monthly counts: first visit → report, report → plan, first visit → plan, plan completed, renewal and reactivation. Given the clinic's own plan options and pay-per-visit price, it adds the price per visit of each option and its saving against paying per visit, largest option first. It never suggests visit counts, frequency, plan length or prices. Counts and prices only: never send patient names or records.
| Argument | Type | Description |
|---|---|---|
| visit_1 | integer | Patients whose visit 1 (the assessment) was in the month counted: a count, not a percentage. |
| visit_2 | integer | Of those, patients who came to visit 2 (the report of findings): a count, not a percentage. |
| currency | string | Currency of the prices: EUR, GBP, USD or AUD. Without it, money is written as a plain number. |
| continued | integer | Of those reassessed, patients who continued after the reassessment (new phase or maintenance): a count, not a percentage. |
| reassessed | integer | Of those who started a plan, patients who reached the reassessment: a count, not a percentage. |
| reactivated | integer | Of those lapsed patients messaged, patients who booked again: a count, not a percentage. |
| plan_options | array | The clinic's own plan options (one to five), as it already offers them: the visits each includes and its total price. Leave it out if the clinic has none: options are never suggested. |
| started_plan | integer | Of those, patients who started a plan, as the clinic defines it: a count, not a percentage. |
| lapsed_messaged | integer | Lapsed patients the clinic messaged to come back: a count, not a percentage. |
| pay_per_visit_price | number | What the clinic charges for one visit paid on its own, in the currency given: with plan_options, it gives each option's saving against paying per visit. |
Works out a health clinic's lead follow-up metrics from its own weekly counts, per source (all, Meta, Google, website, phone, other): contacted ÷ leads, booked ÷ leads, attended ÷ booked and lead → patient, the median time to first response and, with ad spend, the cost per lead, per booking and per new patient. A metric without its counts comes back as pending with the count it needs; nothing is filled with averages. Counts only: never send names, phone numbers or other lead data.
| Argument | Type | Description |
|---|---|---|
| rows* | array | One week of the clinic's own counts, one row per source (each source once; all for every source together): the leads that arrived that week, and how many of them have replied, booked and come so far. Leave out any count the clinic does not have: it is never estimated. |
| currency | string | Currency of ad_spend: EUR, GBP, USD or AUD. Without it, money is written as a plain number. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"rows"
],
"properties": {
"rows": {
"type": "array",
"items": {
"type": "object",
"required": [
"source",
"leads"
],
"properties": {
"leads": {
"type": "integer",
"maximum": 1000000,
"minimum": 0,
"description": "Leads that arrived that week from this source: a count, not a percentage."
},
"booked": {
"type": "integer",
"maximum": 1000000,
"minimum": 0,
"description": "Of those leads, how many have a first visit booked: a count, not a percentage."
},
"source": {
"enum": [
"all",
"meta",
"google",
"website",
"phone",
"other"
],
"type": "string",
"description": "Where these leads came from: all (every source together), meta, google, website, phone or other."
},
"ad_spend": {
"type": "number",
"maximum": 10000000,
"minimum": 0,
"description": "What the clinic spent on ads for this source that week, in the currency given: it gives the cost per lead, per booking and per new patient."
},
"attended": {
"type": "integer",
"maximum": 1000000,
"minimum": 0,
"description": "Of those leads, how many came to the first visit («won»): a count, not a percentage."
},
"contacted": {
"type": "integer",
"maximum": 1000000,
"minimum": 0,
"description": "Of those leads, how many replied or spoke to the clinic: a count, not a percentage."
},
"median_first_response_minutes": {
"type": "number",
"maximum": 1000000,
"minimum": 0,
"description": "Time to first response, in minutes: from arrival (or from opening time, out of hours) to the clinic's first message or call; the week's median."
}
}
},
"maxItems": 6,
"minItems": 1,
"description": "One week of the clinic's own counts, one row per source (each source once; all for every source together): the leads that arrived that week, and how many of them have replied, booked and come so far. Leave out any count the clinic does not have: it is never estimated."
},
"currency": {
"enum": [
"EUR",
"GBP",
"USD",
"AUD"
],
"type": "string",
"description": "Currency of ad_spend: EUR, GBP, USD or AUD. Without it, money is written as a plain number."
}
}
}Returns the full text of one of four MIT-licensed playbooks (agent skills) for people who market health clinics, so the assistant can follow the method step by step: meta_ads_access_audit (who owns and controls a clinic's Meta ad account, Page, Instagram, dataset and WhatsApp), health_ad_compliance (reviewing an ad or landing page against Meta and Google policies and the health-advertising rules of Spain, the UK, the US and Australia; add country for that country's rules), lead_follow_up (a WhatsApp, SMS and call follow-up system for new enquiries) and care_plan_conversion (first visit, report of findings, care plans and retention). Each playbook says when its rules were checked.
| Argument | Type | Description |
|---|---|---|
| topic* | string | Which playbook: meta_ads_access_audit (who owns and controls a clinic's Meta ads setup), health_ad_compliance (reviewing an ad, post or landing page against Meta and Google policies and health-advertising rules), lead_follow_up (answering and following up new patient enquiries) or care_plan_conversion (first visits, care plans and keeping patients). |
| country | string | Only for health_ad_compliance: also return that country's rules (es Spain, uk United Kingdom, us United States, au Australia). |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"topic"
],
"properties": {
"topic": {
"enum": [
"meta_ads_access_audit",
"health_ad_compliance",
"lead_follow_up",
"care_plan_conversion"
],
"type": "string",
"description": "Which playbook: meta_ads_access_audit (who owns and controls a clinic's Meta ads setup), health_ad_compliance (reviewing an ad, post or landing page against Meta and Google policies and health-advertising rules), lead_follow_up (answering and following up new patient enquiries) or care_plan_conversion (first visits, care plans and keeping patients)."
},
"country": {
"enum": [
"es",
"uk",
"us",
"au"
],
"type": "string",
"description": "Only for health_ad_compliance: also return that country's rules (es Spain, uk United Kingdom, us United States, au Australia)."
}
}
}Scans the text of a health clinic's ad, post or landing page (up to 4,000 characters) for phrases that Meta and Google ad policies and the health-advertising rules of Spain, the UK, the US and Australia restrict: testimonials and reviews, promises of a cure, a guarantee or a result, superlatives, questions or statements about the reader's condition (Meta), before-and-after, deadlines and fear, and titles such as Dr. Each finding quotes the phrase with its rule, source link, certainty, severity and a safer pattern, and the result lists what a phrase scan cannot judge (images, the landing page, evidence, registration, offer terms). It is a first pass, not a review: it never says whether an ad can be published. Leave out patient names.
| Argument | Type | Description |
|---|---|---|
| text* | string | The ad text, post or landing page copy to scan (up to 4,000 characters). Leave out patient names. |
| country | string | The clinic's country, for its health-advertising law: es Spain (with the EU rules), uk, us or au. Without it only the platform rules are scanned. |
| language* | string | Language of the answer: es or en. The scan reads both languages either way. |
| platform | string | Where the ad runs. Without it both platforms' rules are scanned. |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"text",
"language"
],
"properties": {
"text": {
"type": "string",
"maxLength": 4000,
"minLength": 1,
"description": "The ad text, post or landing page copy to scan (up to 4,000 characters). Leave out patient names."
},
"country": {
"enum": [
"es",
"uk",
"us",
"au"
],
"type": "string",
"description": "The clinic's country, for its health-advertising law: es Spain (with the EU rules), uk, us or au. Without it only the platform rules are scanned."
},
"language": {
"enum": [
"es",
"en"
],
"type": "string",
"description": "Language of the answer: es or en. The scan reads both languages either way."
},
"platform": {
"enum": [
"meta",
"google"
],
"type": "string",
"description": "Where the ad runs. Without it both platforms' rules are scanned."
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 18, 2026.
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"visit_1": {
"type": "integer",
"maximum": 1000000,
"minimum": 0,
"description": "Patients whose visit 1 (the assessment) was in the month counted: a count, not a percentage."
},
"visit_2": {
"type": "integer",
"maximum": 1000000,
"minimum": 0,
"description": "Of those, patients who came to visit 2 (the report of findings): a count, not a percentage."
},
"currency": {
"enum": [
"EUR",
"GBP",
"USD",
"AUD"
],
"type": "string",
"description": "Currency of the prices: EUR, GBP, USD or AUD. Without it, money is written as a plain number."
},
"continued": {
"type": "integer",
"maximum": 1000000,
"minimum": 0,
"description": "Of those reassessed, patients who continued after the reassessment (new phase or maintenance): a count, not a percentage."
},
"reassessed": {
"type": "integer",
"maximum": 1000000,
"minimum": 0,
"description": "Of those who started a plan, patients who reached the reassessment: a count, not a percentage."
},
"reactivated": {
"type": "integer",
"maximum": 1000000,
"minimum": 0,
"description": "Of those lapsed patients messaged, patients who booked again: a count, not a percentage."
},
"plan_options": {
"type": "array",
"items": {
"type": "object",
"required": [
"visits",
"price"
],
"properties": {
"price": {
"type": "number",
"maximum": 10000000,
"minimum": 0,
"description": "Total price of this option, in the currency given."
},
"visits": {
"type": "integer",
"maximum": 1000000,
"minimum": 1,
"description": "Visits this option includes, as the clinic offers it: a whole number from 1."
}
}
},
"maxItems": 5,
"minItems": 1,
"description": "The clinic's own plan options (one to five), as it already offers them: the visits each includes and its total price. Leave it out if the clinic has none: options are never suggested."
},
"started_plan": {
"type": "integer",
"maximum": 1000000,
"minimum": 0,
"description": "Of those, patients who started a plan, as the clinic defines it: a count, not a percentage."
},
"lapsed_messaged": {
"type": "integer",
"maximum": 1000000,
"minimum": 0,
"description": "Lapsed patients the clinic messaged to come back: a count, not a percentage."
},
"pay_per_visit_price": {
"type": "number",
"maximum": 10000000,
"minimum": 0,
"description": "What the clinic charges for one visit paid on its own, in the currency given: with plan_options, it gives each option's saving against paying per visit."
}
}
}