What is the Cookiebot MCP Server?
The Cookiebot MCP Server lets you connect an AI assistant to your Cookiebot account through the Model Context Protocol (MCP). Once connected, you can ask questions about your domains, consent banner configuration, consent statistics and cookies in plain language, and let the assistant help you classify cookies and write cookie descriptions.
The assistant works with your own Cookiebot account and only has the access that your user has. Changes made through the assistant are the same changes you could make in the Cookiebot Admin.
Please note: MCP (Model Context Protocol) is not the same as CMP (Consent Management Platform). The MCP server is a connection between your AI assistant and Cookiebot. Your Cookiebot CMP continues to run on your website as usual.
Important: AI assistants can make mistakes. Always review suggested cookie categories and descriptions before you confirm a change. The assistant's suggestions do not constitute legal advice.
Direct integration via URL
The Cookiebot MCP Server is currently available as a direct integration. This means you add the server address to your AI assistant yourself, instead of installing a ready-made connector from a directory.
The server address is:
https://mcp.cookiebot.com/api/graphql/mcpBefore you start
You need:
- A Cookiebot account with access to the domain groups and domains you want to work with.
- An AI assistant that supports remote MCP servers, already installed and signed in. This article describes the setup for:
- Claude Code (command line)
- OpenAI Codex CLI (command line)
- The Cookiebot MCP server address above.
Please note: The app-based options (Claude Desktop, Cowork) connect to the server from the provider's cloud, not from your computer. The server address must therefore be reachable from the internet.
Claude Code
Step 1: Open a terminal
Open a terminal on your computer.
Step 2: Add the Cookiebot MCP Server
Type the following command in the terminal and press Enter:
claude mcp add --transport http --scope user cookiebot-admin https://mcp.cookiebot.com/api/graphql/mcp
Step 3: Start Claude Code
Type claude in the terminal and press Enter.
Step 4: Sign in to Cookiebot
- In Claude Code, type
/mcpand press Enter. - Select the server you added (
cookiebot-admin). - Choose to authenticate. A browser window opens.
- Sign in with your Cookiebot account and approve the access request.
→ Authentication in Browser
Step 5: Check the connection
In Claude Code, type /mcp again. The server should be listed as connected, and its tools are available to the assistant. You can also type the following command in the terminal to see all your servers:
claude mcp list
Step 6: Ask your first question
Try a simple request, for example: "Which domain groups do I have in Cookiebot?"
Disconnecting
To remove the Cookiebot MCP Server, type the following in the terminal:
claude mcp remove cookiebot-admin
Removing the server deletes the sign-in stored on your computer. Cookiebot has no option to revoke the access yourself; an unused sign-in expires after 15 days, and every sign-in after 30 days at the latest.
OpenAI Codex CLI
Codex CLI reaches a remote MCP server in the same way as Claude Code.
Step 1: Add the Cookiebot MCP Server
Type the following command in a terminal and press Enter:
codex mcp add cookiebot-admin --url https://mcp.cookiebot.com/api/graphql/mcp
Step 2: Sign in to Cookiebot
Type the following command and press Enter. A browser window opens. Sign in with your Cookiebot account and approve the access request.
codex mcp login cookiebot-admin
Step 3: Check the connection
Type codex mcp list to see your servers, then start Codex with codex and ask your first question.
Step 4: Ask your first question
Step 5: Disconnecting
codex mcp logout cookiebot-admin
codex mcp remove cookiebot-admin
See the Codex MCP documentation for details.
What you can do
The MCP server provides the tools below. You do not need to call them by name; the assistant chooses the right tool based on your request.
Read your account and configuration
| Tool | What it does |
|---|---|
list_domain_groups |
Lists the domain groups on your account, including how long consent stays valid and whether consent is shared across the group's domains. |
list_domains |
Lists the domains in a domain group, with scan frequency and the date of the last scan. You can search by domain name. |
get_cmp_configuration |
Shows the banner settings of a domain group: targeted regions, default language, automatic language detection and the languages used in the banner and cookie declaration. |
Review consent statistics
| Tool | What it does |
|---|---|
get_consent_statistics |
Returns daily consent numbers for a domain and date range: opt-ins (active and implied), opt-outs, and opt-ins per category (Preferences, Statistics, Marketing). The assistant can calculate your opt-in rate for a period. |
Review and manage cookies
| Tool | What it does |
|---|---|
get_trackers |
Lists the cookies and trackers registered on a domain, both those found by the Cookiebot scanner and those you added manually, together with the date of the last scan. |
get_tracker |
Shows all details of a single cookie, including its purpose description in each language. |
set_tracker_category |
Sets the category of a cookie: Necessary, Preferences, Statistics or Marketing. Used to classify unclassified cookies or correct an existing classification. |
set_tracker_purpose |
Sets the purpose description of a cookie for one language, as shown to visitors in your cookie declaration (max. 2,000 characters per language). |
Please note: set_tracker_category and set_tracker_purpose change your live configuration. The category decides which consent a visitor must give for the cookie to be used, and descriptions are shown to your visitors in the cookie declaration. The assistant is instructed to ask for your confirmation before making a change. Claude Code and Codex also ask for your permission before they run a tool, unless you have turned this off.
Example prompts
- "Which domain groups do I have in Cookiebot, and which languages does each banner use?"
- "When was example.com last scanned?"
- "What was the opt-in rate for example.com in the last 30 days?"
- "Show me the cookies on example.com that are still unclassified."
- "Suggest a category for the cookie
_gaon example.com and explain why." - "Write a purpose description for this cookie in all active languages of the domain group."
Classifying cookies with the assistant
- Ask the assistant to list the unclassified cookies on your domain.
- The assistant suggests a category for each cookie. Review the suggestions.
- Confirm the cookies you agree with. The assistant updates the category in Cookiebot.
- Optionally, ask the assistant to write purpose descriptions. Because visitors see the cookie declaration in every active language of the domain group, the assistant proposes a description in each language. Review the wording and confirm.
The updated categories and descriptions are visible in your Cookiebot Admin in the Cookies & Reports tab.
Limitations
- The MCP server cannot create, delete or change domains or domain groups, and it cannot edit the banner design or settings. These tasks must be done in the Cookiebot Admin.
- It cannot start a new scan or change the scan frequency.
- Consent statistics cover up to one year per request.
- A domain list shows the first 2,000 domains by name. Use the search option to find others.
- The next scan date shown for a domain is an estimate, not a confirmed schedule.
- Sign-in with company single sign-on (SSO) is not supported yet.
- The Cookiebot MCP Server is not yet listed in any AI provider's connector directory, so it must be added by URL.
Comments
0 comments
Please sign in to leave a comment.