CookiePilot – cookie banner & Consent Mode v2

io.cookiepilotPublished by cookiepilot.ioOfficial publisherv1.0.0Updated Oct 31, 2026

Add a GDPR cookie consent banner with Google Consent Mode v2 to any website, from the chat.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

Remote MCP endpoint that lets an assistant add a GDPR cookie consent banner with Google Consent Mode v2 to a website from chat.

What you can do
  • Add a GDPR-compliant cookie consent banner to a website.
  • Configure Google Consent Mode v2 alongside the banner.
  • Do this from the chat conversation rather than a separate dashboard.
  • No tool list is published, so the exact operations are not documented here.
When to use it
Useful when a site needs a cookie consent banner and Consent Mode v2 setup and you want the assistant to handle it conversationally instead of configuring it by hand.
Requirements
A remote MCP endpoint at mcp.cookiepilot.io over streamable HTTP; no authentication, environment variables or headers are declared. A website to apply the banner to is implied.
Before you install
The server is described as adding a banner to a website, which changes site content; review changes before publishing. No authentication is declared, so how the server identifies and authorizes the target site is unclear. Consent banners affect legal compliance, so verify the result meets your jurisdiction's requirements.

Installation

In SourceWeft

  1. Open CookiePilot – cookie banner & Consent Mode v2 in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.cookiepilot%2Fcookiepilot/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "cookiepilot-cookie-banner-consent-mode-v": {
      "type": "http",
      "url": "https://mcp.cookiepilot.io/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestOct 31, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.