Connect Your AI Assistant (MCP)

Connect your AI app to your Cookie Compliance account, and it can read your cookie banner and, when you ask, change it. The connection uses MCP (Model Context Protocol), the standard way AI apps add outside tools.

Which address do I use?

• You have a Cookie Compliance account and want the AI to read or change your banner: https://mcp.cookie-compliance.co/mcp/account. When you add it, your AI app asks you to sign in. A Cookie Compliance page opens in your browser and you approve it there. There is nothing to copy, and you never give your password to the AI.
• You are just trying it out, with no account: https://mcp.cookie-compliance.co/mcp. No sign-in. The AI can show a preview of a banner and help install one. It cannot change a real banner.

Full steps for Claude, ChatGPT, Claude Code, Cursor and others: manual.hu-manity.co/connect. If your app has no sign-in button for the server, the same page explains how to use an API token instead.

To check it worked, ask your AI: “Which Cookie Compliance sites can you see?” It should list your sites.

If it is not working

• It says it is connected but cannot see your sites. There are two causes:
  • You added the try-it-out address. Remove the server and add https://mcp.cookie-compliance.co/mcp/account instead.
  • You use an API token and it has expired or was revoked. Create a new token and replace the old one.
• It asks you to sign in again. This can happen from time to time. It is one click in the browser page that opens.
• You connected with an API token and it stopped working. Tokens expire. Create a new token the same way and replace the old one. See the API token steps. Never paste a token into a chat message: it goes in your app's connection settings only.
• It says it cannot apply a change because you have unpublished edits. Open the dashboard for that domain. Click Publish Now if those edits are what you want, or edit the draft to the values you want and then publish. There is no Discard button. The refusal is intentional: it avoids publishing work you have not reviewed.
• Banner colours flashed, then reverted. A live banner loads its published configuration and overwrites design set only on the page. Change appearance in the dashboard (Design) and publish, or ask the connected AI to change it, not in the install snippet.
• The banner shows but trackers still fire before a choice. The snippet is probably not first in <head>, a cache or optimiser moved it, or it was loaded from Google Tag Manager. See Where to put the Cookie Compliance snippet.

Before you change configuration

Consent on Update (Professional; off by default) is what asks returning visitors to choose again after a configuration change. Only a change to a consent-mode Categories Mapping (Google, Meta or Microsoft) re-asks; changes to blocking, consent categories or regional rules do not. Reverting the change does not undo a re-ask that already happened. Design and wording changes do not re-ask. Stored consent logs are kept either way. Read any re-ask warning before you confirm a configuration change, whether you make it in the dashboard or ask an AI to.

Still stuck? Contact support with your AppID and what the AI reported.

Related Articles

• Connect your AI assistant to Cookie Compliance (full steps)
• MCP server on cookie-compliance.co
• Where to put the Cookie Compliance snippet
• Cookie Compliance Capabilities Overview
• Cookie banner vs consent management platform