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.
https://mcp.flowconsent.comFrom cookie inventory to proof of compliance, the agent chains the right tools for you.
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_bannercheck_publish_readinessdeploy_bannerget_banner_snippetYour 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_siteupdate_bannerProof 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_pagesverify_consent_complianceAn 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_complianceget_compliance_historyThe server is added as a remote connector. Authorisation goes through your FlowConsent account, with your explicit consent.
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.comSign in to your FlowConsent account and approve the consent screen. No password or API key ever goes through the MCP server.
Describe what you want. The agent picks the tools and asks you to confirm sensitive actions.
Actions that overwrite a configuration or reach real visitors are declared sensitive: your MCP client uses this to ask you for confirmation.
list_workspacesYour workspaces, with their plan and number of banners.get_workspacePlan, remaining quotas and publishing rights of a workspace.list_bannersYour banners, filterable by workspace.get_bannerDeployment status, configuration and code of a banner.list_servicesThe catalogue of third-party services FlowConsent knows.export_banner_configThe full configuration as JSON, versionable and replayable.diff_banner_configsThe differences between two banners, such as staging and production.create_bannerCreates a banner from your description.update_bannerEdits an existing banner (overwrites the configuration).duplicate_bannerCopies a banner, in the same workspace or another one.delete_bannerDeletes a banner, irreversibly.check_publish_readinessChecks whether a banner can be published and lists what is missing.preview_bannerRenders a preview of the banner without putting anything live.deploy_bannerPuts the banner live for your real visitors.get_banner_snippetReturns the script tag to paste into the site's head.get_setup_instructionsThe guided setup, platform by platform.scan_siteFinds a site's trackers and cookies and pre-fills the services.discover_pagesSuggests 3 to 5 representative pages of a site to check.verify_consent_complianceLoads a page while refusing consent and lists what runs.check_consent_modeChecks the 7 Google Consent Mode signals and their consistency.monitor_complianceSchedules a recurring check of a page.get_compliance_historyThe dated history of checks, with regressions.get_banner_statsA banner's consent statistics.export_consent_logsConsent logs, your GDPR proof for an audit.list_consent_webhooksConfigured consent webhooks, without their secrets.configure_consent_webhookCreates a signed webhook, called on every consent or withdrawal.delete_consent_webhookDeletes a consent webhook.configure_cloudflareSaves the Cloudflare account used for self-hosting.The MCP server has no power of its own: every request goes out with your session, under the same rules as the app.
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.
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.
Four separate permissions. Read banners, edit them, publish them, read statistics. Publishing, which real visitors see, is a permission of its own.
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.
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.
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 policyCan't find your question? Write to us, we answer fast.
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.
No. You sign in with your FlowConsent account and approve a consent screen. There is no key to copy or store in your client.
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.
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.
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.
Free up to 25,000 sessions a month. No credit card, no commitment.