Skip to main content
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

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

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