> ## 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.

# Why use Agentic Data Catalog with Atlan Trident

> What Atlan Trident and the Agentic Data Catalog each do, why agents need both kinds of context, and how the two connect.

Agents that answer business questions need context about your data and about themselves. Atlan builds a product for each.

## What Atlan Trident is

Atlan Trident is where your organization keeps its AI agents and what they use. It holds context about your agents: what they are, what they can do, and how well they do it.

* **Skills**: Versioned skills with owners and releases. See [How skills work](https://platform.atlan.com/concepts/how-skills-work.md).
* **Agents**: A record of each agent, its versions, and its runs. See [How agents work](https://platform.atlan.com/concepts/how-agents-work.md).
* **Traces and evals**: What each run did, and whether a change made the agent better. See [How sessions and traces work](https://platform.atlan.com/concepts/how-sessions-and-traces-work.md) and [How evals work](https://platform.atlan.com/concepts/how-evals-work.md).
* **Metrics and ontology**: The numbers and business model analytics agents answer with. See [Metric Studio](https://platform.atlan.com/studios/metrics-studio) and [Ontology](https://platform.atlan.com/ontology/index).
* **AI Gateway and spend**: One gateway for model and MCP tool calls, and what those calls cost. See [AI Gateway](https://platform.atlan.com/gateway/index.md) and [Review agent spend](https://platform.atlan.com/finops/index.md).

## What Agentic Data Catalog is

The Agentic Data Catalog is Atlan's data catalog. It holds governed context about your data: what tables mean, how data flows, who owns it, and what your organization trusts.

* **Data assets**: Metadata from the data sources you connect, searchable by people and agents. See [Discovery](https://docs.atlan.com/product/capabilities/discovery).
* **Lineage**: How data flows across your sources. See [Lineage](https://docs.atlan.com/product/capabilities/lineage).
* **Business glossary**: The terms your organization agrees on. See [Business Graph (Glossary)](https://docs.atlan.com/product/capabilities/governance/glossary).
* **Governance**: Access policies, data quality rules, and data contracts. See [Access Control](https://docs.atlan.com/product/capabilities/governance/access-control), [Data Quality Studio](https://docs.atlan.com/product/capabilities/governance/data-quality), and [Contracts](https://docs.atlan.com/product/capabilities/governance/contracts).
* **Semantic models**: Models built from governed context and deployed to Snowflake, Databricks, or dbt. See [Context Engineering Studio](https://docs.atlan.com/product/capabilities/governance/context-engineering-studio).

## How data moves between them

* **Imports**: Atlan Trident doesn't import catalog assets, lineage, or glossary terms. Metrics you save in Metric Studio and ontologies you build stay in Atlan Trident.
* **The catalog's MCP server in Atlan Trident**: The catalog's MCP server is in **Store** as **Atlan**. Once it's added, agents connected to MCP Gateway can call the catalog's tools through the same connection. See [Connect remote MCP servers](https://platform.atlan.com/gateway/mcp/how-tos/integrations.md).
* **Permissions on those calls**: Each person signs in with their own catalog account, so the catalog's permissions decide what they can read.
* **Records of those calls**: Atlan Trident records each call under **Tool calls**. It passes the call through to the catalog and doesn't copy catalog content into Atlan Trident.

## Sign-in and administration

* **Accounts**: Each product has its own accounts. A catalog account doesn't sign you in to Atlan Trident, and an Atlan Trident account doesn't sign you in to the catalog.
* **First admin**: An Atlan Trident organization starts with one invited administrator, who invites everyone else. See [Use the web app](https://platform.atlan.com/get-started/use-web-app.md).
* **SSO**: An administrator sets up SSO in each product separately. For Atlan Trident, see [Configure company SSO](https://platform.atlan.com/admin/security/how-tos/configure-sso.md).
* **Which product a sign-in page belongs to**: Check the address. The Atlan Trident web app is at `app.atlan.com`; the catalog is at your tenant's own address.

## MCP servers and plugins

Each product has its own MCP server. Both can appear as "Atlan" in an agent's connector list.

| | Catalog's Atlan MCP server | Atlan Trident's MCP Gateway |
| - | - | - |
| Address | `https://mcp.atlan.com/mcp` | `https://api.atlan.com/mcp` |
| What its tools do | Search catalog assets, follow lineage, read and manage glossary terms | Find and use skills, agents, metrics, saved queries, and ontology, and call the MCP servers your team has added |
| Tool names you see | Search, lineage, and glossary tools | `mcp__search_tools`, `mcp__describe_tools`, and the `mcp__call_…` runners, often beside `registry__` tools |
| Sign-in | Your catalog account, through OAuth or an API key | Your Atlan Trident account |
| Plugin for coding agents | `atlan`, in Anthropic's plugin directory | `atlanai`, in Atlan's plugin marketplace. In Claude Code its server shows as `plugin:atlanai:atlan`. |
| Setup | [Set up Atlan MCP](https://docs.atlan.com/product/capabilities/atlan-ai/how-tos/remote-mcp-overview) | [Connect client to MCP Gateway](https://platform.atlan.com/gateway/mcp/how-tos/connect-a-client.md) |

To tell which server a client is using, look at the server's address: `/mcp` in Claude Code, or the connector list in your client's settings. If you can't see the address, look at the tools: `mcp__search_tools` means Atlan Trident. If an agent picks the wrong one, see [Agent answers from catalog, not your metrics](https://platform.atlan.com/studios/metrics/troubleshooting.md#agent-answers-from-catalog-not-your-metrics).

## Why use them together

An agent that answers business questions needs both kinds of context. From the catalog it learns what your data means and whether it can be trusted. From Atlan Trident it gets the skills and metrics to work with, and you see what it did, what it cost, and whether it is getting better.

The two connect through MCP. Add the catalog's MCP server to MCP Gateway, and an agent reaches the catalog's tools through the same connection it uses for everything else in Atlan Trident.

```mermaid theme={null}
flowchart TB
  A["Your agent"]
  subgraph Trident["Atlan Trident"]
    T2["MCP Gateway"]
    T1["Skills, metrics, ontology"]
    T3["Traces and evals"]
  end
  subgraph Catalog["Agentic Data Catalog"]
    C1["Assets, lineage, glossary, policies"]
  end
  A -- "tool calls" --> T2
  A -- "traces" --> T3
  T2 --> T1
  T2 -- "catalog's MCP server, when added" --> C1
```

| I want to | Use |
| - | - |
| Let people search and understand data assets | Agentic Data Catalog |
| Track lineage across data sources | Agentic Data Catalog |
| Keep the business glossary people look terms up in | Agentic Data Catalog |
| Share and version the skills agents use | Atlan Trident |
| Give agents metrics and trusted SQL to answer with | Atlan Trident |
| See what an agent did, what it cost, and whether it got better | Atlan Trident |
| Control which models and MCP tools agents reach | Atlan Trident |

Each product also works on its own, with its own sign-in, app, and MCP server.

## Agentic Data Catalog vs Atlan Trident

| | Agentic Data Catalog | Atlan Trident |
| - | - | - |
| Purpose | Governed context about your data estate | A governed home for your AI agents and the skills, metrics, and tools they use |
| What it holds | Assets from the sources you connect, lineage, glossary terms, and policies | Skills, agent records, sessions and traces, evals, metrics, and ontology |
| How content gets in | It connects to your data sources and brings in their metadata. People add meaning on top. | You and your agents publish to it. It doesn't crawl your data sources. |
| Where you open it | Your organization's own address, such as `https://<your-tenant>.atlan.com` | [app.atlan.com](https://app.atlan.com) in a browser, or Atlan Trident Desktop |
| Sign-in | Your account on your Atlan tenant | Your account in an Atlan Trident organization |
| Roles | **Admin**, **Member**, and **Guest**, with policies on top | Organization **Admin** and **Member**, plus **Admin**, **Builder**, and **Viewer** in each workspace |
| Programmatic access | Atlan APIs and SDKs | The Atlan Trident API, the `atlanai` SDK, and the `aireg` CLI |
| Docs | [docs.atlan.com](https://docs.atlan.com) | This site |

## See also

* [Explore platform](https://platform.atlan.com/platform-overview.md): The parts of Atlan Trident and how they fit.
* [Glossary](https://platform.atlan.com/concepts/glossary.md): Product names, including earlier names.
* [Install the Atlan plugin](https://platform.atlan.com/plugins/references/claude-code.md): The `atlanai` plugin, and how it sits beside the catalog's `atlan` plugin.


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