MCP.so
Sign In

ConsentStack MCPVerifiedFeatured

@ConsentStack

About ConsentStack MCP

ConsentStack's hosted MCP server lets an AI agent set up and run cookie consent end to end: create a site, configure and publish the banner, get the install snippet, run a compliance scan, and categorize the trackers it finds. Streamable HTTP with OAuth 2.1, so there are no API keys to create or paste. Included on every plan, including the free tier.

Connection details

https://app.consentstack.io/api/mcp

Setup

claude mcp add consentstack --transport http https://app.consentstack.io/api/mcp

Tools

No tools detected

Fetch the live tool list directly from this server's endpoint using the button above.

Overview

Set up and run GDPR and CCPA cookie consent from your AI agent. Create a site, publish a cookie banner, get the install snippet, run a compliance scan, and categorize the trackers it finds, all without leaving the conversation.

ConsentStack is a hosted consent management platform (CMP). This server exposes 22 tools covering the full job, so the same assistant that built your site can put working cookie consent on it.

Quick start

Claude Code:

claude mcp add --transport http consentstack https://app.consentstack.io/api/mcp

Cursor, or any client that supports remote MCP over streamable HTTP:

{
  "mcpServers": {
    "consentstack": {
      "url": "https://app.consentstack.io/api/mcp"
    }
  }
}

Authentication is OAuth 2.1. On first connect your client opens a browser window and you sign in with your ConsentStack account. There are no API keys to create or paste. Full setup instructions live in the MCP server documentation.

What your agent can do

JobTools
Sites and setuplist_sites, get_site_overview, create_site, manage_domains, get_setup_guide
Cookie banner configurationget_config, update_appearance, update_content, update_compliance, update_settings, publish_config, discard_draft
Trackers and script blockinglist_detected_trackers, set_tracker_category, clear_tracker_override, set_hostname_policy
Compliance scanningstart_scan, get_scan_result
Consent analytics and logsget_consent_analytics, get_consent_logs
Documentationsearch_docs, get_doc

A typical end-to-end run

  1. Create. create_site adds a site on the free Basic tier. manage_domains registers the domains it runs on.
  2. Install. get_setup_guide returns the install tags with your real site key already filled in, ready to paste into your <head>.
  3. Configure. Banner appearance, copy, compliance rules, and behavior settings are staged as drafts. Drafts never touch the live site, so your agent can propose a complete cookie banner and you approve it before anything ships.
  4. Publish. publish_config pushes the staged changes live.
  5. Verify. start_scan runs a compliance scan and get_scan_result returns the findings. Each finding names the tool that fixes it, so the agent can categorize the offending tracker and rescan to confirm.

Because every write is staged as a draft and publishing is a separate, explicit step, an agent cannot silently change what visitors see on your production site.

About ConsentStack

ConsentStack blocks tracking scripts before they load, categorizes the trackers it detects, and signals consent to downstream tools through Google Consent Mode v2 and native integrations for Meta, Microsoft, LinkedIn, TikTok, Pinterest, HubSpot, and Shopify. GDPR, CCPA, and the other US state privacy laws are handled by region, so visitors see the banner behavior their jurisdiction requires.

The Basic tier is free and covers 1,000 unique monthly visitors. See plans and pricing for higher traffic tiers, or run the free compliance scanner against your site to see what is firing before consent today.

If you built your site with an AI tool, this is the shortest path to a working cookie banner: the assistant that built the site installs consent on it.

Frequently asked questions

What is the ConsentStack MCP remote MCP server?

The ConsentStack MCP remote MCP server is a hosted Model Context Protocol endpoint at https://app.consentstack.io/api/mcp, so AI assistants can connect to it without installing or running anything locally.

How do I connect to the ConsentStack MCP MCP server?

Add the endpoint https://app.consentstack.io/api/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

Does the ConsentStack MCP MCP server require authentication?

Yes. ConsentStack MCP uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.

Which transport does the ConsentStack MCP MCP server use?

ConsentStack MCP exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments