Connecting to Anypoint
Agent Explorer connects to MuleSoft Anypoint Platform using your own Anypoint account. It reads the platform with exactly the permissions you already have — nothing more.
Connecting
- Open Anypoint in the top navigation.
- If your deployment offers more than one control plane, pick yours (US, EU, Gov, or a private instance).
- Click Connect to Anypoint.
- Sign in on Anypoint's own login page and review the consent screen.
That is the whole flow. There is nothing to create, and nothing to paste — Agent Explorer never asks for or sees your Anypoint password.
What is being requested
The consent screen lists four scopes:
| Scope | What it means |
|---|---|
read:full | Read-only access. Agent Explorer cannot change anything in your platform. |
profile, email | Identify who connected. |
offline_access | Stay connected without signing in again every session. |
Anypoint offers apps acting on a user's behalf only all-or-nothing access — there is no way to grant read access to some products but not others. Agent Explorer requests the read-only variant, so it can never modify your platform.
After connecting
Pick your organization from the selector. Business groups are nested as deeply as they are in Anypoint.
There is no environment to choose. The environment that matters belongs to each broker, not to your session: you pick an instance when you import, and that instance's environment is what its logs, traces and deployment are read from ever after. It is shown on the broker's row in the list, and as a badge beside its name once opened — on every agent imported alongside it too, since they all came from the same instance.
One connection at a time
Agent Explorer holds a single Anypoint connection per user. The connected card names the control plane it is on — "US Cloud", say — beside the host.
To move to a different control plane, disconnect first. That is why the control-plane picker appears before you connect and not after: switching is a disconnect, not a setting.
Disconnecting removes your Anypoint credentials and nothing else. Brokers you have imported stay in their workspace. Their logs, traces and metrics live in the control plane they came from, so those go blank until you reconnect to that plane.
Troubleshooting
Anypoint sign-in did not complete. Two different things produce this message, and Agent Explorer cannot tell them apart — Anypoint's response is identical for both. Either you declined the request on the consent screen, or your Anypoint organization restricts which apps its members may authorize. If you meant to decline, nothing is wrong; just connect again when you're ready. If you didn't decline, ask an Anypoint administrator whether your organization needs to allow Agent Explorer first.
You are asked to reconnect. Your Anypoint session expired and could not be renewed. Click Reconnect.
No Connect button, just "Setup required". The deployment has no Anypoint control plane configured. See Self-Hosting Setup.
No control-plane picker, even though more than one is configured. The picker is only shown before you connect. Disconnect to choose a different plane. If it is still absent afterwards, only one plane is fully configured — a client ID without its secret counts as unconfigured, and on a hosted deployment new environment variables reach the app only after a redeploy.