Cleeng MCP Server lets you run subscription work from the AI tool your team already uses, such as Claude or ChatGPT. You add Cleeng as a connector in that tool, sign in with your Cleeng account, and then ask for data or request changes in conversation.
The Cleeng MCP server is built and hosted by Cleeng. Adding it to your selected AI tool (e.g. Claude or similar) account lets your selected AI tool read Cleeng data and, with your confirmation, change it, on your behalf, within your existing dashboard permissions.
This is not a Cleeng-provided AI feature and is not an endorsement of, or warranty regarding, a specific AI tool. You are connecting your own AI tool to your own Cleeng data, at your own discretion. Cleeng assumes no liability for any outcomes or any issues resulting from such a connection. Data your selected AI tool account retrieves from Cleeng is subject to your agreement with the respective provider (e.g. Anthropic for Claude) once it reaches your selected AI tool (e.g. Claude).
What MCP is
Model Context Protocol (MCP) is an open standard that lets an AI tool access external tools and data sources.
Cleeng hosts an MCP server, so any AI tool that supports the protocol can connect to it. There is no Cleeng app or plugin to install.
Main concepts
AI tool - The application you chat with, such as Claude or ChatGPT. It connects to Cleeng MCP Server and calls Cleeng functions on your behalf. Also called an MCP client.
Cleeng MCP Server - The hosted Model Context Protocol server Cleeng runs. Any MCP-capable AI tool can add it, sign in with Cleeng, and start working.
Connector - An external service added to an AI tool. You add Cleeng MCP Server as a custom connector; there is no Cleeng app or plugin to install.
MCP (Model Context Protocol) - An open standard that lets an AI tool access external tools and data sources.
Role - One of three groups of functions: Retention Intelligence, Customer Experience Management, Product Management. An administrator grants each role per person in the Cleeng dashboard. See the What you can do section below.
User permission level - What an administrator granted you on a role in the Cleeng dashboard. A role can be granted at Read only or at Read + write. A role can also be left ungranted. See the Permissions section below.
AI tool permission level - What your AI tool may do on your behalf within a role: None, Read, or Full. You set it when you connect that tool, and never above your user permission level. See the Permissions section below.
These are two separate products, and you can use either or both.
- Cleeng AI Assistant is the assistant built into the Cleeng dashboard. You work with it inside Cleeng.
- Cleeng MCP Server works the other way around. It lets the AI tool your team already uses connect to Cleeng from outside.
Who it is for
- Data and business teams who need metrics such as churn, revenue, and active subscriptions.
- Customer support teams who look up customer accounts and correct their details.
- Product and technical teams who manage offers.
What you can do
Cleeng MCP allows you to ask about your subscription data and, with your confirmation, change it: look up customers and subscriptions, report on metrics such as churn and revenue, and manage your offers. What you can do depends on your role(s). An administrator grants access per person, across the three roles below.
| Role | Overview |
|---|---|
| Retention Intelligence | Metrics and reporting. Track churn, revenue, and active subscriptions, with period-over-period comparison. |
| Customer Experience Management | Customer accounts and subscriptions. Look up an account, check a subscription, and handle account needs. |
| Product Management | Find offers and their pricing and terms, change them, or take them off sale. |
For the details of what each role covers, see Cleeng MCP Server: What you can do with each role.
How permissions work
Access is set in two places:
- Your user permission level - set by an administrator in the Cleeng dashboard. Signing in requires authentication against your Cleeng account. On logging in, you receive permissions based on the roles assigned to you. Each role is granted at Read only or at Read + write, or not granted at all.
- Your AI tool permission level - set by you, when you connect the Cleeng MCP Server to your AI tool. For each role, you decide what that specific tool may do on your behalf.
| AI tool permission level | What your AI tool can do |
|---|---|
| None | The role is invisible to your AI tool. Cleeng refuses requests inside it. |
| Read | Your AI tool looks things up and can describe a change, but never writes it. |
| Full | Your AI tool can write changes. Each write is previewed with its effect, and a person confirms it. |
Full corresponds to Read + write in the Cleeng dashboard. Your user permission level is the ceiling: an AI tool never receives more access than you already hold, and you can always give it less.
| Your user permission level | AI tool permission level you can choose |
|---|---|
| Role not granted to you | None |
| Read only | None or Read |
| Read + write | None, Read, or Full |
How reads and changes are handled
Reads run freely. Lookups and metrics answer straight away, within the roles you hold. Results come from what Cleeng already reports.
Every change passes through preview and confirmation. Nothing reaches Cleeng until you approve it:
- Your AI tool previews the change. It describes exactly what would change before it writes anything.
- You confirm in the conversation. Declining leaves your account untouched.
- Cleeng checks the limits and records the action. Cleeng validates your account rules and limits before it applies the change.
What Cleeng MCP Server does not do
- It does not create new reporting. Metrics come from what Cleeng already reports.
- It does not create Cleeng accounts. You cannot sign up from inside the AI tool. You need a Cleeng dashboard login first.
- It does not widen anyone’s access. A person’s MCP roles never exceed the permissions they already hold in the Cleeng dashboard.
FAQs
About the product
What is the Cleeng MCP Server?
A hosted Model Context Protocol server operated by Cleeng. It exposes a defined set of Cleeng functions so an MCP-capable AI tool can look things up and, with confirmation, make changes. It is a connection to Cleeng, not a chatbot Cleeng ships.
Where do the numbers come from?
From what the platform and ChurnIQ already report.
Can it take payments or issue refunds?
No. Payment collection, refunds and checkout creation are out of scope.
Can it run something while nobody is watching?
No. Unattended and scheduled actions are out of scope. Every change is confirmed by a person in the conversation.
Getting started
What does a publisher need to get started?
A Cleeng dashboard account with a grant on at least one role, an MCP-capable AI tool, and the Cleeng connection URL. No install, no plugin, no developer work.
Do I need a developer to set this up?
No. A dashboard administrator grants access, and each person adds a connector in their own AI tool.
Access and security
Can the AI tool see more than I can?
No. Available levels come from your permissions in the Cleeng Dashboard, and the AI tool can never receive more access than you already have.
Can the AI tool change our data without us knowing?
No. Reads run freely, and every change is previewed, confirmed by a person and recorded.
How do we limit who can do what?
There are three roles, granted per user in Cleeng Dashboard > Admin & Tools > Access & Security. An administrator can withhold a role, or grant it at Read only or Read + write. Each person then sets an AI tool permission level for each role when they connect a tool, up to the level an administrator granted them.
Does Cleeng train models on our data?
No. Cleeng does not train models on publisher or subscriber data through this connection.
Next steps
- Administrators: Cleeng MCP Server: Grant and manage access and Cleeng MCP Server: What you can do with each role
- Cleeng MCP Server users: Cleeng MCP Server: Connect your AI tool