Skip to main content
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.

​
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 (<slug>__*). 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 <n> 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: 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 <server-name>__<tool>, such as linear__save_issue for a server named Linear, and agents can find them with search mode. 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. 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

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.
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.

​
See also