docs(TSP-1439): document custom MCP servers on Connectors page

integrations/mcp/mcp-client.mdx

@@ -4,7 +4,7 @@
 description: "Connect external MCP servers to your Relevance AI Agents, giving them access to Tools and resources from other services."
 ---
 
-The MCP client integration lets you connect remote MCP servers to your Relevance AI Agents — either through preset connections (Notion, Canva, Atlassian) or by manually connecting any custom server URL. This gives your Agents access to Tools and resources hosted on external platforms without rebuilding them in Relevance AI.
+The MCP client integration lets you connect remote MCP servers to your Relevance AI Agents — either through preset connections (Notion, Canva, Atlassian) or by manually connecting any custom server URL. This gives your Agents access to Tools and resources hosted on external platforms without rebuilding them in Relevance AI. Custom MCP servers you've connected to your project appear in a **Custom** category on the Connectors page, so you can discover and manage them without navigating into each Agent's Tools tab.
 
 <Warning>
   This page is about connecting external MCP servers **to** Relevance AI Agents. If you want to use Relevance AI **from** an AI client like Claude or Cursor, see [MCP & Plugins](/get-started/core-concepts/mcp-plugins).
@@ -42,6 +42,14 @@
 
 <Warning>Local MCP server support (e.g. JSON configuration) is not available.</Warning>
 
+## Managing custom MCP servers from the Connectors page
+
+Custom MCP servers you've connected to your project appear in a **Custom** category on the Connectors page. Each server shows as a card with the server's hostname as a subtitle. Click any card to open the server's configuration for editing. To connect a new custom MCP server directly from the Connectors page without opening an Agent, click the **Add custom MCP** action card.
+
+<Note>
+  The Custom category on the Connectors page is currently rolling out. If you don't see it yet, use the Tools tab path described above.
+</Note>
+
 ## Connecting multiple instances of the same MCP server
 
 You can connect the same MCP server URL multiple times within a project. Each connection operates independently with its own authentication credentials, label, and configuration. Tools from each connection display `(MCP: connection-name)` in their descriptions so Agents can distinguish which connection a Tool belongs to.

integrations/mcp/mcp-server.mdx

@@ -15,7 +15,7 @@
 <Tip>For Claude Code, we recommend using the [Relevance AI plugin](/integrations/mcp/claude-code) instead of a manual MCP connection — it includes built-in skills and context that make the experience significantly better.</Tip>
 
 <Warning>
-  This page is about using Relevance AI **from** external AI clients. If you want to connect an external MCP server **to** a Relevance AI agent, see [MCP Client](/integrations/mcp/mcp-client).
+  This page is about using Relevance AI **from** external AI clients. If you want to connect an external MCP server **to** a Relevance AI agent — or manage your custom MCP connections from the Connectors page — see [MCP Client](/integrations/mcp/mcp-client).
 </Warning>
 
 ---
@@ -39,7 +39,7 @@
   </Accordion>
 
   <Accordion title="ChatGPT" icon="comment">
     ChatGPT supports MCP servers through Developer Mode, available on Pro, Team, Enterprise, and Edu plans.
 
     1. Open ChatGPT **Settings**
     2. Go to **Connectors** → **Advanced** → **Developer Mode**