--- url: https://docs.consentpro.com/mcp.md description: >- Connect your AI assistant to review Consent Pro projects, manage consent settings and prepare changes for your approval. --- # Consent Pro MCP Connect your AI assistant to Consent Pro to review your projects and manage your consent setup from a conversation. You choose what the assistant can access and which changes to approve. [Connect your AI client](/mcp/setup) · [Google Tag Manager integration](/mcp/google-tag-manager) ## What you can do * Review setup steps, scan findings, saved trackers and their categories. * Create custom-site projects, manage scans and update scan schedules. * Review suggested tracker categories, descriptions and translations before saving them. * Edit banner appearance, privacy-policy links and regional settings. * Preview saved banner changes on your website before publishing. * View consent statistics and request emailed consent exports or proof. * Review and edit Google Tag Manager settings with a separate Google connection. Some actions require additional permissions. Billing, transferring or deleting a project and connecting Webflow sites are managed in the Consent Pro dashboard. ## Connect to Consent Pro These instructions target `__CONSENT_PRO_DOCS_ENVIRONMENT__`. | Setting | Value | | -------------- | ------------------------------------------ | | Server name | `__CONSENT_PRO_MCP_NAME__` | | Server URL | `__CONSENT_PRO_MCP_URL__` | | Transport | Streamable HTTP | | Authentication | Browser sign-in with your Finsweet account | Sign in with the account you use for the [Consent Pro Web App](__CONSENT_PRO_WEB_APP_URL__), select your workspace and review the requested permissions. No API key is needed. Follow the [client setup guide](/mcp/setup) for connection instructions. ## Try a request * "Review my website's consent setup and tell me what needs attention." * "Audit my published homepage against my settings and show evidence, failures and unverified checks." * "Scan my website and show me the trackers to review." * "Suggest categories for these trackers, then let me review them." * "Update this tracker's French description and keep its other translations." * "Change my banner's privacy-policy link to https://example.com/privacy." * "Remember visitors’ consent choices for 180 days." * "Send an additional copy of new consent records to my endpoint at https://example.com/consents." * "Preview my saved banner changes before I publish them." * "Connect Google Tag Manager and review my container's consent settings." Be specific about the project, account or container when you have more than one. Consent expiry controls how long visitors’ choices are remembered; it does not change consent-log retention. To [store an additional copy in your own database](/web-app/storing-consents), supply an existing HTTPS endpoint that accepts consent records by JSON POST. Your assistant can save or remove the endpoint for Webflow and custom sites, but saving the address does not create or test the receiving server. Review and publish the draft when ready. Removing the endpoint stops future forwarding after publication; it does not delete existing external records. ## Review and publish changes Banner, tracker and consent-setting changes are saved as drafts. Review them before asking to publish. Renaming a project, starting or cancelling a scan, changing its schedule and connecting an account take effect without publishing. After a scan, review the discoveries and approve which changes to import. New discoveries still need tracker review; importing does not confirm their categories or publish them. Saved tracker lists exclude discoveries that have not been imported. Ask to see the current information and proposed changes before approving edits. You can request suggestions without saving them. Check their accuracy before approving changes. Updating tracker information may also confirm it as reviewed; changes to a shared provider can affect other trackers that use that provider. Translation edits keep other languages and omitted fields unchanged. Avoid editing the same information in the dashboard and your assistant at the same time. For automatic blocking, use the [recommended non-async installation](/runtime/automatic-blocking). A saved installation setting does not replace code already installed on your site. Review categories and resource URLs, publish when ready, and check actual browser requests after rejection, partial acceptance and withdrawal. Draft previews are available for Webflow and custom sites with the current installation. Webflow also needs its banner component and source installed. Select a page and region covered by your banner. Keep preview links private; opening one does not publish changes. Mark the preview checklist step complete after checking the result yourself. Publishing makes the saved configuration available to your website. Browser caches and already-open pages can delay when a visitor sees it. Check the published result in a fresh browser. A successful setup check or scan does not guarantee complete blocking or legal compliance. ## Permissions and your data Choose **Read only**, **Full access** or **Custom** when connecting. Read only lets you inspect your Consent Pro setup; Google Tag Manager access and consent export or proof requests need additional permission. Custom lets you choose individual capabilities, including tracker suggestions, translation editing and setup checklist updates. Reconnect if you want to change the workspace or grant additional access. Existing connections do not automatically receive newly introduced permissions. Project information and requested Google Tag Manager details are shared with your chosen AI client and may be processed by its AI provider. Tracker suggestion requests send selected tracker information to the AI service used by Consent Pro. Review your client's privacy settings alongside Consent Pro's policies. [Privacy Policy](https://consentpro.com/legal/privacy-policy) · [Terms of Service](https://consentpro.com/legal/terms-of-service) · [Contact Support](https://consentpro.com/talk-to-expert) ## Troubleshooting * **A project is missing:** check the signed-in workspace and that your assistant and dashboard use the same environment. Returning to the project list does not necessarily mean the project was deleted. Contact support if the link still opens the wrong place. * **A request is unavailable:** review your connection permissions and reconnect if you need additional access. * **Scan findings are missing:** check the scan status and review the findings before treating an empty tracker list as a complete scan result. * **Saved changes are not visible:** preview the draft or publish the reviewed changes. See [Publishing Changes](/web-app/publishing). For browser evidence from a published page, use the [page audit](/mcp/site-audit). Confirm the exact page and expected behavior first. It defaults to the homepage, supports another page when explicitly requested, tests only that page without crawling and proposes fixes without applying them.