CookieYes MCP Server

The Model Context Protocol (MCP) is an open standard that lets any AI assistant talk to an external service through a shared set of tools. The CookieYes MCP Server is our hosted server: your AI client (Claude, ChatGPT, Cursor, VS Code, and more) connects over HTTP, and it relays your requests to your CookieYes account.

1. Open your Claude Code terminal interface.

2. Add the server with the HTTP transport:

claude mcp add --transport http cookieyes https://app.cookieyes.com/mcp

claude mcp add --transport http cookieyes https://app.cookieyes.com/mcp

3. If prompted with This command requires approval. Do you want to proceed?, type y and press Enter.

4. Initiate the login workflow by running the following command in a new terminal:

! claude mcp login cookieyes

! claude mcp login cookieyes

1. Open the MCP servers settings panel and click + Add server in the Servers section.

2. In the Connect to a custom MCP window, switch the protocol from STDIO to Streamable HTTP.

3. In the URL field, enter

https://app.cookieyes.com/mcp

https://app.cookieyes.com/mcp

4. In the Name field, assign a name (e.g., cookieyes-mcp), then click Save.

5. Click Authenticate.

1. Open Settings (Ctrl+, / Cmd+,).

2. Go to Tools & Integrations > MCP Tools.

3. Click Add Custom MCP (or New MCP Server).

4. Add the following to mcp.json:

{
  "mcpServers": {
    "cookieyes-mcp": {
      "url": "https://app.cookieyes.com/mcp"
    }
  }
}

{
  "mcpServers": {
    "cookieyes-mcp": {
      "url": "https://app.cookieyes.com/mcp"
    }
  }
}

Note: Cursor calls MCP tools in Agent mode. Switch to Agent mode using the dropdown next to the model selector

Cloudflare AI Playground

Open the Run settings panel on the right side of the Cloudflare AI Playground dashboard.
In the MCP Servers section, click + Add.
In the input box, enter the server URL: https://app.cookieyes.com/mcp
Click the save icon next to the server URL field.
Click the Authenticating… button.

GitHub Copilot CLI

In your terminal, type /mcp add and press Enter to open the configuration wizard.
In the configuration wizard:

Name: provide a unique identifier as the server name.
Server Type: use the arrow keys to select 3. SSE (Server-Sent Events).
URL: paste https://app.cookieyes.com/mcp
Leave the remaining optional fields as default, then press Enter to submit.

Press Enter to start authentication.

opencode

1. Create opencode.json in the project root with the MCP server config:

{
  "mcp": {
    "cookieyes": {
      "type": "remote",
      "url": "https://app.cookieyes.com/mcp"
    }
  }
}

{
  "mcp": {
    "cookieyes": {
      "type": "remote",
      "url": "https://app.cookieyes.com/mcp"
    }
  }
}

2. Run OAuth authentication to connect the server: opencode mcp auth cookieyes

Visual Studio Code (VS Code)

Open Command Palette (Ctrl+Shift+P / Cmd+Shift+P).
Run MCP: Add Server.
Choose HTTP/Remote Server.
Paste your MCP URL: https://app.cookieyes.com/mcp

If you configure VS Code by editing mcp.json directly, use this format:

{
  "servers": {
    "cookieyes": {
      "type": "http",
      "url": "https://app.cookieyes.com/mcp"
    }
  }
}

{
  "servers": {
    "cookieyes": {
      "type": "http",
      "url": "https://app.cookieyes.com/mcp"
    }
  }
}

Windsurf

1. Open the command palette, search for Cascade MCP Registry, and select Devin: Cascade MCP Registry.

2. Click Edit config to open mcp_config.json.

3. In your mcp_config.json, paste your server configuration:

{
  "mcpServers": {
    "cookieyes-mcp": {
      "url": "https://app.cookieyes.com/mcp"
    }
  }
}

{
  "mcpServers": {
    "cookieyes-mcp": {
      "url": "https://app.cookieyes.com/mcp"
    }
  }
}

4. Save the file. The marketplace refreshes and lists your server under Installed with a Connect (or Error) status.

5. Click Connect next to cookieyes-mcp, then click Open in the modal that appears.

Zed Editor

Open your project in Zed.
In the agent chat sidebar, click the gear or plug icon in the top header to open the MCP configuration dropdown.
Select Add Custom Server.
Switch the configuration tab from Local to Remote.
In the configuration editor, change the some-remote-server key to cookieyes and set the url value to https://app.cookieyes.com/mcp.
Remove the optional auth and headers objects from the definition.
Click Add Server in the bottom-right corner.
Click Authenticate.

After you start the connection, you're redirected to the CookieYes authentication flow (the same for all clients). Log in or sign up, review the permissions, and click Allow. Once you see Your CookieYes account is now connected, return to your client.

Manage MCP Client sessions

Manage MCP Access

Category	Tool	Type	Description	Example Prompts
Domains & Setup	list_domains	Read-only	List all websites in your CookieYes account	– Show all my sites. – Which of my sites have an inactive banner?
	get_website_details	Read-only	Get detailed configuration for a specific domain.	– List my website details. – Show me the details for example.com.
	get_embed_code	Read-only	Get the JavaScript install code for your site	– Give me the installation code for my site. – How do I install CookieYes?
Banner Management	list_banners	Read-only	List all consent banners configured on a domain	– Show me all my banners. – Which banners are active on my site?
	get_banner_status	Read-only	Check if your cookie banner is live and active	– Is my banner live? – Is the installation code added to my site?
	update_banner_colours	Write/delete	Update banner theme and colours	– Change my banner on example.com to dark theme. – Set the accept button to navy blue.
	update_banner_layout	Write/delete	Change banner layout, position, and preference center style	– Move my banner to the bottom right – Change my banner position to top left.
Compliance & Scanning	get_scan_results	Read-only	View latest cookie scan results by category	– What cookies are on my site? – Show me all third-party trackers on example.com.
	get_compliance_status	Read-only	Check which privacy laws and geo-targeting are enabled	– Is my site GDPR compliant? – What regulations am I covered for?
	trigger_cookie_scan	Write/delete	Start a new cookie scan on your domain	– Run a new scan on my site – Scan my website for cookies.

Note

Most MCP clients, such as Claude, ask you to approve each tool call before it runs. Keep this enabled and review every call, especially write tools, which can modify your account. We also recommend connecting only verified clients or custom clients you trust. Remember that an account owner must enable MCP access before any client can connect.

1. Check banner status

2. Discover cookies on your site

3. Update banner appearance

4. Check compliance configuration

5. Monitor multiple domains

1. What is the CookieYes MCP Server?

2. Is the CookieYes MCP Server the same as a Claude connector?

3. Is the CookieYes MCP Server safe to use?

4. Does the CookieYes MCP Server work with the Free plan?

5. What CookieYes data does the MCP server have access to?

6. Does the MCP server support multiple languages?

CookieYes MCP Server

On this page

Overview

What can you do with CookieYes MCP?

Before You Begin

Connecting to the CookieYes MCP Server

Permissions & Access

Tools

Security & Privacy Considerations

Use Cases

Frequently Asked Questions

Have more questions?