Skip to main content
Connect MuleSoft Anypoint Platform so CloudThinker agents can find failed Mule apps, check recent deployments, read CloudHub logs, and review API Manager policies, then start, stop, restart, roll back, or scale an app through your Approvals. The connection signs in with the client ID and client secret of an Anypoint Connected App that acts on its own behalf.

Prerequisites

  • An Anypoint Platform organization on the US, EU, or Government Cloud control plane. Organizations on another MuleSoft cloud, on MuleSoft Government Cloud Plus, or on Private Cloud Edition can’t connect yet: contact us.
  • The Organization Administrator permission in the business group where you create the Connected App. See MuleSoft’s Creating Connected Apps.
  • The Admin role in your CloudThinker workspace, which can add and edit connections. See Roles.
Apps on CloudHub 2.0, CloudHub 1.0, and your own Mule servers (hybrid) all work through Anypoint’s control plane. Nothing is installed on your servers.

Setup

1

Create a Connected App

Sign in to Anypoint Platform and open Access Management. In the navigation menu, click Connected Apps, and optionally select the business group to create the app in. Click Create App, enter a name such as cloudthinker, and select App acts on its own behalf (client credentials).
2

Add scopes

Click Add Scopes and select the scopes from Required permissions. Click Next, select the business groups the app can reach, and click Next. Select every environment agents should see, such as Sandbox and Production, and click Next. Review the list, click Add Scopes, then click Save.Runtime Manager and API Manager scopes apply per environment. If you don’t select an environment, Anypoint saves those scopes unticked, and agents see no apps.
3

Copy the client ID and secret

In Connected Apps → Owned Apps, click Copy Id for the app, then copy its client secret the same way.
4

Add the connection in CloudThinker

In the sidebar, click More → Workspace settings → Connections. On the Builtin Connections tab, search for MuleSoft Anypoint Platform and click Connect. Fill in the fields from Connection details and click Connect.Success state: the connection shows Connected. CloudThinker has checked that the Connected App can read its own organization. What agents can see in Runtime Manager and API Manager depends on the scopes from step 2.

Connection details

Pick the region you sign in to: anypoint.mulesoft.com is US, and eu1.anypoint.mulesoft.com is EU. CloudThinker always verifies Anypoint’s certificate and doesn’t follow redirects, so the secret is never sent anywhere else.

Required permissions

Agents can do only what the Connected App’s scopes allow, in the business groups and environments you selected.
Start with the read scopes in the environments you want investigated. Add the Runtime Manager action scopes only in environments where agents should be able to restart or scale apps. CloudThinker doesn’t need Exchange scopes.

Agent capabilities

Every change an agent makes goes through your workspace’s Approvals first. On the default Auto · Rules + AI · Ask me mode, AI judgment can let a safe change run without asking — and an Allow Rule can too, once CloudThinker turns on Rule enforcement for your workspace. Choose Manual to approve every change yourself. Hybrid apps have no central log store in Anypoint. For those, agents say so and point you to the log system your servers send to.

Verify the connection

A working connection returns your business groups and environments, then the apps you scoped, grouped by runtime.

Example prompts

Write access

Before any action, CloudThinker reads the app and shows its environment, version, status, and the downtime or capacity change in the approval request. If the app changes between that read and the action, the action is refused and needs a fresh read and approval. An accepted request isn’t a finished one. CloudThinker reads the app again until the deployment settles. A failed or timed-out action is never retried on its own. A restart stops the app and then starts it; if it’s interrupted, the app can stay stopped until you approve a start. Agents can’t deploy new apps, change app properties, or edit API policies. Rollback works only on CloudHub 2.0: use your release pipeline for CloudHub 1.0 and hybrid apps. Scale hybrid apps on your own servers.

Troubleshooting

The client ID or secret is wrong, or the secret was changed. Copy both again from Connected Apps → Owned Apps. Check that Region matches the cloud your organization is on: an EU app can’t sign in to the US region.
The app was created as App acts on behalf of a user. Create a new Connected App with App acts on its own behalf (client credentials) and use its client ID and secret.
The app signed in but can’t read its own organization. Add View Organization and View Environment to the app for that business group, save it, and connect again.
The Runtime Manager and API Manager scopes weren’t saved for any environment. Open the app in Connected Apps, click Add Scopes, and select the business group and each environment again. Check that the scopes now show as ticked.
The app changed after CloudThinker read it, or the Connected App lacks the Runtime Manager action scopes in that environment. Ask the agent to read the app again, then approve the new request. If it’s refused again, add the action scopes from Required permissions.

Security

  • Least privilege — grant only the permissions the agents need for your use case; start read-only and widen later.
  • Read-only by default — use read-only credentials unless you want agents to make changes through this connection.
  • Rotate credentials — rotate keys and tokens on your normal schedule; CloudThinker picks up the new value when you update the connection.
  • Revoke on offboarding — remove the credential at the provider when you delete a connection or a teammate leaves.
  • Set a secret expiry. A Connected App secret doesn’t expire by default. Set an expiration date, or rotate it on your normal schedule.
  • Rotate after an ownership transfer. When the app’s creator leaves or loses admin rights, MuleSoft moves the app to the root organization owner. Rotate its secret, then update the connection.

Approvals

Decide which changes run, wait for a person, or are refused

Connections

Every service CloudThinker can connect to