Cleeng MCP Server uses Model Context Protocol (MCP), an open standard that lets AI tools connect to Cleeng. Once an administrator grants you MCP access in the Cleeng dashboard, you add Cleeng to your AI tool yourself.
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).
Before you start
You need three things in place.
- A Cleeng Dashboard account. You cannot sign up from inside the AI tool.
- MCP Server access granted to you. An administrator sets your user permission level - Read only, or Read + write - on each role. See Cleeng MCP Server: Grant and manage access.
- An AI tool that supports MCP. Any tool that supports the protocol can connect, Claude and ChatGPT among them. Cleeng provides the hosted connection, and you supply the tool. Your IT team may need to allow external connectors in your workspace.
New to Cleeng MCP Server? See Cleeng MCP Server: What it is and how it works for what it does and how permissions work.
1. Add the Cleeng connector to your AI tool
Note: Currently. you can connect Cleeng to Claude. More AI tools to follow soon.
Setup in Claude
In Claude, add Cleeng MCP Server as a custom connector:
- Go to Customize option to add Cleeng MCP Server as a custom connector.
-
In Add custom connector, paste the appropriate Cleeng MCP Server URL for your environment.
Sandbox:
https://mcp.api.sandbox.cleeng.com/mcp/main/v1
Production:https://mcp.api.prod.cleeng.com/mcp/main/v1 - For Authentication, select Always required.
-
For OAuth client, select Use your own OAuth client.
- In the field for “The public identifier from your provider’s OAuth app settings”, enter main-mcp.
- Click Connect to finalize the setup.
2. Sign in with Cleeng
Use your Cleeng Dashboard login. Identity stays with Cleeng.
A verification code step from your authenticator app can appear during sign-in; complete it to finish connecting.
3. Review and authorize
The consent screen lists the three roles and, for each, the permission levels you can grant to this AI tool. Anything above your user permission levels set in the Cleeng Dashboard is grayed out.
The Cleeng Dashboard and the consent screen use different labels for the same idea. Full on the consent screen corresponds to Read + write in the dashboard.
| Your user permission level | AI tool permission level can choose |
|---|---|
| Role not granted to you | None |
| Read only | None or Read |
| Read + write | None, Read, or Full |
At Read, the tool looks things up and can describe a change, but never writes it. At Full, the tool can write changes; each write is previewed and confirmed by you first.
See below an example for Claude:
After a successful authorization, you return to your AI tool.
4. Approve the first function
Before it runs anything, your AI tool names the Cleeng function it wants to use. Nothing runs until you allow it.
See an example from Claude:
From then on you work in conversation. Results come from what Cleeng already reports, and Cleeng creates no new reporting for the AI tool.
For the functions available in each role, see Cleeng MCP Server: What you can do with each role.
What happens when you ask for a change
Cleeng handles reads and writes differently.
- Lookups and metrics answer straight away, within the roles you hold.
- Changes go through a preview first. Your AI tool shows exactly what would change, you confirm in the conversation, and only then does Cleeng validate the change against your account rules and write it.
If your AI tool permission level on a role is Read, your AI tool describes a change but never writes it.
FAQs
What is MCP?
A standard way for an AI tool to connect to a system it doesn’t own. In the case of Cleeng, 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.
Is my Cleeng password ever shared with the AI tool?
No. Sign-in happens on Cleeng's own pages. The AI tool never sees the password and Cleeng never stores third-party credentials.
Can an AI tool change something on its own?
No. A write is previewed as a plain-language statement of exactly what will change, and nothing is sent until the person confirms in the conversation. Declining leaves the platform untouched.
Troubleshooting
If a request is refused, the reason is usually one of the presented below.
Authentication Flow: No Cleeng account.
Cause: If you don't have an account, you will see regular authentication error messages after being redirected to Cleeng login/sign in page.
Fix: Ask an administrator to create your dashboard account first, then connect again. You cannot sign up from inside the AI tool.
Authentication Flow: No permission.
Cause: The request falls outside the roles you were granted.
Fix: A dashboard administrator can raise the grant.
Conversation with AI: Read only
Cause: You may have permission but you decided to not give write permission to the AI tool. Your AI tool grant on that role is Read, so the change is described and never written.
Fix: If you change your mind, then you can update the permission directly from the AI connector settings section.