The setup prompt
Once your assistant is connected, this single prompt takes you from an empty project to a cookie banner published to test.
You will find it on the MCP page under Setup prompt, and in the dialog that shows a new key, already filled in with your project's domain. Copy it from there, or use it from here and put your own domain in.
The prompt
1. Start a scan if no scan is already running or completed. Continue with the steps below only once a scan is running or completed.
2. Set up the cookie banner for the example.com domain.
3. Configure the cookie banner according to the applicable law practices.
4. Add privacy policy link: {{YOUR_PRIVACY_POLICY_URL}}
5. Configure the geo-targeting rules with banner as per law.
6. Do not use em dashes for content.
7. Publish only to the test environment. If publishing to test is not possible, save it as a draft instead.
8. Finally, give me the script and the setup instructions for both the test and the live environment.
Replace example.com with your domain and {{YOUR_PRIVACY_POLICY_URL}} with the address of your privacy policy page.
What happens
It asks before starting the scan. A scan uses one from your plan allowance for the billing period, so the assistant tells you that and waits for you to agree.
The scan runs in the background. A small website usually finishes within a few minutes, larger ones take longer. The assistant checks back on it rather than blocking.
It categorizes what the scan found. Cookies come out of a scan uncategorized. The assistant sorts them into Necessary, Analytics, Marketing and the rest, and writes a plain language description for each.
It builds the banner. Colors, position, buttons and the wording visitors read, including the link to your privacy policy.
It sets geo rules. Which banner and which default cookie settings visitors get, by location, so that opt in applies where the law asks for opt in and opt out where it asks for opt out.
It publishes to test only. Real visitors are untouched. On plans without the test script the banner is saved as a draft instead.
It gives you the scripts. The test script for checking your work, and the live script for when you are ready.
The results in your dashboard
Everything the assistant did is in the dashboard, in the same places you would have done it yourself.
Cookies → Scanner
The scan it started, with the number of cookies and pages it found. Open the row for the full results.
Cookies → Cookie Inventory
Every cookie categorized, with a description. Each one shows who changed it last, and where the change came from, so an assistant's work is easy to tell apart from a person's.
Banner Configuration → Templates
The banner it built, with your colors and wording, published to test. Use the preview to see it exactly as a visitor would.
Banner Configuration → Geo Location Rules
The rules it created, with the locations each one covers and the cookie categories that start on there.
Banner Configuration → Scripts
The test and live script tags. Put the test script on a staging site, or on your live site behind a check, and confirm the banner looks right before you go further.
Going live
When you are happy with the test banner, publish to live. You can do it yourself on the Templates page, or ask the assistant to. Either way it is a deliberate step, and the assistant will tell you it replaces what real visitors see before it does it.
See Publishing to live and Installing the production script.