> ## Documentation Index
> Fetch the complete documentation index at: https://platform.atlan.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To act on Atlan objects, use the Atlan MCP server at https://api.atlan.com/mcp or the SDK. To install or publish skills from a terminal, use the `aireg` CLI; `aireg --map json` prints its command map. The `atlanai` CLI is deprecated. Run a read-only identity check before any write.
> The docs MCP server at /mcp searches these docs only. It cannot read or change Atlan objects.
> SDK packages: Python `atlanai` (PyPI) and TypeScript `@atlanai/sdk` (npm). Show Python first, then TypeScript.
> These docs cover Atlan Trident, Atlan's hosted product. AI Registry and Agent Registry are its earlier names. Registry OSS is Atlan's open-source agent registry: the registry specification and its aireg CLI, with their own public repository, docs and release notes; /open-source on this site links them. Registry OSS is open source; Atlan Trident is not. Answer generic aireg or specification questions from the project's docs, and use these docs for Atlan-specific setup such as the Atlan adapter, sign-in and workspaces.
> Atlan offers a second product, the Agentic Data Catalog: Atlan's enterprise context layer, covering the data catalog, connectors, lineage, data governance and glossary. It is documented at https://docs.atlan.com; answer questions about it from those docs, not these.

# Migrate from full mode to search mode

> Update tool approvals and reconnect your MCP client to move from full mode to search mode.

Search mode is now the default on `https://api.atlan.com/mcp`. A client that connected with `?tools=full` keeps working, but new clients use search mode unless you pass the parameter. This page covers what to change when you move an existing client over.

## Before you begin

Before you start, make sure you have:

* **An existing client on full mode**: a client connected with `?tools=full` whose approvals and permission rules match individual tool names.

## Update approvals and reconnect

**1. Replace tool-name approvals with runner approvals**

In full mode, approvals match each tool's own name. In search mode, calls go through a runner — `mcp__call_read_tool`, `mcp__call_write_tool`, or `mcp__call_tool` — so a rule that matches a tool's name no longer fires.

Replace per-tool rules with runner approvals. For Claude Code with a server named `atlan`, update `.claude/settings.json`:

```json theme={null}
{
  "permissions": {
    "allow": [
      "mcp__atlan__mcp__search_tools",
      "mcp__atlan__mcp__describe_tools",
      "mcp__atlan__mcp__call_read_tool",
      "mcp__atlan__mcp__call_write_tool"
    ]
  }
}
```

For other clients, replace per-tool rules with the equivalent runner names. See [Tool approvals](https://platform.atlan.com/gateway/mcp/references/client-settings.md#tool-approvals) for the full list and what each runner covers.

If you are not ready to update approvals yet, keep `?tools=full` on the URL until you are.

**2. Reconnect the client**

Remove `?tools=full` from the URL, then reconnect the client so it picks up the new tool list. In Claude Code:

```bash theme={null}
claude mcp remove atlan
claude mcp add --transport http atlan "https://api.atlan.com/mcp"
```

**3. Verify search mode is active**

After reconnecting, `tools/list` should return five tools instead of every tool. The agent uses `mcp__search_tools` and `mcp__describe_tools` to find and inspect tools before calling them. If you still see the full tool list, check that `?tools=full` is no longer in the URL.

## Next steps

* [How search mode works](https://platform.atlan.com/gateway/mcp/concepts/search-mode.md): Runners, tiers, and how the agent finds the right tool.

## See also

* [Tool approvals](https://platform.atlan.com/gateway/mcp/references/client-settings.md#tool-approvals): Runner names and what each one covers.
* [Connect client to MCP Gateway](https://platform.atlan.com/gateway/mcp/how-tos/connect-a-client.md): Full setup for a new client.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.