atlanai
plugin on every machine. Each developer still signs in once with their own Atlan account.
Prerequisites
- Managed-settings control: Administrator control of the managed-settings path on each platform.
- Atlan accounts: Each developer belongs to your Atlan organization.
Steps
1
Write managed settings
Add the
atlan marketplace and enable the plugin:autoUpdate takes each new plugin version when Claude Code refreshes the marketplace. Without it,
machines stay on the version they first installed. To hold a reviewed version instead, add
"ref" with a commit or tag to the source and move it deliberately.2
Copy settings to each machine
Give the file administrator ownership so users cannot change it.
3
Verify on one machine
- Claude Code lists
atlanaias enabled, from theatlanmarketplace. /mcp,plugin:atlanai:atlan, Authenticate completes the browser sign-in.- “Connect me to Atlan.” shows the developer’s organization.
Claude chat and Cowork
Claude’s organization plugin page installs into Claude chat and Cowork, a separate surface from Claude Code. Add the marketplaceatlanai/atlan-plugins there and the connector
https://api.atlan.com/mcp for the organization.
See also
Install the Atlan plugin
Install and sign in on one machine, in any supported agent.
MDM deployment
Deploying Atlan Trident Desktop through device management.