Skip to main content
Two different tools sit under this heading. They solve opposite problems, and the names are close enough to confuse, so start here.
Preview. Both are distributed org-internal today. The atlanai/claude-plugins marketplace is private during preview, and @atlanai/registry is not on public npm. Confirm access with your Atlan contact first.

​
Capture coding-agent sessions

The Claude Code trace plugin installs local hooks that turn each coding session into OpenTelemetry traces and ships them to Agent Registry. You get the same session, trace, and cost views for coding work that the SDKs give you for your own agents — without changing any application code.

Claude Code trace plugin

Install the marketplace plugin, sign in, and verify a captured session.

Managed installation

Deploy it fleet-wide through Claude Code managed settings.
If you want Atlan tools inside Claude Code rather than session capture, that is the MCP endpoint instead — see the Claude Code integration. The two are independent: connecting MCP does not capture sessions, and installing the plugin does not add tools.

​
Install agent artifacts into a project

registry resolves skills, plugins, subagents, commands, hooks, MCP servers, rules, and LSP servers from a Git repository and projects them into whichever coding agents a project actually uses — Claude Code, Codex, Cursor, or the vendor-neutral AGENTS.md layout — then records exactly what it did so the next run can tell whether anything moved.

Registry package manager

Install artifacts, pin refs, and keep a project in sync.

Command reference

Every command, flag, scope, and exit code.
  • CLI overview — the atlanai CLI, which owns publishing, registry reads, and trace management. It is a different binary from registry.
  • Publish skills from GitHub — put skills into Agent Registry, rather than pulling them into a project.
  • Tracing SDKs — instrument your own agents instead of a coding agent.