Skip to content
Start free Sign in

Kukie.io MCP Server: AI Connector for Claude and ChatGPT

Your AI app, meet your sites.

The Kukie.io MCP server lets Claude, ChatGPT and your code editor read your sites and make the changes you approve.

See pricing How to connect your app

In plain words

Ask the way you ask a colleague.

Your app reads what it needs from Kukie.io, so the answer comes from your own sites, not from a guess.

  • “Which of my sites need attention this week?”
  • “Which cookies on shop.example.com still need a category?”
  • “Are my legal documents up to date?”
  • “What did my team change through AI this week?”

Changes

Follow one change from start to finish.

What happens when you ask your app to restyle the banner. Nothing changes until step 4.

  1. Step 1: You ask

    Use our green on the buttons and hide Reject all.

    Your app reads the banner's current settings from Kukie.io first.

  2. Step 2: Kukie.io previews it

    Each setting with its value now and after, one preview for each kind of change.

    And a warning when it matters: here, that Reject all would also disappear where your banner asks visitors to opt in. Nothing has changed yet.

  3. Step 3: Your app asks you

    Kukie.io marks every change tool as one that modifies your settings.

    So Claude, ChatGPT and other apps ask before they use it, unless you set them to approve tools on their own. Here, you keep Reject all.

  4. Step 4: Kukie.io makes it and records it

    With your role, your plan and the same checks as the Banner Editor.

    The record shows who asked and from which app. Select Revert in your dashboard, or ask your app, to put it back: every change except a scan can be undone.

What you can ask

Your sites, in plain words.

Seven questions to start with. Each answer comes from your own Kukie.io data.

  • “What did the last scan find, and what is new?”

  • “How did visitors answer the banner last month?”

  • “Is the banner on every page of example.org?”

  • “Does my privacy policy name every provider?”

  • “Was my shop down this month?”

  • “Look up consent record c7f2-91ab-4e0d.”

  • “Is Google Consent Mode set up on my shop?”

Your controls

You choose what it can reach.

You sign in on Kukie.io's own screen, not in the app, and decide there what the app may do.

  1. One organisation

    An app connects to one organisation at a time, and only once an owner or admin has turned AI access on there.

  2. The sites you pick

    All the sites you can open, or only the ones you tick. Sites added later stay out of a list.

  3. Read only, or changes too

    Allowing changes needs your password. Your role and site access are checked again on every request.

Scope

Clear about what it reaches.

It reads what your role lets you see and changes a careful set of banner settings. It deletes nothing of yours: an undo removes only a region rule or a language the connector itself added.

20

tools that read

Sites and their health, scans and cookies, providers and your privacy policy, banner settings and texts, region rules, consent figures, a consent record by its ID, uptime and the status of your legal documents.

10

tools that change, after a preview

Banner appearance, behaviour, languages and texts, region rules, integrations, Google's banner text, cookie categories, starting a scan and undoing a change.

0

tools that delete your data

Not your sites, cookies, consent records or documents. Billing, the team, API keys, moving a site and publishing legal documents stay in your dashboard.

Your app also gets a preview tool and 6 ready-made prompts, such as “Review all my sites” and “Get a site ready for Google Consent Mode”. Connect it for reading only, and it sees none of the tools that change.

Getting started

Connected in a minute.

There is nothing to install. You add one address to your app and sign in to Kukie.io.

  1. Step 1: Copy the address

    The MCP server address is the same for every app.

  2. Step 2: Add it to your app

    As a custom connector, a plugin or an MCP server, depending on the app.

  3. Step 3: Sign in and choose

    Your app opens Kukie.io. Choose the organisation, the sites and the access.

  1. 1

    Open chatgpt.com/plugins, select the plus button and then Add custom MCP server.

  2. 2

    Paste the MCP server address as the server URL and choose OAuth.

  3. 3

    Install the plugin and connect it, then choose the organisation, the sites and the access on Kukie.io.

Read the ChatGPT guide

MCP server address

https://app.kukie.io/mcp

The same address for every app. You sign in with OAuth, and there is nothing to install.

  1. 1

    Run the command in your terminal.

  2. 2

    Start Claude Code, type /mcp and choose kukie to sign in.

  3. 3

    Choose the organisation, the sites and the access on Kukie.io.

Read the Claude Code guide

Terminal

claude mcp add --transport http kukie https://app.kukie.io/mcp
  1. 1

    Add Kukie.io to ~/.cursor/mcp.json, or to .cursor/mcp.json in one project.

  2. 2

    Open Customize, find kukie and switch it on.

  3. 3

    Cursor opens Kukie.io. Choose the organisation, the sites and the access.

Read the Cursor guide

mcp.json

{
  "mcpServers": {
    "kukie": {
      "url": "https://app.kukie.io/mcp"
    }
  }
}
  1. 1

    Open the Command Palette, run MCP: Add Server and choose HTTP.

  2. 2

    Enter the MCP server address, and kukie as the server ID.

  3. 3

    A browser window opens Kukie.io. Choose the organisation, the sites and the access.

Read the VS Code guide

MCP server address

https://app.kukie.io/mcp

The same address for every app. You sign in with OAuth, and there is nothing to install.

  1. 1

    On the AI Connector page in your account, create an AI key: a name, its access and when it expires.

  2. 2

    Send the key as a bearer token from Muse, an n8n workflow or your own script.

  3. 3

    Give an automation read access only: nobody is asked before it acts.

Read the Muse and automations guide

Request header

Authorization: Bearer kk_ai_YOUR_KEY

The AI Connector is included on the Agency and Unlimited plans. Your AI app comes from its own provider, with its own plans, and what it does with the answers is covered by that provider’s terms.

Read the AI Connector guide

Questions about the AI Connector

Does Kukie.io run its own AI model?
No. Kukie.io runs no AI model. The AI Connector is a connection point for the AI app you already use, such as Claude or ChatGPT. The app and its provider do the thinking, and Kukie.io answers the app's requests with your data and makes only changes it has previewed first.
Which AI apps work with the AI Connector?
The AI Connector is a remote MCP server, built on the Model Context Protocol, at https://app.kukie.io/mcp. Any app that can add a remote MCP server and sign in with OAuth works with it, including Claude on the web, on the desktop and on mobile, ChatGPT, Claude Code, Cursor and VS Code. Apps and automations that cannot sign in that way, such as Muse or an n8n workflow, use an AI key you create in your Kukie.io account instead.
Can the AI app change my banner without asking me?
Not unless you let it. Kukie.io accepts a change only after the app has fetched a preview of exactly that change, and it 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, or use an AI key in an automation, nobody is asked, so give those read access only. Every change is recorded with its previous values, and every change except a scan can be undone in your dashboard or by asking the app.
What can the AI app see about my visitors?
Only totals, such as how many visitors accepted each category, plus a single consent record if you ask the app to look one up by its consent ID. That record shows the choice, the categories and services accepted, the date and time, the country and the banner version. The app never receives a visitor's IP address, visitor identifier, page address or a team member's email address.
What about text that comes from scanned pages?
Cookie names, page titles and other text a scan collects from websites can contain anything, including instructions written for an AI app. Kukie.io cleans that text and marks it as untrusted in every answer, so your app can tell it apart from Kukie.io's own data.
Who in my organisation can connect an AI app?
Any team member, with their own role and site access, which Kukie.io checks again on every request. AI access starts off for each organisation: an owner or admin turns it on, for reading only or for changes too, and can turn it off again or disconnect any app connected to the organisation. You disconnect your own apps on the AI Connector page in your account, and an app loses access at once. Changing your password or turning off two-factor authentication also ends every app and key on your account.

Bring your sites into the conversation.

Connect the AI app you already use. You choose the sites and what it may do, and every change is previewed and recorded.

See pricing Contact us

Related features

The AI Connector works across the tools you already use in Kukie.io. These are its neighbours.

See all features

More for people who run many sites

Guides for agencies and teams, and how AI rules meet cookie data.

See all articles

Disclaimer

Kukie.io provides tools to collect and record consent. It is not legal advice, and using it does not by itself make a website compliant with any law.

Listed on

Kukie.io on Trustpilot (opens in a new tab) Kukie.io on G2 (opens in a new tab) Kukie.io on SaaSHub (opens in a new tab) Kukie.io on AlternativeTo (opens in a new tab)