## Atlan MCP tools URL: https://docs.atlan.com/product/capabilities/atlan-ai/references/mcp-tools Last-Modified: 2026-11-20T13:37:08+04:00 > Reference for every tool available in the Atlan MCP server—search, lineage, metadata, governance, glossary, data quality, knowledge, and more. Filter by category or access level. Through the Atlan MCP server, agents reach the context layer as 41 governed tools across nine categories—search, lineage, asset metadata, glossary, data quality, and more—each with a defined access level. The Atlan MCP server exposes 41 tools across nine categories: search and discovery, lineage and exploration, asset metadata, custom metadata, asset lifecycle, business glossary, data domains, data quality, and knowledge and artifacts. Each tool has a defined access level—Read (query only), Write (modifies metadata), or Admin (requires admin permissions). Filter by category or access level to find the tool you need. Tools that change anything in Atlan propose first: they return a preview of the change and wait for your approval before writing. Each preview shows a readable location breadcrumb for the affected assets, so similarly named assets in different connections or schemas are easy to tell apart before you approve. When a change touches several fields, all of them appear together in one consolidated change set with a single approval. Some tools are gated per tenant, so your client may list fewer than the full set. For the metadata these tools can return about an asset, such as refresh status, usage, and access details, see [Asset metadata available through Atlan MCP](https://docs.atlan.com/llms/platform/atlan-mcp-overview/mcp-asset-attributes/llms.txt). > **Note: fluent_search is replacing search_assets** > > On tenants with Fluent Search enabled, `search_assets`'s listing steers toward `fluent_search` first, then is retired once adoption of `fluent_search` is high enough. If your integration still calls `search_assets` after it's retired on your tenant, you'll get a pointer response telling you to switch to `fluent_search`, not an error—no results are lost, but the call won't return catalog data. Update integrations that pin `search_assets` by name to call `fluent_search` instead. _Last updated: 20 November 2026._ ---