# Link a remote MCP server
URL: https://metorial.com/docs/platform/integrations/link-remote-mcp-server

Connect a remote MCP server to Metorial.

---

Use a remote MCP server when the provider already offers an MCP endpoint. Metorial connects to it and you can use it like any other provider on Metorial. Connections are secure, auditable, and permissions and tool filters in Metorial apply like they do for any other provider.

<PageIntro>
  <Learn>
    * How to link a remote MCP server
    * How to check that it deployed successfully
  </Learn>

  <Reading title="Before you start">
    * Get the remote server URL
    * Check whether the server uses Streamable HTTP or SSE
  </Reading>
</PageIntro>

## Link the server [#link-the-server]

<Steps>
  <Step title="Open remote MCP servers">
    In the dashboard, open **Integrations**. Under **Custom Providers**, select **Remote MCP Servers**.

        <img alt="Remote MCP Servers page" src="__img0" />
  </Step>

  <Step title="Link a remote MCP server">
    Select 

    **Link Remote MCP Server**

    .
  </Step>

  <Step title="Enter the server details">
    Enter the remote MCP server URL. Select the transport the server supports: **Streamable HTTP** or **SSE**. Then select **Continue**.

        <img alt="Remote MCP server URL and transport fields" src="__img1" />
  </Step>

  <Step title="Name the provider">
    Enter a name and, if useful, a short description. Select **Link Remote MCP Server**.

        <img alt="Remote MCP server name and description fields" src="__img2" />
  </Step>

  <Step title="Check the deployment">
    Metorial discovers the server and creates its first version. In **Version Details**, wait for the status to show **Available** and **Current**. The deployment log should say that the MCP server deployment succeeded.

        <img alt="Successful remote MCP server deployment" src="__img3" />
  </Step>
</Steps>

<Callout type="info">
  Linking a server might not ask you to authenticate. If the server protects its tools,
  complete authentication when the connection flow asks for it.
</Callout>