
Secure Privacy Mcp
io.github.secureprivacyPublished by GitHub account secureprivacyv1.1.1Updated Oct 24, 2026
An MCP server that automatically integrate GDPR-compliant cookie consent banners into websites
Overview
Lets an AI assistant install a Secure Privacy GDPR cookie consent banner on a website in one step, returning a script tag to embed.
- What you can do
- Install a cookie consent banner on a website in a single step
- Register the site's domain with Secure Privacy and return a domain ID
- Fetch and assign all available banner templates (design and functional)
- Generate the integration script tag and configure consent modes such as Google Consent Mode, Microsoft UET and Meta
- Detect existing Secure Privacy installations so the script tag is not duplicated
- When to use it
- Useful when you want an assistant to set up GDPR-compliant cookie consent for a site without manually walking through a vendor dashboard, and you are comfortable with Secure Privacy as the consent management provider.
- Requirements
- A local MCP client configuration that runs the mcp-remote proxy via npx, which connects to the hosted Secure Privacy endpoint; Node.js and an active internet connection are needed. No API key or credentials are required according to the README.
Installation
In SourceWeft
- Open Secure Privacy Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Secure Privacy MCP Server
A remote Model Context Protocol (MCP) server that enables AI agents like Claude Desktop, GitHub Copilot, and Cursor to automatically integrate GDPR-compliant cookie consent banners into websites with a single command.
Built on Cloudflare Workers, this MCP server provides a one-click solution for implementing Secure Privacy's cookie consent management platform, handling domain registration, template assignment, and script injection seamlessly.
What is MCP?
The Model Context Protocol (MCP) is an open standard that enables AI assistants to securely connect to external tools and data sources. It allows AI agents to perform actions on your behalf, making complex multi-step workflows as simple as a single conversational request.
Key Features
- One-Click Installation: Fully automate cookie banner deployment with a single AI command
- GDPR Compliant: Automatically configure compliant consent management
- Multiple Consent Modes: Support for Google Consent Mode (GCM), Microsoft UET, Meta, and more
- Template Management: Auto-assign all available cookie banner templates
- No API Key Required: Users don't need to provide any credentials
- AI Agent Compatible: Works with Claude Desktop, GitHub Copilot, Cursor, and other MCP clients
Available Tools
install_secure_privacy_banner
Fully install Secure Privacy cookie banner on a website in one step. This is the primary tool that orchestrates the entire installation process.
What it does:
- Registers a domain with Secure Privacy
- Assigns templates - Fetches and assigns all available cookie banner templates (design + functional)
- Generates the script tag - Creates the integration code for your website
- Configures consent modes - Sets up Google Consent Mode (GCM), Microsoft UET, Meta, and more
Response includes:
- Domain URL registered
- Domain ID for tracking
- Number of templates assigned
- Script tag for integration
- Confirmation of GDPR compliance
Example Usage
Simply ask your AI agent in natural language:
The AI will automatically use the Secure Privacy MCP to set everything up and provide you with the script tag to add to your website.
Installation
Claude Desktop
-
Install the mcp-remote proxy:
-
Open Claude Desktop and go to Settings > Developer > Edit Config
-
Add this configuration:
-
Restart Claude Desktop
-
Start using it! Ask Claude: "Add a cookie banner to my website"
GitHub Copilot (VS Code)
-
Install the mcp-remote package globally:
-
Open VS Code Settings (JSON) and add the MCP configuration:
-
Restart VS Code
-
Use Copilot Chat and ask: "Add Secure Privacy cookie banner to my site"
Cursor
-
Install the mcp-remote proxy:
-
Open Cursor Settings and navigate to the MCP configuration
-
Add the Secure Privacy MCP server:
-
Restart Cursor
-
Chat with the AI and request: "Install cookie consent on my website"
Troubleshooting
Connection Issues
If the MCP server doesn't appear in your AI client:
- Verify the URL is correct:
https://mcp.secureprivacy.ai/sse - Restart your AI client after updating the configuration
- Check that
mcp-remoteis properly installed by running:npm list -g mcp-remote - Make sure you have an active internet connection
MCP Not Showing Up
- Ensure the configuration file syntax is correct (valid JSON)
- Check for typos in the server URL
- Try reinstalling
mcp-remote:npm install -g mcp-remote - Verify your AI client supports MCP (check version requirements)
Script Already Exists
If you see a message that the script is already present, that's normal! The MCP automatically detects existing Secure Privacy installations and won't duplicate the script tag.
Development
Get Started
Deploy to Cloudflare Workers:
Or use the command line:
Customizing the MCP Server
To add your own tools to the MCP server, define each tool inside the init() method of src/index.ts using this.server.tool(...).
Testing with Cloudflare AI Playground
You can test your MCP server from the Cloudflare AI Playground:
- Go to https://playground.ai.cloudflare.com/
- Enter your deployed MCP server URL (
mcp.secureprivacy.ai/sse) - Use your MCP tools directly from the playground
Need Help?
For additional support:
- Secure Privacy Support: Contact support
- Documentation: Browse our docs
- Email: [email protected]
License
See LICENSE file for details.
Source: README.md at commit 824ac8d
Tools
0Version history
1- v1.1.1LatestSep 16, 2026
Score
40% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 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
- License10 pts
Declare a license in the repository or the registry entry.