Catalog templates
OAuth discovery asks the server for its authorization metadata. Registered OAuth app requires an organization administrator to supply the vendor-issued client configuration when the setup form requests it. The server’s actual metadata and a successful connection test determine the usable setup.Tenant-specific setup
- Snowflake: provide the full MCP server URL for your account. Public endpoints only; Private Link is unsupported. Your Snowflake role and the server’s tools determine what you can read.
- Databricks: provide the workspace’s SQL MCP URL. The catalog accepts AI Gateway SQL MCP service URLs and the
/api/2.0/mcp/sqlshape. Public AWS, Azure, and Google Cloud workspace endpoints are supported; Private Link is unsupported. - dbt: provide the account access URL under
dbt.comorgetdbt.com. - Looker: provide a Looker-hosted instance under
cloud.looker.comorlooker.app; an administrator configures the OAuth client. - Glean: provide the backend domain shown in Admin → About Glean.
- Zendesk: provide your Zendesk sign-in address. Glean and Zendesk may also restrict network access; ask the vendor administrator when an otherwise correct endpoint is unreachable.
- Datadog: the supplied template uses the US1 endpoint. Other sites require a compatible custom server configuration.
Verify tools and access
Select Set up, finish the required endpoint and authorization steps, then Connect your account. Refresh the server’s tools and inspect authenticated MCPtools/list. Make one read-only call and find it in MCP activity. A displayed card or successful OAuth consent alone does not prove the tool works.
GitHub’s MCP template supplies remote tools; the GitHub App separately imports repository metadata and activity. Slack also separates personal tools from shared workspace previews.
To connect in the other direction, where a Snowflake or Databricks agent calls Atlan’s tools, use Atlan from data-platform agents. See Connect remote MCP servers for setup and constraints.



