Skip to content

CLI · MCP server · JavaScript library

Operate Anypoint Platform with safer defaults

Install once, authenticate through your organization’s Connected App, and use the same well-tested client to inspect applications, analyze logs, pull metrics, manage API assets, and perform guarded lifecycle operations.

npm install --global @sfdxy/anypoint-connect anc config init anc auth login anc auth status

Choose how you want to use it

Credentials, without the mystery

anypoint-connect uses a Connected App that acts on behalf of a user. The Client ID and Client Secret identify the app; a browser login authorizes the user; the resulting OAuth tokens are stored separately and refreshed automatically.

Connected AppClient ID, Client Secret, redirect URI, Full Access, Background Access
Browser authorizationThe user signs in with existing Anypoint permissions and MFA
Local profileRestricted credential file plus encrypted, refreshable OAuth tokens

Follow the exact Connected App fields, including what to ask an organization administrator for and how to rotate a secret safely.

What it covers

Area Typical work
Runtime Manager List, inspect, compare across environments, publish and deploy a JAR, redeploy, roll back, restart, scale, stop, start, and delete applications
Logs Tail and download logs, cluster errors with context, find recurring patterns, summarize log health
Monitoring Traffic, failures, and p50–p99 latency per app, worker, or route; heap, old-generation pressure, GC, CPU, and RAM per worker; incident time series; freeform AMQL. See Monitoring
Exchange and Design Center Search assets, download specifications, preview and sync spec files, publish API and application assets
API Manager and Governance Instances, policies, SLA tiers, alerts, governance rulesets and conformance
Platform services Environments, entitlements, audit log, Anypoint MQ, and Object Store v2

Every MCP tool is listed in the tool catalog; every command is in the CLI reference.

Safety is part of the interface

Deployment changes preview by default. Publishing binds the exact JAR bytes, redeploys change only the artifact reference, deletion is bound to the deployment ID that was inspected, Design Center writes need a single-use preview token, and production needs an additional acknowledgement. Read the safety model before automating a change.

Start with a read. anc auth status verifies the local session, and anc apps list --env Sandbox verifies that the intended environment is visible. Authentication, environment visibility, permissions, and subscription entitlements are separate states with separate fixes.