Appearance

Connect Your AI Client ​

Use a client supporting Streamable HTTP and OAuth browser authentication. The instructions below target production and use this server URL:

text
https://mcp.consentpro.com/mcp

Use your account for the Consent Pro Web App in this environment. Production and staging have separate data and sign-in sessions.

Codex CLI ​

Add the remote server and authenticate:

bash
codex mcp add consent-pro --url https://mcp.consentpro.com/mcp
codex mcp login consent-pro

Complete the browser sign-in described under Authorize the connection. If adding the server already completed sign-in, a separate login is unnecessary. Start Codex and use /mcp to check the connection.

Codex app ​

  1. Open Settings → MCP and choose Add → Add MCP Server.
  2. Set the name to consent-pro.
  3. Select Streamable HTTP and enter https://mcp.consentpro.com/mcp as the URL.
  4. Save, choose Authenticate and complete browser sign-in.
  5. Return to the app and check that Consent Pro is connected.

The CLI and app share MCP configuration on the same Codex host. If you already added the server through the CLI, check the existing entry before adding another one. UI labels can vary by client version.

Claude Code ​

Add the remote HTTP server:

bash
claude mcp add --transport http consent-pro https://mcp.consentpro.com/mcp

Start claude, enter /mcp, select consent-pro and choose the authentication option. Complete browser sign-in, then return to Claude Code.

Claude on the web or desktop ​

  1. Open Settings → Connectors → Add custom connector.
  2. Enter consent-pro as the name and https://mcp.consentpro.com/mcp as the URL.
  3. Save or add the connector and choose the sign-in option.
  4. If an OAuth client choice is shown, select Claude Published Identity.
  5. Complete browser sign-in, then return to Claude and enable the connector for your conversation.

Custom connectors may depend on your plan or workspace administrator's settings. Button labels can vary by client version.

Cursor ​

Add this entry to your project's .cursor/mcp.json, or to ~/.cursor/mcp.json for all projects. Merge it with existing servers rather than replacing them.

json
{
  "mcpServers": {
    "consent-pro": {
      "url": "https://mcp.consentpro.com/mcp"
    }
  }
}

Open Cursor's MCP settings, find the server and choose Needs login or its authentication option. Complete browser sign-in and enable Consent Pro for Agent.

Other MCP clients ​

  1. Add a remote MCP server named consent-pro.
  2. Choose HTTP / Streamable HTTP transport.
  3. Enter https://mcp.consentpro.com/mcp as the endpoint.
  4. Use the client's OAuth sign-in option. No API key or manually copied bearer token is required.
  5. Complete authorization, return to the client and check the Consent Pro connection.

Clients that support only local stdio servers or static API keys cannot connect directly using this setup.

Authorize the connection ​

  1. Choose Read only, Full access or Custom.
  2. Sign in with your Finsweet account and select the Consent Pro workspace to connect.
  3. Review and approve the requested permissions.
  4. Return to your client and ask: "List my Consent Pro projects."

The connection is bound to that account and workspace. Read only excludes Google Tag Manager and consent export/proof requests. To use GTM, choose Full access or Custom with View Google Tag Manager enabled, then follow the GTM connection guide.

To switch workspaces or change permissions, reconnect the connector and review the access you want to grant. Existing connections do not automatically receive newly introduced permissions. If you want tracker suggestions, translation editing or setup checklist updates, include those capabilities when reconnecting.

Tracker suggestion requests send selected tracker information to the AI service used by Consent Pro. Suggestions are shown for your review and do not save or publish changes.

Troubleshooting ​

  • A request is unavailable: check the approved permissions and reconnect if you need to change them.
  • Your projects are missing: check the selected workspace and whether the client uses the production or staging endpoint.
  • Sign-in fails: retry authentication in your client. If it reports an unsupported transport or OAuth flow, check the client's remote MCP support.
  • Google is not connected: ask "Connect Google Tag Manager" and open the returned link yourself. Connect it separately from the Consent Pro sign-in.
  • A draft change is not visible to visitors: it is saved as a draft until it is published. Ask your assistant to publish it (this needs the Publish changes permission), or use the Publish changes button in the Consent Pro dashboard.

Client references ​