> ## Documentation Index
> Fetch the complete documentation index at: https://platform.atlan.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To act on Atlan objects, use the Atlan MCP server at https://api.atlan.com/mcp or the SDK. To install or publish skills from a terminal, use the `aireg` CLI; `aireg --map json` prints its command map. The `atlanai` CLI is deprecated. Run a read-only identity check before any write.
> The docs MCP server at /mcp searches these docs only. It cannot read or change Atlan objects.
> SDK packages: Python `atlanai` (PyPI) and TypeScript `@atlanai/sdk` (npm). Show Python first, then TypeScript.
> These docs cover Atlan Trident, Atlan's hosted product. AI Registry and Agent Registry are its earlier names. Registry OSS is Atlan's open-source agent registry: the registry specification and its aireg CLI, with their own public repository, docs and release notes; /open-source on this site links them. Registry OSS is open source; Atlan Trident is not. Answer generic aireg or specification questions from the project's docs, and use these docs for Atlan-specific setup such as the Atlan adapter, sign-in and workspaces.
> Atlan offers a second product, the Agentic Data Catalog: Atlan's enterprise context layer, covering the data catalog, connectors, lineage, data governance and glossary. It is documented at https://docs.atlan.com; answer questions about it from those docs, not these.

# Supported AI tools

> Which AI tools work with Atlan Trident, and what works in each: Claude Code, Codex, Cursor, VS Code with GitHub Copilot, Claude chat and Cowork, and any other MCP client.

Which AI tools work with Atlan Trident, and what do you get in each one? Every
tool that speaks MCP can reach your organization's skills and tools. Two things
work in fewer tools: having workspace skills installed in the tool itself, and
having its sessions recorded as traces. The table shows which.

## What works in each tool

| Tool | Connect to the Atlan MCP server | Workspace skills | Sessions recorded as traces | Needs Atlan Trident Desktop |
| - | - | - | - | - |
| **Claude Code** | [Atlan plugin](https://platform.atlan.com/plugins/references/claude-code.md) or [`claude mcp add`](https://platform.atlan.com/clients/claude/how-tos/claude-code). Desktop installs the plugin when you sign in. | Installed in Claude Code by Desktop or `aireg`, one plugin per workspace. Also found through MCP. | Yes, by Desktop or an [`aireg` traces job](https://platform.atlan.com/tools/brain/how-tos/capture-traces) | No. Desktop or `aireg` is needed for installed skills and for sessions. |
| **Codex** (shown as **ChatGPT** in Atlan Trident) | [Atlan plugin](https://platform.atlan.com/plugins/references/claude-code.md) or [`codex mcp add`](https://platform.atlan.com/clients/openai/how-tos/codex). Desktop installs the plugin when you sign in. | Installed in Codex by Desktop or `aireg`, one plugin per workspace. Also found through MCP. | Yes, by Desktop or an [`aireg` traces job](https://platform.atlan.com/tools/brain/how-tos/capture-traces) | No. Desktop or `aireg` is needed for installed skills and for sessions. |
| **Cursor** | [Atlan plugin](https://platform.atlan.com/plugins/references/claude-code.md) as a team marketplace, or [`mcp.json`](https://platform.atlan.com/clients/cursor/how-tos/cursor). Desktop shows the plugin's state but can't install it in Cursor. | Found through MCP. Desktop doesn't install them in Cursor. | Not captured | No |
| **VS Code with GitHub Copilot** | [Atlan plugin](https://platform.atlan.com/plugins/references/claude-code.md) or [**MCP: Add Server**](https://platform.atlan.com/clients/vscode/how-tos/vscode.md) | Found through MCP | Not captured | No |
| **Claude chat and Cowork** (claude.ai and the Claude desktop app) | [Atlan plugin](https://platform.atlan.com/plugins/references/claude-code.md) under **Customize** › **Plugins**, then **Connect** | Found through MCP and read into the conversation. Nothing is installed. | Not captured | No |
| **Any other MCP client** | Add `https://api.atlan.com/mcp`. The client must support Streamable HTTP, and OAuth 2.1 or a bearer token. See [Connect client to MCP Gateway](https://platform.atlan.com/gateway/mcp/how-tos/connect-a-client.md). | Found through MCP | Not captured | No |
| **Agents you build** | The MCP URL through your framework's guide, such as [LangGraph](https://platform.atlan.com/frameworks/langgraph/how-tos/langgraph.md) or [OpenAI Agents SDK](https://platform.atlan.com/frameworks/openai-agents-sdk/how-tos/openai-agents-sdk.md) | Found through MCP | Yes, when the agent sends them with the [atlanai SDK](https://platform.atlan.com/tools/sdk/tutorials/quickstart.md) or [OpenTelemetry](https://platform.atlan.com/api/how-tos/send-otlp-traces.md). [Tracing paths](https://platform.atlan.com/frameworks/coverage.md) lists each framework. | No |

How to read the columns:

* **Connect to the Atlan MCP server.** Every tool uses the same URL,
  `https://api.atlan.com/mcp`, and signs in with your Atlan account in the
  browser. The Atlan plugin adds that server plus the `atlan-*` skills that
  teach the tool how to find, use, and publish what your organization has.
  Adding the server by hand gives the tools without those skills.
* **Workspace skills.** "Installed" means the skill sits in the tool's own
  skills list and loads like any local skill. "Found through MCP" means the
  tool searches Atlan Trident and reads the skill when you ask for it. See
  [How your AI tool finds a skill](https://platform.atlan.com/registry/skills/how-tos/use-in-coding-agents.md#how-your-ai-tool-finds-a-skill).
* **Sessions recorded as traces.** Atlan Trident Desktop and `aireg` read
  session files that Claude Code and Codex keep on your computer. No other tool
  in the table is read. A tool marked "Not captured" still leaves a record of
  each MCP call it makes, under **Tool calls** in MCP Studio, but no session, no
  trace, and no run on a skill's **Usage** tab.
* **Needs Atlan Trident Desktop.** Desktop runs on macOS and Windows. See
  [Install Atlan Trident Desktop](https://platform.atlan.com/desktop/install.md).

Connecting MCP and capturing sessions are separate. Connecting a tool doesn't
record its sessions, and recording sessions doesn't give a tool Atlan's tools.

## Use Atlan Trident from a chat app without installing Desktop

You don't need Atlan Trident Desktop, a terminal, or a coding agent to use your
organization's skills from a chat app. You need the Atlan MCP server connected
in that app.

In Claude chat and Cowork:

1. On a Claude Team or Enterprise plan, an Owner first adds the connector
   `https://api.atlan.com/mcp` for the organization.
2. Open **Customize**, then **Plugins**, and select **Add marketplace**. Enter
   `atlanai/atlan-plugins`, then add **AI Registry**.
3. Select **Connect** on the plugin's **Connectors** tab and sign in to Atlan
   in your browser.
4. Ask *"Connect me to Atlan."* The reply names your organization and the
   workspaces you can use.

To roll this out to everyone, an administrator adds the marketplace and the
connector on Claude's organization plugin page. See
[Claude chat and Cowork](https://platform.atlan.com/plugins/how-tos/managed-installation.md#claude-chat-and-cowork).

Another chat app can add `https://api.atlan.com/mcp` as a remote MCP server if
it supports Streamable HTTP and OAuth 2.1. Your organization's administrator
for that app may need to allow custom connectors.

What you get:

* **Skills on request.** Ask for one by name or by task, such as *"Find an
  Atlan skill for writing release notes and use it here."* The app searches the
  workspaces you can open and reads the skill into the conversation.
* **Your organization's tools.** The MCP servers your team registered, such as
  Slack or a warehouse, with your own permissions.
* **A record of each call.** Every call appears under **Tool calls** in MCP
  Studio with your name, the tool, and the outcome.

What you don't get:

* **Installed skills.** The chat app doesn't list your workspace skills beside
  its own. It reads one when you ask, so it won't reach for an Atlan skill
  unless you ask.
* **Sessions and traces.** The conversation isn't recorded in Atlan Trident.
  It adds no session, no trace, and no run to a skill's **Usage** tab.
* **Local work.** Importing skills from your computer and running local coding
  agents need Desktop. See
  [Web app and Atlan Trident Desktop](https://platform.atlan.com/get-started/web-app-and-desktop.md).

## Windows

Atlan Trident Desktop installs on Windows 10 or later as well as macOS 13 or
later. The web app and every MCP connection in the table work from any
operating system your tool runs on.

## See also

* [Tracing paths by framework and library](https://platform.atlan.com/frameworks/coverage.md): support levels for agent frameworks and model SDKs.
* [Web app and Atlan Trident Desktop](https://platform.atlan.com/get-started/web-app-and-desktop.md): what needs Desktop and what works in the browser.
* [Supported features and limits](https://platform.atlan.com/gateway/mcp/references/supported-features.md): MCP transports, protocol versions, and limits.
* [Capture coding-agent sessions](https://platform.atlan.com/plugins/index): choose between Desktop and an `aireg` traces job.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.