Skip to main content
Register a remote MCP server in MCP Gateway so every agent connected to the gateway can call its tools. Do this when you want agents to reach a tool that is not built into Atlan — a team’s Linear workspace, a Snowflake database, or a service your team runs. To connect your own client to the gateway instead, see Connect client to MCP Gateway.

Before you begin

Before you start, make sure you have:
  • A place for the server: You can set a server up in your personal workspace (for you alone) or for the organization (available across team workspaces). For the organization, an admin picks which workspaces can see it. See MCP permissions.
  • Organization Admin role: Required to add an enabled server for the organization, enable or disable a server, or remove one. Not required for a personal workspace server.
  • Supported server: The server speaks Streamable HTTP and is reachable from the internet. stdio servers and legacy HTTP+SSE servers are not supported.
Each MCP server is registered once for the whole organization. If it is already in MCP Studio > Servers, do not add it again — connect your account or link your workspace credential to the existing server.

Add server

Choose the path that matches where your server appears in Store. You can also start in MCP Studio: the Add a server dialog over its Servers page opens on the Store list, and for a server the Store doesn’t list, the dialog offers adding one by its address or from an API file.
The Store shows a card for each available server on its Connectors tab. A card shows Connect until the server is set up, Sign in when it is set up and you have not signed in yet, and Manage once it is ready to use. Find your server’s card and select Connect to begin. A card with no Connect button means you can’t set up servers in any of your workspaces, or the server isn’t taking new setups.
Store Integrations catalog with connected Glean and Linear servers, a Connect action for Miro, and Set up actions for other templates
1

Find server and pick workspace

Select Store in the left rail, then the Connectors tab, and select Connect on the server’s card. Under Pick a workspace, choose your personal workspace to set the server up for you alone, or the organization. A workspace you can’t set servers up in says so. Select Continue.
2

Check address

Under Check the address, fill in the endpoint or tenant fields the template asks for, then select Continue. If it asks for your organization’s own address, use one on a vendor domain Atlan has reviewed — setup refuses any other address. MCP integration templates lists each vendor’s endpoint and the inputs it needs.If Continue stays unavailable because the form does not accept your server’s address, ask an organization admin to add the server by its address instead, as the Custom URL tab describes.
3

Test connection and set up

Under Test the connection, select Test connection. When it passes, select Continue. Under Confirm and set up, accept the terms and select Set up in workspace.
4

Sign in with your account

When the server uses each person’s own account, the last step is Sign in with your account. Everyone else who wants to use the server selects Sign in on its card and signs in at the vendor.
5

Verify connection

Tools appear within seconds as <server-name>__<tool> in the server’s Tools tab. To test a tool without a client, open the server in MCP Studio and select Open playground. In your client, call mcp__describe_tools with the server’s name (search mode) or refresh tools/list (full mode), then make a test call as the person who will use it — a passing connection test does not prove the caller has permission.

What the server’s state warnings mean

An integration installed from a reviewed definition reflects the server’s real state: the Store reads the server’s current state whenever it shows the installation. When the server’s state and the installation’s record no longer match, the integration warns you:
  • Server archived — the server was archived in MCP Studio while the Store still manages the installation, so agents cannot reach its tools. Select Restore server to bring the server back — restoring needs an organization admin — or remove this installation.
  • Removal didn’t finish — the installation was removed, but its server is still active in MCP Studio, so agents can still reach it. That happens when the removal’s archive step failed, or when someone restored the server since. Select Finish removal to archive the server; archiving needs an organization admin, unless the installation is in your personal workspace. If someone restored the server on purpose, leave it as it is.

Troubleshooting

Next steps

See also