AI assistant overview
You can connect an AI assistant to a project and let it do the setup work with you. Ask it to scan your website, categorize the cookies it finds, write the banner text, set up geo rules for GDPR and CCPA, and publish the result to test. Everything it does shows up in your dashboard exactly as if you had done it yourself.
This uses MCP (Model Context Protocol), an open standard for connecting assistants to tools. Claude supports it, ChatGPT supports it through connectors, and so do a growing number of other clients.
How it works
Three steps, and they take about two minutes.
- Create a key. It carries your own permissions and is shown to you once.
- Connect your assistant. Paste the connector URL into Claude, ChatGPT, or any MCP client.
- Send the setup prompt. The assistant scans, builds your banner, and publishes it to test.
Start with Connecting an assistant.
What the assistant can do
Once connected, the assistant works on one project: the one its key was created in.
Your project. Read the domain, plan and verification state. Get the DNS TXT record that proves you own the domain, and check it once you have added it at your DNS provider. Read how much of your page view and scan allowance you have used this billing period.
Cookie scanner. Start a scan, cancel one that is running, list past scans and read the results of any of them. Set up, pause, or remove the recurring scan schedule.
Cookie inventory. List the cookies a scan found, with search and filters, and set the category and description on them. It cannot add or delete cookies. Cookies arrive through a scan, and that is true whether you work in the dashboard or through an assistant.
Banner customization. Create banners, rename them, change colors, position, margins and which buttons show, and write the text visitors read, in any language your plan supports. Publish a banner to test, or all the way to live. Delete a banner.
Geo targeting. See which locations your plan can target, read your current rules, and create, change or delete them.
Install scripts. Read the test and live script tags to put on your website.
Consent audit. Look up one visitor's consent history, and email yourself a CSV export of it.
What it cannot do
The assistant has no access to billing, plans, team members, organizations or projects themselves. It cannot invite anyone, change your plan, create a project, or read back a key. Anything in that list stays in the dashboard.
It asks before anything risky
Some actions cost you something or reach real visitors. For those, the assistant is required to tell you what will happen and wait for you to agree before it goes ahead:
- Starting a scan, because it uses one scan from your plan allowance
- Cancelling a running scan, because its results are lost
- Publishing a banner to live, because it replaces what real visitors see straight away
- Deleting a banner, and deleting or changing a geo rule, because geo rules have no draft stage
- Deleting the scan schedule
- Exporting consent records, because the CSV is emailed to you
Everything else, including editing a banner draft and publishing to test, happens without a prompt. Draft and test changes never reach real visitors.
Permissions
A key can only do what the person who created it can do.
Owners and Admins can change things, so their keys can too.
Users can view but not change, so a key created by a User can read your project, scans, cookies, banners, geo rules and scripts, and nothing more. The assistant is not even shown the tools that would change something.
Permissions are checked fresh on every request. If someone's role changes, or they leave the organization, their keys follow immediately with no extra step.
Your plan applies in the same way. If a feature is not on your plan, the assistant is told so plainly and moves on. Custom CSS, multilingual banners, geo targeting, the test script and scheduled scans all depend on your plan, and scans come out of your usual scan allowance. See Plans and pricing.
Seeing what was changed
Every cookie records who last changed its category and description, and whether that change came from the dashboard or from an assistant, including which key was used. You can see this on the cookie in your inventory, so an assistant's work is never indistinguishable from a person's.