The AI Connector is the Kukie.io MCP server. It lets an AI app you already use, such as Claude or ChatGPT, read your Kukie.io sites and, if you allow it, change banner settings after previewing each change. Ask it which sites need attention, what a scan found or how visitors answer your banner, and it can answer from your own data.
The AI Connector is included on the Agency and Unlimited plans. See the pricing page for what each plan includes. Kukie.io runs no AI model: the model belongs to the app you connect.
Before you start
- Your organisation is on a plan that includes the AI Connector.
- Your organisation's AI access is on, or you are an owner or admin. It starts off, and an owner or admin turns it on (see AI access for your organisation).
- Your AI app can add a remote MCP server (often called a custom connector) and sign in with OAuth. Apps that cannot sign in that way use an AI key.
Connect an app
- In your Kukie.io account, open the account menu and select AI Connector.
- Under Connect an AI app, copy the MCP server address:
https://app.kukie.io/mcp - Add the address to your AI app. The steps for each app are in Claude, ChatGPT, Claude Code and Cursor and VS Code.
- Your app opens Kukie.io to sign in. Check the address at the top: it shows where the app will send you back, in large type.
- Choose the Organisation, then the Sites: All sites you can open, or Only the sites you choose. With a list, sites added later stay out until you connect again.
- Choose the Access: Read only, or Read and make changes. To allow changes, confirm your password.
- Select Allow access. Kukie.io sends you back to your app and emails you that an app was connected.
The app works with your role and your site access, which Kukie.io checks again on every request. If your role is lowered or you leave the organisation, the app loses that access at the same moment.
What the app can read
- Your plan's limits and features, and what the connection is allowed to do.
- Your sites: status, the embed code, languages, integrations and the issues that need attention.
- Scan results, cookies, the providers found and the policy alignment check.
- Banner settings and texts as visitors get them, and region rules.
- Consent figures as totals, the same as the Analytics page shows.
- One consent record, if you give the app its consent ID: the choice, the categories and services accepted, the date and time, the country and the banner version.
- Whether your legal documents are published and up to date, but not their text.
- Uptime status, on plans that include uptime monitoring.
- The history of changes made through the connector, with the display names of the team members who made them.
The app never receives a visitor's IP address, visitor identifier or page address, or a team member's email address. Text taken from scanned websites, such as a cookie description, is cleaned and marked as coming from a third party before the app sees it.
How changes work
A connection with Read and make changes can change the banner's appearance, behaviour, languages and texts, turn integrations on or off, add or change region rules, apply Google's banner text, categorise up to 100 cookies at a time and start a scan. Every change takes the same steps:
- The app asks Kukie.io for a preview. It lists each setting with its value now and after, and any warning, such as a Reject all button that would be hidden.
- Kukie.io marks every change tool as one that modifies your settings, so apps such as Claude and ChatGPT ask you before they use it. If you set your app to approve tools on its own, nobody is asked: keep such apps on read-only access.
- Kukie.io makes the change through the same checks as the dashboard, with your role and your plan, and records it with its previous values.
A preview is good for one change and expires after 15 minutes. If someone changes the same settings in the dashboard in the meantime, the change is refused, so nothing is overwritten by surprise. A connection can make 60 changes an hour, an organisation 30 every 10 minutes, and a site can be scanned through the connector 3 times a day.
The connector cannot delete sites, cookies, consent records or documents, and it never reaches billing, team members and roles, API keys, site transfers or the writing and publishing of legal documents.
Review and undo a change
- Open Site Settings for the site and select the AI changes tab, or open the AI Connector page and go to AI changes.
- Find the change. Each row shows the app, the person, the time and every setting before and after.
- Select Revert, then Undo change.
You can also ask the app to undo it. An undo is refused if the setting was changed again since, so a later edit is never overwritten. A started scan cannot be undone. Reverting needs neither the plan nor the organisation's AI access.
AI access for your organisation
Organisation owners and admins choose what AI apps may do in the organisation, under AI access for this organisation on the AI Connector page:
- Read and make changes: apps can read and, where the person who connected allowed it, make changes.
- Read only: apps can read but not change anything. Connections stay.
- Off: no app or key can use the organisation. Turning access off disconnects every connection and key, and access turned off there is turned on again only there.
AI access starts off. Until someone chooses a level, it turns on when an owner or admin chooses one there, connects the first AI app or creates the first AI key: the access they choose for that app or key becomes the organisation's. Other members see that AI access is off and can ask an owner or admin to turn it on.
Owners and admins also see every member's connections and keys under Team connections, and can disconnect any of them.
Disconnect an app
- Open the AI Connector page.
- Under Your connections and keys, select Disconnect next to the app.
The app loses access at once. To use it again, connect it again from the app. Changing your password or turning off two-factor authentication ends every app and key on your account, and a connection not used for 90 days ends by itself.
What Kukie.io keeps, and what your app's provider receives
- A record of each connection, for as long as your account exists.
- A log of each request: the tool used, the outcome, the time it took and the size of the answer, never the question or the answer. It is kept for 90 days.
- Each change with its settings before and after, kept for 180 days so it can be reviewed and, except a scan, undone.
What your AI app does with the answers is up to the app and its provider, under the terms you agreed with them. The provider is a recipient you choose, not a Kukie.io sub-processor. If your AI app's plan lets its provider use your conversations, check that this suits you before you connect. Our Privacy Policy and Data Processing Agreement (Annex I, item 7) describe what can leave Kukie.io. This article is information, not legal advice.
