> ## 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. # Manage MCP servers > Check an MCP server's connection and tools, keep its catalog current, review its activity, and change, turn off, or remove it. After a server is added, manage it from its page in Atlan: check its connection, keep its tools current, review what agents did on it, and change or retire it. To add a server, see [Add MCP servers](https://platform.atlan.com/gateway/mcp/how-tos/integrations.md). ## Before you begin Before you start, make sure you have: * **Workspace access**: Refreshing a server's tools and changing its settings take update access to its workspace. * **Organization admin**: Turning a server on or off and removing it take the organization **Admin** role, unless the server is in your personal workspace. ## Open server's page In **Store**, select **Installed** in the sidebar, then select the server's name. Its page has **Overview**, **Tools**, **Activity**, and **Settings** tabs. Registered servers also appear under **Brain** > **MCP servers**, each with its **Connection** and **Enabled** state. ### Overview The server's page opens on **Overview**. **About** describes the server and, when it is on, names how agents reach its tools (`__*`). **Connection** shows its endpoint, authentication, protocol version, and transport, with **View settings** opening the **Settings** tab. **Tools** previews the server's tools, with **View all tools** opening the full list. **Recent calls** lists the newest calls through the server, each opening its session. The rail beside them shows the server's **Health** and authentication, its usage — calls, failures, and median time — and **Details**: its workspace, who registered it, and its server ID. A server installed from the Store also shows the listing it came from and the release its setup is pinned to. ### Tools The **Tools** tab shows how many tools the server has once Atlan has cataloged them. The same count heads the list, with the time of the last update. If you can edit the server's workspace and the server is on, **Refresh now** sits beside the count. For a server that uses each person's account, sign in first. Selecting **Refresh now** opens **Review the server's changes**, which lists the tools to add, to update, and to remove for everyone. Nothing changes until you select **Apply** or **Apply and remove**. Applying removes the tools listed for removal from the catalogue, so no agent sees or calls them. If the server lists nothing new, Gateway reports **Already up to date** and applies nothing. Tools are in two groups, each with its own count: * **Read-only tools**: tools the server says only look things up. * **Write/delete tools**: tools the server says can create, update, or delete data, and tools that don't say. A group with more than eight tools lists the first eight. Select **Show all \** to see the rest. A group lists every tool while you search, or when the last update added or changed tools in it. A server with more than 10 tools has **Search tools**. Tools the last update added or changed are marked **New** or **Changed**, and **Removed in the last update** lists tools agents can no longer call. ### Activity Organization admins see three numbers for the server first: **Calls, last 7 days**, **Failure rate**, and **Average time**. **Recent calls** lists the latest five calls through the server that you can see, with the tool, how long each call took, and when. A call that didn't succeed has a badge: | Badge | Meaning | | - | - | | **Refused** | The gateway refused the call because the tool isn't in the server's catalog. | | **Cancelled** | The call was cancelled. | | **Failed** | The call failed. | If a recent call was refused and you can edit the server's workspace, **Refresh the tools to pick up new ones** opens the **Tools** tab. **See all calls in MCP activity** opens the **MCP activity** report, filtered to this server. **History** lists changes to the server, newest first: the server being added, changed, or removed; its tools being cataloged or refreshed, with the tools each refresh added, changed, or removed; your own sign-in to it; and its shared credential, if you can read it. Your own changes show as **You**. Repeated changes by the same person in a row show as one line with a count, such as **· 3 times**. **Recent calls** and **History** update every 10 seconds while the tab is open. ## How the gateway catalogs tools Once a server is added, the gateway connects to it, lists its tools, and stores each one in the catalog, usually within seconds. Every client then sees the tools as `__`, such as `linear__save_issue` for a server named Linear, and agents can find them with [search mode](https://platform.atlan.com/gateway/mcp/concepts/search-mode.md). A tool the server marks as an MCP Apps helper, with a `ui.visibility` that leaves out `model`, is catalogued but stays out of `tools/list` and search results. To read what each tool does in Atlan, open the server's **Tools** tab. Each row shows the tool's description and the inputs it takes, and expands to list its inputs with each one's type, whether it is required, and what it is for. A new tool shows **New** and a changed tool shows **Changed**; expanding a changed tool shows **What changed**. | The gateway | When | | - | - | | Discovers tools | When the server is added, turned back on, or its URL changes | | Refreshes the catalog | Every hour, and when you select **Check connection** | | Keeps the catalog if the server returns nothing | An empty tool list never wipes existing tools | A server that uses each person's account is not refreshed in the background, because no shared credential exists. Check its connection after signing in. ### Connection status | Status | Meaning | Next step | | - | - | - | | **Ready** | The server needs no sign-in and its tools are available. | None | | **Connected** | You are signed in and the server's tools are available to you. | None | | **Sign-in required** | The server uses each person's account and you haven't connected yet. | Select **Connect**. | | **Reconnect needed** | Your sign-in expired or was revoked. | Connect again. | | **Checking** | Atlan is discovering the server's tools. | Wait a few seconds. | | **Attention** | The server needs action, such as a new credential. | Open the server and select **Check connection**. | | **Unavailable** | The gateway could not reach the server. | Check the URL and that the server is public. | | **Turned off** | The server is out of service, and its tools leave the catalog. | Turn it back on. | Until a person connects to a per-person server, its tools are hidden from that person's `tools/list`, and the result names the server so the client can prompt them. ## Change or remove server * **Turn off** a server to take it out of service without deleting it. * **Change its URL** to point at a new deployment. The gateway removes the tools it cataloged from the old address, then rediscovers the tools the new address offers. A server that signs in with OAuth can't be repointed to a different address: its sign-in is set up for the one it was added with, so the change is refused. * **Remove for everyone** deletes the server and all of its tools. A server cannot be moved to another workspace. Add it again in the new workspace instead. > [!WARNING] > > **Remove for everyone** deletes the server and every tool it cataloged, for every person and agent. To take a server out of service and keep its setup, turn it off instead. ## Troubleshooting If a server shows a connection warning, its tools are missing, or calls to it are refused, see [MCP Gateway errors](https://platform.atlan.com/gateway/mcp/troubleshooting.md). ## See also * [Add MCP servers](https://platform.atlan.com/gateway/mcp/how-tos/integrations.md): Add a server and set up its credentials. * [Track usage and audit tool calls](https://platform.atlan.com/gateway/mcp/how-tos/track-usage-and-audit.md): See calls across every server. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.