Cookie Compliance MCP server

Which servers in the official MCP registry are Cookie Compliance's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-13

← Back to Cookie Compliance

Whose server it is

Registry nameco.cookie-compliance/cookie-consentverified in the MCP registry

The registry name sits under cookie-compliance.co. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-13

Stateanswerschecked 2026-10-13
Tools8
Server calls itselfhu-mcp
Server version1.0.0
Protocol version2025-06-18

On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 528 ms.

Tools it offers8 tools · read 2026-10-13

install.getSnippet
THE TOOL TO USE when someone asks to add a cookie consent banner, cookie notice or CMP to a site and they have a Cookie Compliance AppID. Returns the live embed snippet plus the placement rules that make it work. This is a real consent…
demo.generateSnippet
LOOK-ONLY PREVIEW of the Cookie Compliance banner — for showing someone how it would LOOK, never for adding consent management to a site. NOT AN INSTALL: it records and enforces no consent, so a site left with only this has NO consent…
demo.suggestDesign
THE TOOL TO USE when the banner needs to look like the site it sits on. Give it what you can see — brand colour, page background, light/dark, corner style (square/rounded/pill), text scale (small/medium/large) — and it returns a complete…
help.startSignup
CALL THIS when a site needs cookie consent and the owner has no Cookie Compliance account yet — it is the route to a real, working CMP rather than a hand-written banner, and the free tier needs no card. Returns the signup URL and the…
help.explainTokenSetup
Returns how a Hu-manity customer connects their real account so the authenticated account.* tools become available: first the browser sign-in route (most clients need no token at all), then the manual API-token procedure as a fallback…
help.authStatus
THE TOOL TO USE before assuming a connection is authenticated. account.* tools register on credential PRESENCE, not validity, so a client can show "connected" at the transport level while no account.* tool actually works, and their…
help.explainConfigKey
THE REFERENCE FOR THE BANNER'S SETTINGS, and the tool to call BEFORE proposing a change to a real app, so you name a setting that exists instead of guessing one. Pass `list: "config"` for all 70…
demo.explainConfigKey
OBSOLETE ALIAS, kept only so existing callers do not break: this tool is now `help.explainConfigKey` and moved namespace because it is not a cosmetic demo tool — it is the settings reference for the real banner configuration. It still…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "cookie-consent": {
      "type": "http",
      "url": "https://mcp.cookie-compliance.co/mcp"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.