Skip to main content
Register Atlan MCP Gateway in Unity Gateway so Databricks agents can search Registry artifacts and call the tools their Atlan identity can access.

​
Before you begin

Use a Unity Catalog workspace with Model Serving support. Your role needs USE CATALOG, USE SCHEMA, CREATE SERVICE, and permission to create or use the HTTP connection. The workspace must reach api.atlan.com and auth.atlan.com. Choose your Atlan identity: a registered agent for a shared connection, or each person’s account. Keep an agent’s client_secret in your secret manager. The data platform overview lists the shared endpoint and OAuth values.

​
Register the external MCP service

  1. In Databricks, open Unity Gateway → MCPs → + MCP. Select Connect an existing MCP server, choose a catalog and schema, and name it atlan.
  2. Create or select an HTTP connection to https://api.atlan.com/mcp. If the form separates URL fields, use host https://api.atlan.com, port 443, and base path /mcp.
  3. Choose OAuth Machine-to-Machine for an Atlan agent, using its client credentials, token endpoint https://auth.atlan.com/oauth/token, and scopes contextplane:read contextplane:write. For each person’s account, choose Dynamic Client Registration.
  4. Select Create & load tools and sign in if prompted. Include mcp__initialise and the Registry or remote tools the agent needs, then select Create MCP Service.
  5. Grant callers EXECUTE on the service and USE CATALOG and USE SCHEMA on its parents.
See Databricks’ external MCP server guide for connection permissions and platform availability.

​
Verify in AI Playground

Choose a model with tool support. Under Tools → + Add tool → MCP Servers, choose External MCP servers and select atlan. Ask it to find an Atlan skill by name. Confirm a registry__search_artifacts call and check Atlan’s Tool calls for the session activity. Session records depend on the audit write succeeding. If a tool is missing, check the service’s tool selection and the Atlan identity’s workspace access.