Add a cookie consent banner that blocks trackers before consent and records proof of consent.
The publisher's own URL. Not a PlugMCP endpoint.
https://mcp.cookie-compliance.co/mcp
Claude opens with the name and URL filled in. You still confirm it there.
claude mcp add --transport http co.cookie-compliance-cookie-consent https://mcp.cookie-compliance.co/mcp
Run in a terminal.
{
"mcpServers": {
"co.cookie-compliance-cookie-consent": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.cookie-compliance.co/mcp"
]
}
}
}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchAdd a cookie consent banner that blocks trackers before consent and records proof of consent.
README is not crawled yet. No repository on file.
No tool list yet. Remote servers get one after the first health check.