> Create, publish and check your consent banners in plain language, from Claude or any MCP client. 28 tools, OAuth 2.0, no API key. > > Canonical: https://www.flowconsent.com/en/mcp Official MCP server # Run FlowConsent from your AI agent. Create, publish and check your consent banners in plain language, from Claude or any MCP client. You connect with your FlowConsent account, with no API key. Server URL · `https://mcp.flowconsent.com` [Create a free account](https://app.flowconsent.com/auth/sign-up?utm_source=flowconsent.com\&utm_medium=referral\&utm_campaign=general) · [Read the documentation](https://www.flowconsent.com/en/doc/mcp-server) - 28 tools - OAuth 2.0 and PKCE - No API key Use cases ## The whole life of a banner, from the conversation. From cookie inventory to proof of compliance, the agent chains the right tools for you. Create and publish **A complete banner, without opening the editor.** Services, texts, colours, Consent Mode, legal identity: the agent sets everything up, checks the banner can be published, puts it live and hands you the embed code. `create_banner` · `check_publish_readiness` · `deploy_banner` · `get_banner_snippet` Scan **Your tracker inventory in one sentence.** The scan finds a site's scripts, pixels and cookies, suggests the matching services from the catalogue and flags cookies your banner does not declare yet. `scan_site` · `update_banner` Prove **Proof that nothing fires before consent.** The agent loads your pages while refusing consent and lists whatever still runs. Cookieless Google Consent Mode pings are recognised as compliant. `discover_pages` · `verify_consent_compliance` Monitor **An alert as soon as compliance slips.** A recurring check per page, a dated history of verdicts, and an alert by email and webhook when a new tracker shows up. `monitor_compliance` · `get_compliance_history` Connection ## Connected in two minutes. No API key. The server is added as a remote connector. Authorisation goes through your FlowConsent account, with your explicit consent. \[ 01 ] ### Add the connector In Claude (Settings, then Connectors), add a custom connector with the server URL. Any MCP client that supports remote servers works the same way. `https://mcp.flowconsent.com` \[ 02 ] ### Authorise access Sign in to your FlowConsent account and approve the consent screen. No password or API key ever goes through the MCP server. \[ 03 ] ### Ask Describe what you want. The agent picks the tools and asks you to confirm sensitive actions. Example requests - Scan mysite.com and create a banner with the services you find. - Check that nothing loads before consent on my homepage. - Review the Google Consent Mode setup of my banner. - Monitor my checkout page and tell me if a tracker appears. - Export last month's consents for my DPO. The tools ## 28 tools. Each one says whether it reads or writes. Actions that overwrite a configuration or reach real visitors are declared sensitive: your MCP client uses this to ask you for confirmation. Accounts and banners - `list_workspaces` · Your workspaces, with their plan and number of banners. Read - `get_workspace` · Plan, remaining quotas and publishing rights of a workspace. Read - `list_banners` · Your banners, filterable by workspace. Read - `get_banner` · Deployment status, configuration and code of a banner. Read - `list_services` · The catalogue of third-party services FlowConsent knows. Read - `export_banner_config` · The full configuration as JSON, versionable and replayable. Read - `diff_banner_configs` · The differences between two banners, such as staging and production. Read Create and publish - `create_banner` · Creates a banner from your description. Write - `update_banner` · Edits an existing banner (overwrites the configuration). Sensitive - `duplicate_banner` · Copies a banner, in the same workspace or another one. Write - `delete_banner` · Deletes a banner, irreversibly. Sensitive - `check_publish_readiness` · Checks whether a banner can be published and lists what is missing. Read - `preview_banner` · Renders a preview of the banner without putting anything live. Read - `deploy_banner` · Puts the banner live for your real visitors. Sensitive - `get_banner_snippet` · Returns the script tag to paste into the site's head. Read - `get_setup_instructions` · The guided setup, platform by platform. Read Scan and check - `scan_site` · Finds a site's trackers and cookies and pre-fills the services. Write - `discover_pages` · Suggests 3 to 5 representative pages of a site to check. Read - `verify_consent_compliance` · Loads a page while refusing consent and lists what runs. Read - `check_consent_mode` · Checks the 7 Google Consent Mode signals and their consistency. Read - `monitor_compliance` · Schedules a recurring check of a page. Write - `get_compliance_history` · The dated history of checks, with regressions. Read Proof and integrations - `get_banner_stats` · A banner's consent statistics. Read - `export_consent_logs` · Consent logs, your GDPR proof for an audit. Read - `list_consent_webhooks` · Configured consent webhooks, without their secrets. Read - `configure_consent_webhook` · Creates a signed webhook, called on every consent or withdrawal. Write - `delete_consent_webhook` · Deletes a consent webhook. Sensitive - `configure_cloudflare` · Saves the Cloudflare account used for self-hosting. Sensitive Security ## Your agent has your rights. Not one more. The MCP server has no power of its own: every request goes out with your session, under the same rules as the app. Your rights, nothing more **No power of its own.** The agent cannot do anything you could not already do in the app. Your account's access rules apply exactly as they are. Sign-in **OAuth 2.0 and explicit consent.** You sign in to your FlowConsent account, with a consent screen and PKCE. No password or API key goes through the server. Permissions **Four separate permissions.** Read banners, edit them, publish them, read statistics. Publishing, which real visitors see, is a permission of its own. Tokens **Short-lived, revocable access.** The access token lasts one hour, and access expires at the latest 30 days after your consent. Tokens are only stored as hashes. Safeguards **No publishing without a legal identity.** As in the app, publishing is refused until the company name, address, contact email and privacy policy are filled in. Data **Published retention periods.** What the MCP server keeps, and for how long, is set out in our privacy policy. An automatic purge applies these periods every day. [Read the privacy policy](https://www.flowconsent.com/en/legal/privacy) Questions ## Questions about the MCP server Can't find your question? Write to us, we answer fast. [Write to us](https://www.flowconsent.com/en/demo) ### Which MCP clients are supported? Claude, through a remote connector, and any client that supports remote MCP servers over Streamable HTTP with OAuth authentication. The URL to enter is https\://mcp.flowconsent.com. ### Do I need an API key? No. You sign in with your FlowConsent account and approve a consent screen. There is no key to copy or store in your client. ### Which plan do I need? The MCP server uses your account, with the same rights and limits as your plan. Banner hosting by FlowConsent is included in the Pro and Enterprise plans; on the Free plan, the banner is self-hosted on your Cloudflare account. ### Can the agent publish a banner without my approval? Publishing needs a dedicated permission, and the tool is declared sensitive so that your client asks you to confirm. It is also refused while the banner's legal identity is incomplete. ### How do I remove access? Remove the connector in your MCP client. In any case, access expires at the latest 30 days after your consent, after which you need to reconnect. ## Make your site compliant today. Free up to 25,000 sessions a month. No credit card, no commitment. [Create my banner](https://app.flowconsent.com/auth/sign-up?utm_source=flowconsent.com\&utm_medium=referral\&utm_campaign=general) · [Scan my site](https://www.flowconsent.com/en/scan)