CookieYes MCP server
2026년 11월 12일 커밋AI 어시스턴트를 통해 쿠키 동의 배너 관리, 쿠키 스캔 실행 및 GDPR/CCPA 준수 여부를 직접 확인합니다.
다른 이름 cookieyes/cookieyes-mcp, mcp
- 스타
- 0
- Tools
- 10
- 다운로드, 30일
- —
- 최신 버전
- 1.0.2
- 마지막 커밋
- 2026년 11월 12일
- 라이선스
- MIT
CookieYes MCP란?
AI 어시스턴트를 통해 쿠키 동의 배너 관리, 쿠키 스캔 실행 및 GDPR/CCPA 준수 여부를 직접 확인합니다. 10개 도구를 제공합니다. 예: list_domains, get_website_details, get_embed_code.
프로젝트 README에서 생성된 요약
CookieYes MCP server 정보
CookieYes를 사용하면 AI 어시스턴트를 통해 쿠키 동의 배너를 관리하고 GDPR 또는 CCPA 준수 여부를 확인할 수 있습니다. 이 호스팅 방식의 원격 MCP server는 로컬 설치나 수동 빌드 없이 Claude, ChatGPT, Cursor, VS Code와 같은 도구를 사용자의 CookieYes 계정에 직접 연결합니다. 인증에는 PKCE가 적용된 OAuth 2.1을 사용하므로, 별도의 API key를 관리할 필요 없이 기존 계정으로 로그인하면 됩니다.
개발자는 제공되는 10가지 도구를 사용하여 도메인 목록 조회, 배너 활성화 여부 확인, 쿠키 스캔 실행 등 다양한 작업을 수행할 수 있습니다. 또한 write 도구를 통해 배너 레이아웃과 색상을 업데이트하거나 라이트/다크 테마를 전환하는 등 시각적인 조정도 가능합니다. 서버는 모든 플랜에서 작동하지만, 사용자 지정 hex 색상 설정이나 페이지 스캔 제한과 같은 특정 기능은 현재 사용 중인 CookieYes 구독 레벨에 따라 결정됩니다.
활용 사례
- 1배너 배포 확인특정 쿠키 동의 배너가 현재 웹사이트에서 활성화되어 있는지 어시스턴트에게 확인 요청을 합니다.
- 2개인정보 보호 준수 감사현재 웹사이트 설정이 어떤 특정 개인정보 보호법을 충족하는지 검토합니다.
- 3쿠키 탐지 수행AI에게 사이트 전체 크롤링을 지시하여 활성화된 모든 쿠키를 식별하고 분류합니다.
- 4배너 디자인 맞춤 설정자연어를 사용하여 동의 배너의 시각적 테마나 특정 버튼 색상을 변경합니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
CookieYes MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 CookieYes MCP 설치
$ claude mcp add --transport http mcp https://app.cookieyes.com/mcpCursor에 CookieYes MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://app.cookieyes.com/mcp"
}
}
}VS Code에 CookieYes MCP 설치
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "http",
"url": "https://app.cookieyes.com/mcp"
}
}
}VS Code CLI에 CookieYes MCP 설치
$ code --add-mcp '{"name":"mcp","type":"http","url":"https://app.cookieyes.com/mcp"}'Codex에 CookieYes MCP 설치
$ codex mcp add mcp --url https://app.cookieyes.com/mcpCodex config.toml에 CookieYes MCP 설치
~/.codex/config.toml
[mcp_servers.mcp] url = "https://app.cookieyes.com/mcp"
Gemini CLI에 CookieYes MCP 설치
$ gemini mcp add -s user --transport http mcp https://app.cookieyes.com/mcpGemini settings.json에 CookieYes MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"url": "https://app.cookieyes.com/mcp",
"type": "http"
}
}
}CookieYes MCP 도구 10
README에서 감지됨list_domainsget_website_detailsget_embed_codelist_bannersget_banner_statusupdate_banner_coloursupdate_banner_layoutget_compliance_statustrigger_cookie_scanget_scan_results
| list_domains | — | |
| get_website_details | — | |
| get_embed_code | — | |
| list_banners | — | |
| get_banner_status | — | |
| update_banner_colours | — | |
| update_banner_layout | — | |
| get_compliance_status | — | |
| trigger_cookie_scan | — | |
| get_scan_results | — |
자동 검사
2026년 11월 14일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능cookieyes/cookieyes-mcp is public and reachablegithub.com/cookieyes/cookieyes-mcp ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-12github.com/cookieyes/cookieyes-mcp ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음10 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨No tool named like delete, drop or exec통과
- 원격 엔드포인트가 MCP 핸드셰이크에 응답HTTPS endpoint answered 401 (sign-in required)통과
README
GitHub에서 보기CookieYes MCP Server
Manage cookie consent banners, run cookie scans and check GDPR / CCPA compliance — straight from your AI assistant.
Documentation · Get a free account · Support
Overview
The CookieYes MCP Server connects AI assistants and IDEs — Claude, ChatGPT, Cursor, VS Code, LobeHub and any other Model Context Protocol client — to your CookieYes account. Ask in plain language and your assistant checks whether your banner is live, scans your site for cookies, reviews which privacy laws you cover, or restyles your banner for you.
It is a hosted, remote MCP server. There is nothing to install, build or run: add the endpoint to your client and sign in with your CookieYes account.
| Endpoint | https://app.cookieyes.com/mcp |
| Transport | Streamable HTTP |
| Authentication | OAuth 2.1 with PKCE — sign in with your CookieYes account, no API keys |
| Plans | Every CookieYes plan, including Free |
| Capabilities | 10 tools · 6 prompts |
| Language | English |
| Official MCP Registry | com.cookieyes/mcp |
Contents
- Before you connect
- Tools
- Prompts
- Example requests
- Connect your client
- Security and privacy
- Plan limits
- Managing and revoking access
- FAQ
- Support
- License
Before you connect
- A CookieYes account. Sign up if you don't have one — the Free plan works.
- MCP access turned on. The account owner opens the profile menu → MCP access (direct link) and switches on Enable OAuth-based access. No client can connect until this is on. Anyone on the account can see the status — an MCP enabled badge on Organisations & Sites — but only the owner can change it.
- An MCP client that supports remote servers with OAuth.
Tools
Read-only tools never change your account. Write tools change your live configuration, so the assistant first confirms the website and banner with you, and most clients also ask you to approve the call.
Websites and setup
| Tool | Type | What it does |
|---|---|---|
list_domains |
Read-only | Lists the websites in your account with their plan, banner status and compliance status. Supports search and pagination. |
get_website_details |
Read-only | Shows details for one website, including its plan's cookie-scan page limit. |
get_embed_code |
Read-only | Returns the script tag that installs the CookieYes banner on your site. |
Banners
| Tool | Type | What it does |
|---|---|---|
list_banners |
Read-only | Lists a website's banners with their law (GDPR / CCPA), status, layout, position and theme. |
get_banner_status |
Read-only | Checks whether the banner is live on the site, when it was last detected, and whether it has been disabled. |
update_banner_colours |
Write | Switches the theme (Light, Dark, Auto-generated) or sets individual colours for the banner, buttons, links, toggles, the preference centre and blocked-content placeholders. Colours are hex values; the assistant converts names and RGB for you. |
update_banner_layout |
Write | Changes the layout (box, banner or popup), its position on the page, and the preference-centre style (centre, push-down, left or right sidebar). |
Compliance and scanning
| Tool | Type | What it does |
|---|---|---|
get_compliance_status |
Read-only | Shows which privacy laws are enabled (GDPR, CCPA and others), plus geo-targeting and IAB TCF status. |
trigger_cookie_scan |
Write | Starts a cookie scan — a full crawl up to your plan's page limit, or a custom scan of URLs you choose to include or exclude. |
get_scan_results |
Read-only | Returns the latest completed scan, with cookies grouped by category. |
Prompts
Ready-made, guided workflows. In clients that support MCP prompts they appear as slash commands or in a prompt picker.
| Prompt | What it does |
|---|---|
check_banner_setup |
Checks whether the cookie consent banner is active on a website. |
discover_cookies |
Scans a website and walks you through the cookies and trackers it finds. |
check_compliance |
Reviews a website's compliance configuration. |
monitor_domains |
Checks banner status across all of your websites at once. |
update_banner_theme |
Guides you through changing the banner theme or colours. |
customise_banner_layout |
Guides you through changing the banner layout, position or preference-centre style. |
Example requests
Check your setup
- "Show all my sites."
- "Is my cookie banner live on example.com?"
- "Which of my sites have an inactive banner?"
- "Give me the installation code for my site."
Compliance
- "Is my site set up for GDPR?"
- "Which privacy laws does my banner cover?"
Cookie scanning
- "Scan my website for cookies."
- "What cookies are on my site? Group them by category."
Banner design
- "Switch my GDPR banner on example.com to the dark theme."
- "Set the accept button to navy blue."
- "Move my banner to the bottom right as a box."
Connect your client
Every client uses the same endpoint, https://app.cookieyes.com/mcp. When you connect, you are sent to CookieYes to
log in, review the permissions and click Allow. When you see Your CookieYes account is now connected, return to
your client.
Install CookieYes from the LobeHub MCP marketplace, or add a custom MCP server with the URL
https://app.cookieyes.com/mcp (Streamable HTTP), then complete the CookieYes sign-in.
- Open Settings → Connectors.
- Search for CookieYes, select it and click Connect.
claude mcp add --transport http cookieyes https://app.cookieyes.com/mcp
Then authenticate from inside Claude Code with /mcp, or run claude mcp login cookieyes.
- Open Settings → Plugins → Browse plugins.
- Search for CookieYes and click Install plugin.
You can also click + in any chat, search for CookieYes and install it from there.
Open Settings → Tools & Integrations → MCP Tools → Add Custom MCP, and add:
{
"mcpServers": {
"cookieyes-mcp": {
"url": "https://app.cookieyes.com/mcp"
}
}
}
Cursor calls MCP tools in Agent mode.
Run MCP: Add Server from the Command Palette, choose HTTP, and paste the endpoint. Or edit mcp.json directly:
{
"servers": {
"cookieyes": {
"type": "http",
"url": "https://app.cookieyes.com/mcp"
}
}
}
Open Cascade MCP Registry from the command palette, click Edit config, and add to mcp_config.json:
{
"mcpServers": {
"cookieyes-mcp": {
"url": "https://app.cookieyes.com/mcp"
}
}
}
Save, then click Connect next to cookieyes-mcp.
Add to opencode.json in your project root:
{
"mcp": {
"cookieyes": {
"type": "remote",
"url": "https://app.cookieyes.com/mcp"
}
}
}
Then run opencode mcp auth cookieyes.
Add a remote (Streamable HTTP) MCP server with the URL https://app.cookieyes.com/mcp, keep OAuth as the
authentication method, then click Authenticate. Step-by-step instructions for each client — including Vercel Connect
and the Cloudflare AI Playground — are in the documentation.
Security and privacy
- OAuth 2.1 with PKCE. Your client receives a scoped access token. Your CookieYes password is never shared with it.
- Owner opt-in. Nothing can connect until the account owner turns on MCP access, and they can turn it off at any time.
- Confirmation before changes. The assistant confirms the website and banner before any write, and never changes several banners in one step without your approval. Keep your client's per-tool approval turned on and review write calls.
What the server can access: your websites and their banner configuration (status, layout, position, colours, compliance settings), and cookie scan results.
What it never accesses: personal data, consent logs or visitor data; cookie values, session data or user identifiers; your cookie policy and other legal text; billing details, passwords or team-member information.
See the CookieYes privacy policy and DPA.
Plan limits
The server works on every plan, but tools follow your plan's limits:
- Cookie scans — the number of pages and scans per month depends on your plan.
- Banner colours — Free plans can switch between the Light and Dark themes. Auto-generated themes and custom colours need a paid plan.
Managing and revoking access
- Disconnect one client: profile menu → MCP access → find the client under Connectors → Disconnect.
- Pause every client: the account owner switches off Enable OAuth-based access. Switching it back on restores access straight away.
- From your client: remove the CookieYes server in the client's own settings.
FAQ
Do I need to install or host anything? No. CookieYes runs the server. You only add the URL to your client.
Is this the same as the CookieYes connector in Claude or the plugin in ChatGPT? Yes. They are all the same hosted server; "connector" and "plugin" are what those apps call an MCP server.
Is it free? Yes, the server is available on every plan, including Free. Some tools have plan-based limits (see Plan limits).
My client says access is restricted. MCP access is turned off for that account. The account owner can turn it on under MCP access.
Which languages are supported? English.
Support
- Documentation: https://www.cookieyes.com/documentation/mcp-server/
- Email: support@cookieyes.com
- Contact: https://www.cookieyes.com/contact/
About this repository
This repository holds the public listing information for MCP directories such as LobeHub (lhm.plugin.json). It does
not contain the server's source code; the server is operated by CookieYes Limited.
License
The contents of this repository are released under the MIT License. Use of the hosted CookieYes service is governed by the CookieYes Terms of Service.
CookieYes MCP 질문
CookieYes MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --transport http mcp https://app.cookieyes.com/mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
CookieYes MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
CookieYes MCP는 어떤 도구를 제공하나요?
10개 도구를 제공합니다. 예: list_domains, get_website_details, get_embed_code, list_banners, get_banner_status.
별도로 설치하거나 호스팅해야 하나요?
아니요, 서버는 CookieYes에서 호스팅합니다. 제공된 엔드포인트를 MCP 클라이언트에 추가하기만 하면 됩니다.
CookieYes MCP server는 무료로 사용할 수 있나요?
네, Free 플랜을 포함한 모든 플랜에서 사용할 수 있습니다. 다만 일부 도구는 플랜에 따라 제한이 있을 수 있습니다.
계정 액세스를 어떻게 활성화하나요?
계정 소유자가 프로필 메뉴로 이동하여 MCP access를 선택한 후, Enable OAuth-based access를 켜야 합니다.
서버에서 지원하는 언어는 무엇인가요?
현재 서버는 영어만 지원합니다.