anypoint-connect¶
A CLI, MCP server, and TypeScript library for Anypoint Platform: deploy applications, tail and analyze logs, pull metrics, manage API specs, and inspect queues and Object Stores — with production safety nets on every mutating operation.
npm install -g @sfdxy/anypoint-connect
anc config init
anc auth login
anc auth status
Start here¶
| You want to | Go to |
|---|---|
| Set it up from scratch, including the Connected App | Getting started |
| Work across several organizations | Profiles and multiple orgs |
| Understand what happens when access is missing | Access readiness |
| Look up a command | CLI reference |
| Let an AI agent use it | MCP server |
| Find the right tool | Tool catalog |
| Know what can and cannot mutate production | Safety model |
| Ship a locally built JAR | Deploying a JAR |
| Fix something | Troubleshooting |
What it covers¶
| Area | Examples |
|---|---|
| Applications | Status, deployment spec, resources, settings, deploy, redeploy, rollback, restart, scale, stop, start, delete |
| Logs | Tail, download, error clustering with context windows, recurring patterns, statistical health |
| Monitoring | Request and response metrics, percentiles, time series, per-replica, JVM memory and GC, freeform AMQL |
| Exchange | Search, asset detail, spec download, JAR publication |
| API Manager | Instances, policies, SLA tiers, alerts |
| Design Center | Projects, branches, safe file sync, governed publication |
| Platform | Environments, entitlements, audit log |
| Anypoint MQ | Queues, depth and throughput, dead-letter browsing, test publishing |
| Object Store v2 | Stores, keys, values |
Safety, in one paragraph¶
Every mutating operation is dry-run by default: called without confirm: true it returns a preview of
exactly what would change and modifies nothing. Redeploying an existing application changes only the
artifact reference — runtime, target, replicas, and settings are preserved, so a redeploy cannot
silently downgrade a runtime or relocate an app. Deletion needs a deployment-ID-bound confirmation and,
in production, a separate acknowledgement, so it fails closed if the deployment changed underneath you.
The full model is on the safety page.
This is the one that needs credentials¶
Of the four tools in this ecosystem, only anypoint-connect authenticates against
Anypoint Platform. Set it up when you want runtime evidence or lifecycle operations; skip it if you only
need to lint, build, package, or document a project locally.