anypoint-connect

Quick Start

# 1. Install
npm install -g @sfdxy/anypoint-connect

# 2. Configure (interactive — prompts for Client ID & Secret)
anc config init

# 3. Authenticate (opens browser for OAuth)
anc auth login

# 4. Verify
anc auth status

No Connected App yet? The four-step setup, including the exact scopes to grant, is in Getting started. Requires Node.js >=20.0.0.

anc apps list --env Sandbox
anc logs tail my-api --env Sandbox
anc monitor view --env Production

Working across several organizations? Use named profiles — Profiles and multiple orgs.

Related MCP server: WhenLabs/When

What it does

Every command is documented in the CLI reference.

MCP server

56 tools for AI agents. Set up credentials first — the server has nothing to offer an unauthenticated session.

anc config init
anc auth login

Every host runs the same command; only the file and the wrapping key differ.

{
  "mcpServers": {
    "anypoint-connect": {
      "command": "npx",
      "args": ["-y", "@sfdxy/anypoint-connect@0.11.0", "mcp"]
    }
  }
}

Installed globally, use "command": "anc", "args": ["mcp"] and skip the download. No env block is needed: the active profile resolves from the project's .anypoint-connect.json, falling back to default. Credentials never pass through the protocol — the server holds the session, the agent calls tools.

Per-host examples, prompts, and resources are in the MCP guide; the full tool table is in the catalog.

Safety

Every mutating operation is dry-run by default: without confirm: true it returns a preview and changes nothing. Redeploying an existing app changes only the artifact reference, so runtime, target, replicas, and settings are preserved and a version bump cannot silently downgrade a runtime or halve capacity. update_app_settings PATCHes only application properties, merging protected values rather than blanking them. Deletion requires a deployment-ID-bound confirmation — plus a separate acknowledgement in production — so it fails closed if the deployment changed since you looked.

// preview
deploy_jar({ "jarPath": "target/example-api-1.0.0-mule-application.jar", "appName": "example-api", "environment": "Sandbox" })
// apply
deploy_jar({ "jarPath": "target/example-api-1.0.0-mule-application.jar", "appName": "example-api", "environment": "Sandbox", "confirm": true })

Full model in Safety; the build, publish, deploy, and rollback path in Deploying a JAR.

When something fails

Access problems come in six distinct states — not configured, not authenticated, environment not visible, not permitted, transient, and ready — and they have different fixes. The error text names which one you are in. See Access readiness and Troubleshooting.

Library

import { AnypointClient } from '@sfdxy/anypoint-connect';

const client = new AnypointClient({
  clientId: process.env.ANYPOINT_CLIENT_ID!,
  clientSecret: process.env.ANYPOINT_CLIENT_SECRET!,
});

const me = await client.whoami();
const envs = await client.accessManagement.getEnvironments(me.organization.id);

The API clients give you token refresh, rate limiting, and caching, but not the confirmation gates — those live in the CLI and MCP layers. More in the library guide.

Documentation

Published at https://avinava.github.io/anypoint-connect/ with search.

Ecosystem

The canonical package matrix and supported combination live in the mule-skills ecosystem hub. This is the only tool in the set that needs Anypoint credentials. A complete release crosses two boundaries: mule-build produces and versions the artifact, while this package puts it in an environment. More detail is on the local ecosystem page.

Development

npm install
npm run build
npm test
npm run lint

Releases are tag-triggered: bump the version, push the tag with git push --follow-tags, and GitHub Actions runs CI, publishes to npm with provenance, and creates the release.

License

MIT