Connections and setup
The longer walkthroughs. Start with the install guide; come here when your kit asks for a connection. Each one gives the exact menu names, one step at a time.
What each kit needs
Some kits only need the AI. Others connect to an account you already have.
| Kit | Connections |
|---|---|
| Content Ideas & Script | None |
| Google & ChatGPT Ranking | WordPress (or paste in), Google Business Profile (paste in, or Windsor.ai) |
| Practice Website | WordPress, from the Claude or ChatGPT desktop app (or paste in) |
| Dentist Website | Wix’s connector in Claude (or paste into Wix) |
| Facebook & Instagram Ads | Meta Ads connector, Gmail for the Friday report |
| Google Ads | Windsor.ai, or a file you upload with Google Ads Editor (no cost); Gmail for the Friday report |
| Landing Page & Funnel | WordPress, or paste into GoHighLevel or any other builder |
| Edit and Post Viral Content | ffmpeg and a transcriber on your computer |
| Never Miss a Lead | GoHighLevel, through HighLevel’s connector, and WhatsApp on GoHighLevel, for the automatic half. Without them, the kit writes your front desk answers and the replies for the WhatsApp Business app, which costs nothing. |
If a kit notices a connection is missing, it won’t just fail. It tells you what’s missing, points you to the right walkthrough and offers the manual route while you sort it out.
WordPress Application Password
An Application Password is a separate password WordPress makes just for one tool. You can switch it off at any time without changing your real password.
- Log in to your WordPress admin. Click Users, then Profile.
- Scroll down to Application Passwords.
- In the name box, type Full Arch kit. Click Add New Application Password.
- WordPress shows the new password once. Copy it now.
- Put it somewhere safe that only your computer can read, never in the chat:
- The Claude or ChatGPT desktop app: make a small connection file that the kit reads without showing. Open a plain text editor (TextEdit on a Mac, then Format, Make Plain Text; Notepad on Windows) and type these three lines with your own website, your WordPress username, and the password inside double quotes, spaces and all:Save it in your “My practice” folder (the one withwp.env
WP_SITE=https://www.yourpractice.co.uk WP_USER=your-wordpress-username WP_APP_PASSWORD="abcd efgh ijkl mnop qrst uvwx"
practice-profile.md) with the namewp.env, notwp.env.txt. Then type Check my WordPress connection in the chat.On Windows with PowerShell, use Windows’ own settings instead: click Start, search Edit environment variables for your account, and under User variables click New three times, for
WP_SITE,WP_USERandWP_APP_PASSWORD(no quotes there). Close and reopen the desktop app. - Claude on the web, the desktop app chat, Cowork or a ChatGPT Project: skip the password, and never keep it in a Cowork folder. The kit gives you the finished post or page, and you paste it into WordPress as a draft. It takes a couple of minutes.
- The Claude or ChatGPT desktop app: make a small connection file that the kit reads without showing. Open a plain text editor (TextEdit on a Mac, then Format, Make Plain Text; Notepad on Windows) and type these three lines with your own website, your WordPress username, and the password inside double quotes, spaces and all:
Practice Website Kit: the same three lines go in a file called wordpress-connection.env instead. Make the Application Password with an Administrator login, because WordPress keeps the kit’s schema code only for Administrators. Then type Check my WordPress connection. The kit’s own INSTALL.md shows where to save the file.
The kit always publishes as a draft. You read it in WordPress and press Publish yourself.
If it doesn’t work:
- Your site must start with
https://. Application Passwords don’t work on a site without a security certificate. - Some security plugins switch Application Passwords off. In Wordfence, open Login Security, then Settings, and untick “Disable WordPress application passwords”. In Solid Security (formerly iThemes Security), open Settings, then Advanced, then WordPress Tweaks, and set REST API to Default Access.
- The spaces in the password are fine. Copy it exactly as shown.
- WordPress says “not allowed” or “401”: check the username is your WordPress username, not your email.
Wix connector
Wix has an official connector for Claude. With it switched on, Claude builds the pages the kit writes straight into your Wix account. You sign in on Wix’s own page, so no password goes into the chat.
- In Claude, click Customize, then Connectors. Click +, browse the directory and pick Wix.
- Click Connect and sign in to Wix, or create a Wix account there (you can start without paying).
- If Wix isn’t in the list: Customize, Connectors, +, Add custom connector, paste the address below, click Add, then Connect.Wix connector address
https://mcp.wix.com/mcp
- Start a new chat or Cowork task, click +, then Connectors, check Wix is switched on, and type Build my website.
The kit shows you every page before it builds anything, never deletes anything, and publishes only after it has listed the changes and you’ve said yes. Before your site names a practice, get that practice owner’s OK in writing: type Write my permission message and the kit drafts the email.
To use your own address and remove Wix’s ads you need a paid Wix plan. When we checked in October 2026, a UK comparison site listed the Light plan at about £9 a month billed yearly; Wix shows you the price for your country. Register the domain in your own name, so it stays yours whichever practice you work at.
No connector, or using ChatGPT? The kit writes every page and gives you click by click steps to paste them into the Wix editor yourself.
Meta Ads connector
- In Claude, click your name, then Settings, and under Customize click Connectors, then Browse.
- Find Meta Ads and click Connect.
- Log in with the Facebook account that manages your practice’s ads.
- Pick your practice’s ad account and allow access.
Meta’s connector is still being rolled out, and not every ad account has it yet. If you can’t see it, you lose nothing: the kit writes your whole campaign as a step by step brief that you build by hand in Ads Manager, and it can still read the results you paste in for the Friday check.
Everything the kit builds through the connector is created paused. Nothing spends until you switch it on yourself.
Windsor.ai
Windsor is the bridge that lets your AI read and build Google Ads campaigns, and post to your Google Business Profile.
- Go to windsor.ai and sign up.
- Click Connectors, then Google Ads, then Connect. Log in with the Google account that runs your ads and pick your ads account.
- If you want Google posts to go in directly, do the same for Google Business Profile.
- In Claude, click your name, then Settings, and under Customize click Connectors. Add Windsor and sign in with your Windsor account. If Windsor isn’t in the list, choose Add custom connector and paste the server address shown on Windsor’s MCP page.
No Windsor? You don’t need it. The Google Ads Kit makes an import file for Google Ads Editor, Google’s own desktop app, at no cost. You upload the file yourself. The walkthrough is inside the kit.
Gmail connector
- In Claude, click your name, then Settings, and under Customize click Connectors.
- Find Gmail and click Connect. Sign in with the email account you want the report sent to.
The Friday report is saved as a draft in your Gmail, addressed to you. If you’d rather it arrived in your inbox as a sent email, you can set the weekly task to approve that automatically. The report only ever goes to you.
GoHighLevel, with HighLevel's official connector
This connection is optional. It lets the kit check your build and, on the right plan, run the Monday lead review. HighLevel makes an official connector for Claude. It works in Claude chat, Cowork and Claude Code, you sign in with your HighLevel login, and there are no token files to make.
Before you connect it: the connection can let the kit read patient conversations, which can include health details. Only let it read conversations if your practice is on a Claude Team or Enterprise plan with a data processing agreement. On Claude Pro, use it for build checks only and run the weekly review from totals you paste in.
In Claude and Cowork
- In Claude, click your name, then Settings, and under Customize click Connectors. Click +, then Add custom connector.
- Call it HighLevel and paste this address, then click Add:Connector address
https://services.leadconnectorhq.com/mcp/anthropic/v2
- Click Connect and sign in with HighLevel. Pick your practice’s sub account (not the whole agency) and approve.
- In a chat or a Cowork task, click +, then Connectors, and switch HighLevel on.
- Type List my GoHighLevel pipelines. If you see them, you’re connected. If you see nothing, check you picked the practice’s sub account, not the agency, and that HighLevel is switched on under +, Connectors in that chat.
Claude Code uses the same connector when you’re signed in to the same Claude account. Type /mcp to check it’s there. If it isn’t, type this in the terminal, then /mcp in Claude Code to sign in with HighLevel:
claude mcp add --transport http highlevel https://services.leadconnectorhq.com/mcp/anthropic/v2
What the kit will and won’t do. The connector can read and write in HighLevel, including sending messages. The kit’s rules stay the same: it never sends a message, never deletes anything, and only creates or changes something in HighLevel after you say yes to that exact change. The pipeline, workflows, the AI Employee and WhatsApp are set up in the GoHighLevel screen, and the kit gives you a numbered checklist for those.
To cut the connection, go back to Settings, then Connectors under Customize, and disconnect HighLevel.
In the ChatGPT desktop app
HighLevel makes a matching official connector for ChatGPT and other OpenAI tools. You sign in with HighLevel the same way, so there is no key to copy and no file to edit.
- In the ChatGPT desktop app, open Settings, then MCP servers, then Add server.
- Name it leadconnector, choose Streamable HTTP, and paste this address as the URL. Save, then click Restart.Server address
https://services.leadconnectorhq.com/mcp/openai/v2/
- Click Authenticate next to it. Sign in with HighLevel, pick your practice’s sub account (not the whole agency) and approve.
- Open the desktop app in your practice folder and type List my GoHighLevel pipelines. If you see them, you’re connected. When the app asks to reach HighLevel, say yes for that site only. When it asks before using a HighLevel tool, approve
execute_operationonce each time, never for the whole session.
To cut the connection, remove leadconnector from the app’s MCP servers. The kit’s references/ghl-build.md, part 2.3, has the same steps. A private key from HighLevel is still there as an advanced option on the desktop apps (parts 2.4 and 2.5), but you don’t need it.
Before real messages from leads or patients go through it: sign GoHighLevel’s data processing agreement, and add a line to your practice privacy notice saying enquiries are handled in GoHighLevel and that an AI assistant may reply first. The kit’s GDPR checklist walks you through both.
WhatsApp on GoHighLevel
This is where most people get stuck, so take it slowly. You need three things before you start:
- Meta Business verification. Your practice verified in Meta Business Settings, under Security Centre. Meta checks your business documents, which can take a few days.
- A display name that matches your practice name. Meta approves it.
- A phone number that isn’t already on WhatsApp. If your practice number is on the WhatsApp Business app, it has to be removed from the app first, or you use a new number.
Then:
- In GoHighLevel, open your sub account, then Settings, then WhatsApp, and start the setup.
- Log in with the Facebook account that owns your Meta Business, and follow Meta’s steps: pick your business, add the number, confirm it with the code Meta sends.
- Wait for the display name to be approved. You can keep building while you wait.
- Ask the kit to Write my WhatsApp templates. It writes the messages Meta must approve before you can send them (the welcome, the reminders, the follow ups), in the format Meta’s review expects, with sample values filled in, so they are ready to submit. Submit them in GoHighLevel under WhatsApp templates.
The kit also writes the opt in wording for your forms. Only message people who have agreed to hear from you on WhatsApp.
ffmpeg and the transcriber
ffmpeg is the open source tool, at no cost, that does the actual video work. The transcriber turns speech into text so the kit knows where to cut. Both run on your computer, so the video file itself stays there. The words of the transcript and a few still frames go to your AI tool so it can check the edit, which is why no patient, record or screen should ever be in shot.
The easiest way: in the Claude desktop app, open the Code tab (Claude Code), pick your Practice Videos folder and type Run the video setup check. The kit checks what’s there, tells you what’s missing, and installs it with you, one step at a time, after asking you first. Everything it installs stays on your computer, so you do this once. Cowork runs in the cloud and can’t install tools on your computer, so use the Code tab (or the ChatGPT desktop app) for this kit.
On a Mac, one paste does it all. In Terminal, type bash ~/.claude/skills/video-fa/scripts/setup_mac.sh (for the ChatGPT desktop app, bash ~/.agents/skills/video-fa/scripts/setup_mac.sh) and press Return. It installs Homebrew, ffmpeg and Python and ends with the setup check. Allow about an hour the first time, most of it waiting. The kit’s INSTALL.md has the same steps.
If you’d rather do each step yourself:
Mac
- Open Terminal. Install Homebrew (an open source installer for Mac tools, at no cost) by pasting this line and pressing Return. It asks for your Mac password, which you type into Terminal, not into Claude. Nothing shows while you type; that is normal:If Homebrew ends with “Next steps” and two lines to run, copy and run them.Terminal, Mac
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
- Then type this. It can take ten minutes or more. It must be
ffmpeg-full: the plainffmpegcan’t burn in captions or convert iPhone HDR footage.Terminal, Macbrew install ffmpeg-full python
- Paste this line and press Return, so Terminal finds the full version:Terminal, Mac
echo 'export PATH="$(brew --prefix ffmpeg-full)/bin:$PATH"' >> ~/.zprofile
- Close Terminal and open it again.
Windows
- Open PowerShell and type these two lines, one at a time, accepting the prompts:PowerShell
winget install --id Gyan.FFmpeg -e winget install --id Python.Python.3.12 -e
- Close PowerShell and open it again.
Check it worked. Type ffmpeg -version. If you see a version number, go back to the desktop app and type Run the video setup check. When it asks to install the speech tools, say yes.
“ffmpeg: command not found”. Close the terminal and open it again. If it still isn’t found, type “Run the video setup check” in Claude Code and the kit will walk you through it. On a Mac, a message about “ass” or “zscale” means the plain ffmpeg is installed: run brew install ffmpeg-full and the PATH line above, then reopen Terminal.
Google Business Profile, by hand
- The kit writes your Google post and gives it to you.
- Go to business.google.com, or search your practice name on Google while logged in, and click Add update.
- Paste the text, add a photo of your practice or team (never an AI made image of a person), choose the button (Book or Learn more) and add your booking link. Click Post.
Set up a weekly check
Weekly checks only read your accounts. They write a report and never change anything. Changes happen only when you ask for them in a normal chat and say yes.
- Open Cowork in the Claude desktop app and click Schedule.
- Create a new task. Copy the task wording from your kit’s INSTALL.md. For the ads kits it reads:Weekly task
Run the Friday check from my ads kit. Read only: do not change anything in any account. Compare the last 7 days with the targets in my targets file, write the Friday report, and save it as a Gmail draft to me.
- Set it to run weekly, on Friday at 7am.
- On Friday morning, the report is waiting in your Gmail drafts.
Cowork runs in the cloud, so the weekly check runs with your laptop closed. It reads your practice profile and targets file, so if those sit in a folder on your computer, keep the Claude desktop app open when the task runs.
Weekly checks in the ChatGPT desktop app run only while your computer is on and the app is open. If you want them to run with your laptop closed, use Cowork for those.
The Never Miss a Lead Monday review is different. Reading the week’s patient conversations needs a Claude Team or Enterprise plan, which comes with a data processing agreement. On a personal plan such as Pro, paste in the week’s totals from GoHighLevel’s reporting instead, with no names or message text, and the kit writes the review from those. On Team or Enterprise, the review reads GoHighLevel through the HighLevel connector, so it can run as a Cowork scheduled task on Monday, set up the same way as the Friday check.
Which AI plan
The kits run inside an AI tool you already pay for. Here is what each tool needs.
| Tool | What you need | Roughly what it costs | Good for |
|---|---|---|---|
| Claude, on the web or the desktop app | A paid plan, with code execution switched on | Claude Pro is about £18 a month (when we checked in September 2026) | Every kit except Edit and Post Viral Content, including Never Miss a Lead with the HighLevel connector |
| Claude Cowork (inside the Claude desktop app, running in the cloud) | Claude Pro or above | Included in Pro | The kits that write, the Gmail, Meta Ads, Windsor.ai and HighLevel connectors, and the weekly checks. Not Edit and Post Viral Content |
| Claude Code (the Code tab in the Claude desktop app, or the terminal) | Claude Pro or above | Included in Pro | Every kit. The route for Edit and Post Viral Content and saving drafts straight into WordPress |
| The ChatGPT desktop app (Mac or Windows) | ChatGPT Plus or above | About £20 a month (when we checked in September 2026) | Every kit. The full route for ChatGPT users, using the manual routes where a connector isn’t available |
| ChatGPT, with a Project | ChatGPT Plus | About £20 a month (when we checked in September 2026) | The writing kits only: Content Ideas & Script, the words from Ranking, Landing Page and the two website kits, ads planning, every Never Miss a Lead message and the GDC & ASA Checker. No connections |
| Cursor, Gemini CLI, GitHub Copilot, Windsurf and other tools that read the Agent Skills format | Their own plan | Their own price | Any kit, installed with one command |
Which should I pick? If you’re starting from nothing, get Claude Pro and install the Claude desktop app. It covers every kit: chat and Cowork for the kits that write and the weekly checks, and the Code tab (Claude Code) for the kits that work on your computer.
Patient data: one rule for every kit
Before your first run, switch off model training. This keeps your practice’s work out of the AI company’s training data.
- In Claude: Settings, then Privacy, then switch off “Help improve Claude”.
- In ChatGPT: Settings, then Data controls, then switch off “Improve the model for everyone”.
- Never put anything that identifies a patient into a personal AI chat: name, date of birth, address, phone, email, NHS number or a photo of their face.
- Clinical notes or transcripts only go into Claude with every identifier removed and “Help improve Claude” switched off. For regular patient related work, we recommend a Claude Team or Enterprise plan, which doesn’t train on your chats and comes with a data processing agreement.
- Any tool that reads messages from new leads or patients (the WhatsApp assistant that answers new leads in GoHighLevel, or the Monday lead review) needs a data processing agreement with that provider and a line in your practice privacy notice.
- Recording a consultation needs the patient’s documented consent, a practice owned device, and deleting the audio once you’ve used it.
The writing kits don’t need any patient data. If you paste some in, they ask you to take it out, but that is a safety net, not a guarantee, so check before you paste.
Your practice profile, in full
You don’t need this before your first result. Each kit asks the two or three things its first job needs, gives you the result, then offers to remember your practice. That memory is one short file, practice-profile.md. You make it once, and every kit uses it. It holds ten things:
- Practice name and address
- Website, phone and booking link
- The dentist’s name, title and GDC number
- The treatments you want more of (up to five), with “from” prices if you publish them
- The areas you serve
- Opening hours
- Your tone in three words
- The words you never use
- Your Google Business Profile link
- The one thing patients most often ask
There are three ways to make it. Pick one.
Way 1 · Let the kit ask you (recommended). Type Set up my practice profile in any kit. It asks the ten questions one at a time. At the end it gives you the file. Save it.
Way 2 · Use your practice AI headquarters. If your practice already keeps its facts, brand and rules in one shared folder (chapter 9 of the ebook), point the kit at that folder and it writes the profile for you.
Way 3 · Fill it in yourself. Open practice-profile.template.md from the kit’s config folder, fill in each line and save it as practice-profile.md.
If anything changes, like a new treatment or a new price, tell any kit “update my practice profile” and it will rewrite the file.
The one command install
Bought a pack? The double click installer beside START-HERE does the same with no command. This is the way for a single kit, or if you prefer the terminal.
The quick way to install every kit in a pack at once. This needs Node.js. If you don’t have it, download it from nodejs.org (it costs nothing) and install it like any other app. Then open the folder where you unzipped your kits in the terminal and type:
npx skills add ./the-practice-pack -a claude-code -g
Run it from the folder that contains the-practice-pack (or the-dentist-pack). On Windows, Extract All usually puts it inside a folder with the pack’s full name, such as the-practice-pack, so open that one. Or open the pack folder itself and type npx skills add ./ -a claude-code -g.
Bought a single kit? Use the name of its folder instead, for example npx skills add ./content-fa -a claude-code -g. It lists what it’s about to install and asks you to confirm.
“npx: command not found”. Node.js isn’t installed. Download it from nodejs.org (it costs nothing), install it, close the terminal, open it again and retry.
Other AI tools
Open a terminal in the folder that contains the-practice-pack (see the one command install for where Windows puts it) and type:
npx skills add ./the-practice-pack
Pick your tools from the list it shows. It installs the kits into each one.
When things go wrong
“The upload failed” or “invalid skill”. Upload the zip exactly as you downloaded it. If you unzipped it and zipped it again, the folder inside may have the wrong name. Download it again from your order email and upload that.
The kit doesn’t start when I ask. Check the kit’s switch is on in Customize, then Skills. Start a brand new chat and type the kit’s first prompt.
“I can’t run code” or files won’t open. Code execution is switched off. Go to Settings, then Capabilities, and under Code execution and file creation switch on Cloud code execution and file creation.
I can’t find the Meta Ads connector. Your ad account may not have it yet. Use the brief route: the kit writes the campaign for you to build in Ads Manager.
WordPress says “not allowed” or “401”. See the WordPress walkthrough.
“npx: command not found” or “ffmpeg: command not found”. See the one command install or the ffmpeg walkthrough.
Still stuck? Email fullarch@drskots.com with a screenshot of where you are, and tell us which kit and which tool. We reply within two working days.