Skip to main content
Connect a Cortex Agent to Atlan MCP Gateway so it can search Registry artifacts and use tools with the signed-in person’s Atlan permissions.

Before you begin

Use a role allowed to create API integrations and external MCP servers. Choose the database and schema for the server, and identify the Snowflake role that will use it. Each person also needs access to the relevant Atlan workspaces. This procedure uses Dynamic Client Registration. The data platform overview lists Atlan’s endpoint and OAuth values.

Create the integration and MCP server

Run the following in the intended database and schema. Replace analyst with the role that will use the connection.
Both grants are required for tool discovery and invocation. See Snowflake’s MCP connector guide for object privileges and supported authentication methods.

Add Atlan to your agent

In Snowsight, open the agent’s MCP Connectors settings and select Atlan from the available connectors. Sign in to Atlan when prompted. Ask the agent to find an Atlan skill by name. Confirm a registry__search_artifacts call, then check Atlan’s Tool calls for the session activity. Session records depend on the audit write succeeding. If Atlan does not appear, confirm your current role has USAGE on both objects with SHOW EXTERNAL MCP SERVERS. If a tool is missing, check the signed-in person’s Atlan workspace access.

Connect Cortex Code CLI

Cortex Code CLI can also connect with an Atlan token supplied through your environment: