# MCP server: drive FlowConsent from Claude Connect the official MCP server and manage banners, scans and compliance in natural language. > Canonical: https://www.flowconsent.com/en/doc/mcp-server > Last updated: 2026-07-29 ## What it is The FlowConsent MCP server (`https://mcp.flowconsent.com`) lets you drive FlowConsent from Claude or any MCP client: create and deploy banners, scan a site, verify compliance, set up recurring monitoring — in natural language. ## Connecting 1. In Claude (claude.ai → Settings → Connectors), add a remote connector with the URL `https://mcp.flowconsent.com`. 2. Authenticate: the OAuth flow asks for your explicit consent on your FlowConsent account. No API key to copy. ## Typical flows - **Create and publish**: `list_workspaces` → `create_banner` → `check_publish_readiness` → `deploy_banner` → `get_banner_snippet` (the snippet includes the Consent Mode stub: paste it first in the ``). - **Inventory**: `scan_site` detects a site's third-party services and pre-fills the configuration. - **Prove compliance**: `discover_pages` suggests representative pages, `verify_consent_compliance` loads each page while refusing consent and lists what still runs. Cookieless Google Consent Mode pings (gcs=G100) are recognized as compliant. - **Monitor**: `monitor_compliance` schedules a recurring check, `get_compliance_history` is your dated history. A regression triggers an email and your webhooks. ## Good to know Every tool declares whether it reads or writes; actions visible to real visitors (`deploy_banner`) ask for confirmation. Server-side processing escapes any banner: see the server SDK.