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.
- Agents: A record of each agent, its versions, and its runs. See How agents work.
- Traces and evals: What each run did, and whether a change made the agent better. See How sessions and traces work and How evals work.
- Metrics and ontology: The numbers and business model analytics agents answer with. See Metric Studio and Ontology.
- AI Gateway and spend: One gateway for model and MCP tool calls, and what those calls cost. See AI Gateway and Review agent spend.
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.
- Lineage: How data flows across your sources. See Lineage.
- Business glossary: The terms your organization agrees on. See Business Graph (Glossary).
- Governance: Access policies, data quality rules, and data contracts. See Access Control, Data Quality Studio, and Contracts.
- Semantic models: Models built from governed context and deployed to Snowflake, Databricks, or dbt. See 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.
- 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.
- SSO: An administrator sets up SSO in each product separately. For Atlan Trident, see Configure company SSO.
- 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.
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.
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.
Each product also works on its own, with its own sign-in, app, and MCP server.
Agentic Data Catalog vs Atlan Trident
See also
- Explore platform: The parts of Atlan Trident and how they fit.
- Glossary: Product names, including earlier names.
- Install the Atlan plugin: The
atlanaiplugin, and how it sits beside the catalog’satlanplugin.