Read Contentsquare funnels, journeys, and error impact from the terminal
Connect Contentsquare and your agent can pull experience analytics while you work. Funnel drop-offs, page group metrics, journey paths, and the errors costing you conversions all answer in the terminal, without a browser tab. When a change is needed, such as recommending goals for a project, the agent shows the plan first and waits for your approval.
21 tools: 19 read, 2 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Contentsquare MCP run looks like inside Luumen.
Authorize once with OAuth 2.0. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as recommendgoals, submitmcpfeedback. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Contentsquare MCP — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.