Persyst connector
Clever Cloud MCP connector for ChatGPT, Claude and Copilot
Connected once by an administrator, with no Clever Cloud console access for each member.
Updated on October 18, 2026
Your tools
- Connected once, by the admin
- Rights per person, team or client
- Who read what, and when
Everyone’s AI
In short
- A product owner reads production logs with no console or command line: they ask in their assistant, like for everything else.
- The application is the unit of access: an application is opened to a team or a person. The other applications in the account don’t exist for their assistant.
- Read only: no deployment, restart or configuration change is possible from the assistant.
- The Clever Cloud authorisation stays in Persyst, encrypted; the assistant only receives the authorised logs, deployments and metrics.
EXAMPLES
What your team can ask
Why did the application restart last night?
A deployment at 2:14 am failed on startup, then the previous one was relaunched automatically at 2:16 am. The logs show a missing environment variable at boot. Here are the 40 lines around the error.
Sources consulted
- Clever Cloud · app-api · deployments
- Clever Cloud · app-api · logs 2:00 – 2:30 am
How many 500 errors on the API since this morning, and at what times?
One hundred and twelve error responses since 7 am, concentrated between 9:10 and 9:25, all on the same payment route. The peak matches the 9:08 deployment.
Sources consulted
- Clever Cloud · app-api · today’s logs
- Clever Cloud · app-api · deployments
HOW IT WORKS
Clever Cloud in your AI, in three steps
Connect the account
In Data sources, an administrator picks Clever Cloud and authorises Persyst from their account, with no API key to copy. Persyst discovers the accessible applications. The administrator selects the ones to declare; the others stay out of reach.
Open applications and rights
Each application is granted to a team or a person, with the allowed tools: deployments, logs, metrics. Grants can be changed at any time and apply to the next question.
Ask from the assistant
The member asks in ChatGPT, Claude, Copilot or Le Chat. The assistant finds the application, reads the authorised items and answers with its sources. Every tool call is logged: who, which application, which tool, when.
TOOLS
What your assistant can do
Clever Cloud· 4 tools
Opened team by teamLists the Clever Cloud applications open to the member, with the tools allowed on each.
list_clever_cloud_appsAn application’s deployments: date, state, commit, duration.
list_clever_cloud_deploymentsAn application’s logs over a period, filtered by text or level.
read_clever_cloud_logsAn application’s metrics over a period: CPU, memory, requests.
read_clever_cloud_metrics
Rights and audit trail
Rights per person, team or client.
Then, inside the tool, only the items you open. The rest does not exist for the AI.
One-click revocation.
Removing a member cuts their access in every AI at once.
A history.
Who used which tool, and when.
Credentials that stay put.
They remain encrypted in Persyst, never in the assistants.
COMPARISON
Persyst or direct access to Clever Cloud?
| Criterion | Persyst | Without Persyst: direct access to Clever Cloud |
|---|---|---|
| Who authenticates | The company, once, through an administrator. | Each person, with a Clever Cloud account or through someone who has one. |
| Installation | None: a remote MCP server, authorized from the assistant. | Nothing to install, but an export or a screenshot to redo for every question. |
| Where credentials live | Encrypted in Persyst, never in the assistant. | One Clever Cloud account per person, or files passed around by email. |
| Scope | Per person, team or client, then per opened item. | Everything the account allows. |
| History | Who used which tool, and when, for the whole team. | None. |
| When a member leaves | One-click revocation, in every AI. | Account to remove in Clever Cloud; what was already shared stays shared. |
What this connector does not do
- Read only: no deployment, restart, scaling or environment variable change.
- No access to secrets: environment variables and add-on credentials are not exposed.
- Logs are available for Clever Cloud’s retention period, not beyond.
Questions
Frequently asked questions
Does every member need a Clever Cloud account?
No. An administrator authorises Persyst once with their account. Authorised members consult the open applications from their assistant, with no account or console access.
Can a product owner read production logs?
Yes, if the application is open to them. No console, no CLI, no token to configure: they ask in their assistant and get the log lines for the requested period.
Can one application be opened without the others?
Yes. Rights are set per application, then per tool: deployments, logs, metrics. One team sees the API, another the website, nobody sees the billing application.
Can the assistant act on the infrastructure?
No. The connector is read only. Deploying, restarting or changing a configuration is done in the Clever Cloud console, by the people allowed to.
