CLEENG MCP SERVER

Run your subscription business from Claude

MCP connects Cleeng to AI, helping your team find information, answer questions and get work done faster — without adding another screen to the workflow.

Book a demo Read the docs

WORKS WITH CLAUDE, CHATGPT, CURSOR AND MORE

Your existing access is all agents need.

Connect once, use the roles you already have, and keep every action governed by the same permissions and data your team uses today.

https://dashboard.cleeng.com/oauth/consent?client_id=claude-mcp

Claude would like access to your Cleeng account

By continuing, you allow Claude to use your Cleeng data in accordance with their terms of service and privacy policy.

Kübra GüvenCleeng TV (company 4821)

Switch account

Permissions requested

Retention IntelligenceNoneReadFull

Customer Experience ManagementNoneReadFull

Product ManagementNoneReadFull

Available permission levels come from this user’s permissions in the Cleeng dashboard. Claude cannot receive more access than the user already has.

Authorise

Cancel

Authorising will redirect you to claude.ai

Live in one step

A hosted Cleeng MCP server, added once with a single URL. No API keys to manage.

Access you already control

Each person signs in with their own Cleeng account and gets the role they already hold — Retention Intelligence, Customer Experience Management or Product Management.

Every change approved first

Reads are free. Every change is previewed, confirmed, limited and logged.

Numbers you can verify

Figures come from the same governed model your dashboards read, with the metric named.

Your team, with agents doing the work alongside them.

Agents use the access your team already has to answer questions, complete tasks, and keep people in control of changes.

Retention and analytics

YOUR AI TOOL · CLEENG CONNECTED

TRY ONE

Read runs inside the person’s existing role. Confirm means the change is previewed and a person approves it before it lands.

Questions teams ask before they connect

What is MCP?

A standard way for an AI tool to connect to a system it doesn’t own. Cleeng runs the server; your AI tool connects to it and can then work with your Cleeng data, inside the permissions of whoever signed in.

Can an AI tool change our data without us knowing?

No. Reads run immediately and change nothing. Every change is previewed, confirmed by a person, limited to that person’s role and recorded.

How do we limit who can do what?

Three roles, granted per user in Access and Security with None, Read or Full: Retention Intelligence, Customer Experience Management and Product Management. Nobody gets more through the connection than they already have in the dashboard.

Can it get a number wrong, or make one up?

Figures come from the same governed model your dashboards read, and the answer names the metric it used, so you can check it. Where the model has no answer, you get no answer. How that model is built →

Does this create new reporting?

No. It surfaces the metrics the platform already computes.

Which AI tools does this work with?

Any tool that supports MCP connects the same way.

Named list of supported AI toolsProduct / engineering — same list as the hero

What does it cost?

Commercial modelProduct / commercial — included in the subscription, priced separately, or early access

How long does setup take?

One admin session: add the URL, grant the roles.

Typical time to first queryProduct — from sandbox session to a working answer

Is our data safe?

The connection reaches only the records inside your own Cleeng account, through the same governed model the dashboards read. It cannot reach raw card data or another customer’s account, it authenticates with each person’s own Cleeng credentials, and every call is logged. The full boundary →

Connect Cleeng to the AI tool your team already opens.

Bring a question your team currently waits days for.