chore: Relabel menu and items (#2175)

* relabeling

* continue relabeling

* fmt

* integrations to connections

* Update terminology from "gateway" to "Assistant" across documentation and codebase for consistency

* rewording

Author: tlgimenes

apps/docs/client/src/content/en/mcp-mesh/api-reference.mdx

@@ -21,7 +21,7 @@ Proxies MCP requests to a single upstream connection.
 ### Gateway (virtual server)
 
 - `POST /mcp/gateway/:gatewayId`
-- `POST /mcp/gateway` (default gateway; requires `x-org-id` or `x-org-slug`)
+- `POST /mcp/gateway` (default Hub; requires `x-org-id` or `x-org-slug`)
 
 Aggregates tools/resources/prompts across multiple connections.
 

apps/docs/client/src/content/en/mcp-mesh/concepts.mdx

@@ -9,8 +9,8 @@ icon: BookOpen
 - **Organization**: the top-level tenant boundary. Everything (connections, gateways, logs) is org-scoped.
 - **Members**: users invited into an organization.
 - **Roles**: role assignments for members, used by access control checks.
-- **MCP Server (Connection)**: a configured upstream MCP endpoint (usually HTTP), optionally with stored credentials.
-- **Gateway**: a virtual MCP server that aggregates multiple connections into a single MCP surface.
+- **Connection**: a configured upstream MCP endpoint (usually HTTP), optionally with stored credentials.
+- **Hub**: a virtual MCP server that aggregates multiple connections into a single MCP surface.
 - **Tool call**: a `tools/call` request routed through the Mesh to a downstream MCP server (or via a gateway).
 - **Monitoring log**: a record of a tool call (inputs, outputs, duration, error), used for debugging and ops.
 
@@ -25,7 +25,7 @@ icon: BookOpen
 2. The client calls either:
    - the **Management MCP** (admin tools), or
    - a **Proxy endpoint** (one connection), or
-   - a **Gateway endpoint** (aggregated tools/resources/prompts).
-3. The Mesh authorizes, loads credentials, proxies to the downstream MCP server(s), and logs monitoring events.
+   - a **Hub endpoint** (aggregated tools/resources/prompts).
+3. The Mesh authorizes, loads credentials, proxies to the downstream Connection(s), and logs monitoring events.
 
 

apps/docs/client/src/content/en/mcp-mesh/connect-clients.mdx

@@ -17,10 +17,10 @@ There are two common ways to connect clients to the Mesh:
 
 - **Management MCP**: `POST /mcp`
 - **Connection proxy**: `POST /mcp/:connectionId`
-- **Gateway (virtual server)**: `POST /mcp/gateway/:gatewayId` (or omit `:gatewayId` to use the org default gateway with headers)
+- **Hub (virtual server)**: `POST /mcp/gateway/:gatewayId` (or omit `:gatewayId` to use the org default Hub with headers)
 
 <Callout type="tip">
-  If your goal is a “single MCP URL” for a curated tool surface, use **Gateways**. If you want a direct pipe to one upstream MCP, use **Connection proxy**.
+  If your goal is a "single MCP URL" for a curated tool surface, use **Hubs**. If you want a direct pipe to one upstream MCP, use **Connection proxy**.
 </Callout>
 
 ## Authentication quick notes

apps/docs/client/src/content/en/mcp-mesh/mcp-gateways.mdx

@@ -1,26 +1,26 @@
 ---
-title: MCP Gateways
+title: Hubs
 description: Publish a virtual MCP server that aggregates tools/resources/prompts from multiple connections
 icon: Waypoints
 ---
 
 import Callout from "../../../components/ui/Callout.astro";
 
-## What is a gateway?
+## What is a Hub?
 
-An **MCP Gateway** is a **virtual MCP server** that aggregates multiple connections into a single MCP surface:
+A **Hub** is a **virtual MCP server** that aggregates multiple connections into a single MCP surface:
 
 - tools (`tools/list`, `tools/call`)
 - resources (`resources/list`, `resources/read`)
 - prompts (`prompts/list`, `prompts/get`)
 
-This is how you create a curated endpoint for clients without exposing every tool from every connected server.
+This is how you create a curated endpoint for clients without exposing every tool from every connected integration.
 
 ## Endpoint
 
 - `POST /mcp/gateway/:gatewayId`
 
-You can also omit `:gatewayId` and rely on the organization’s default gateway by providing one of these headers:
+You can also omit `:gatewayId` and rely on the organization's default Hub by providing one of these headers:
 
 - `x-org-id`, or
 - `x-org-slug`
@@ -32,7 +32,7 @@ You can also omit `:gatewayId` and rely on the organization’s default gateway
 
 ## Tool exposure strategies
 
-Gateways also control **how tools are exposed** to clients (useful when tool surfaces get large).
+Hubs also control **how tools are exposed** to clients (useful when tool surfaces get large).
 These strategies ship by default:
 
 ### Passthrough (baseline)
@@ -56,14 +56,14 @@ These strategies ship by default:
   - `GATEWAY_RUN_CODE` (run JS in a sandbox that can call tools)
 - Goal: reduce tool exposure overhead on large surfaces by shifting work into a constrained runtime.
 
-## The default gateway (auto-created per org)
+## The default Hub (auto-created per org)
 
-Every new organization gets a **Default Gateway**:
+Every new organization gets a **Default Hub**:
 
 - **Strategy**: `passthrough`
 - **Mode**: `exclusion`
 - **Default exclusions**: the built-in **Mesh MCP** connection (management tools) and the **Store/Registry** connection are excluded by default
-- **Default behavior**: everything else in the org is included — so as you connect MCP servers, this endpoint becomes the “all tools in the org” gateway
+- **Default behavior**: everything else in the org is included — so as you connect Integrations, this endpoint becomes the "all tools in the org" Hub
 
 This is the endpoint most teams use as the single aggregated MCP surface for an org.
 

apps/docs/client/src/content/en/mcp-mesh/mcp-servers.mdx

@@ -1,5 +1,5 @@
 ---
-title: MCP Servers
+title: Connections
 description: Register upstream MCP servers, store credentials, and proxy requests securely
 icon: Server
 ---
@@ -8,14 +8,14 @@ import Callout from "../../../components/ui/Callout.astro";
 
 ## What is a connection?
 
-An **MCP Server** in the Mesh is a configured upstream MCP endpoint (typically HTTP). The Mesh stores its configuration and (optionally) credentials, and can then proxy MCP requests to it.
+A **Connection** in the Mesh is a configured upstream MCP endpoint (typically HTTP). The Mesh stores its configuration and (optionally) credentials, and can then proxy MCP requests to it.
 
 ## In the UI
 
-Go to **MCP Servers** to:
+Go to **Connections** to:
 
-- browse connected servers
-- add a new server (**Connect MCP Server**)
+- browse connected connections
+- create a new connection (**Create Connection**)
 - search and manage existing connections
 
 ## Proxying to a single connection
@@ -33,7 +33,7 @@ The Mesh will:
 5. log a monitoring event
 
 <Callout type="info">
-  If you need a single aggregated endpoint for multiple servers, use [MCP Gateways](/en/mcp-mesh/mcp-gateways) instead.
+  If you need a single aggregated endpoint for multiple connections, use [Hubs](/en/mcp-mesh/mcp-gateways) instead.
 </Callout>
 
 

apps/docs/client/src/content/en/mcp-mesh/overview.mdx

@@ -42,9 +42,9 @@ The Mesh centralizes these concerns once, so you can operate MCP traffic like an
 
 ## Product surfaces (what you can do today)
 
-- **Store**: browse a catalog of MCP servers you can connect to (default: the official MCP Registry).
-- **MCP Servers**: connect and manage MCP servers (HTTP MCP endpoints).
-- **MCP Gateways**: publish a curated “virtual MCP server” that aggregates tools/resources/prompts from multiple connections.
+- **Store**: browse a catalog of Connections you can connect to (default: the official MCP Registry).
+- **Connections**: connect and manage MCP servers (HTTP MCP endpoints).
+- **Hubs**: publish a curated "virtual MCP server" that aggregates tools/resources/prompts from multiple connections.
 - **API Keys**: create scoped keys with explicit tool permissions.
 - **Members & Roles**: invite teammates and manage roles + permissions.
 - **Monitoring**: tool-call logs, errors, latency, filtering, and streaming.

apps/docs/client/src/content/en/mcp-mesh/quickstart.mdx

@@ -1,6 +1,6 @@
 ---
 title: Quickstart
-description: Run Mesh locally, connect an MCP server, create a gateway, and verify monitoring
+description: Run Mesh locally, connect an Integration, create a Hub, and verify monitoring
 icon: Rocket
 ---
 
@@ -71,25 +71,25 @@ The application will be available at `http://localhost:8080`.
 
 **More details:** [Kubernetes: Helm Chart](/en/mcp-mesh/deploy/kubernetes-helm-chart)
 
-## 2) Connect an MCP server
+## 2) Create a Connection
 
 When you open a new organization, the Mesh will prompt you to:
 
 - **Browse Store** or
-- **Connect MCP Server** directly - provide the MCP URL (HTTP endpoint) and any required credentials
+- **Create Connection** directly - provide the MCP URL (HTTP endpoint) and any required credentials
 
-The **Store** is a catalog of MCP servers you can connect to. By default, the Store points to the **official MCP Registry**.
+The **Store** is a catalog of Connections you can connect to. By default, the Store points to the **official MCP Registry**.
 
 ## 3) Create an organization and invite members
 
 - Go to **Members**
 - Invite teammates
 - Assign roles (Admin/User) as needed
 
-## 4) Create an MCP Gateway (virtual server)
+## 4) Create a Hub (virtual server)
 
-- Go to **MCP Gateways**
-- Click **Create MCP Gateway**
+- Go to **Hubs**
+- Click **Create Hub**
 - Choose **Include** (only selected connections/tools) or **Exclude** (everything except the exclusions)
 
 ## 5) Generate an API key for a client

apps/docs/client/src/content/pt-br/mcp-mesh/concepts.mdx

@@ -9,8 +9,8 @@ icon: BookOpen
 - **Organization**: limite de tenancy. Tudo (connections, gateways, logs) é escopado por organização.
 - **Members**: pessoas dentro da organização.
 - **Roles**: papéis dentro da org (usados para permissões).
-- **MCP Server (Connection)**: um endpoint MCP upstream configurado (normalmente HTTP), com credenciais no vault quando necessário.
-- **Gateway**: um “MCP virtual” que agrega múltiplas connections em um único endpoint.
+- **Conexão**: um endpoint MCP upstream configurado (normalmente HTTP), com credenciais no vault quando necessário.
+- **Hub**: um "MCP virtual" que agrega múltiplas connections em um único endpoint.
 - **Tool call**: uma requisição `tools/call` roteada pelo Mesh para uma connection (ou via gateway).
 - **Monitoring log**: registro de tool call (inputs/outputs, duração, erro) para debug e operação.
 
@@ -25,7 +25,7 @@ icon: BookOpen
 2. O cliente chama um endpoint:
    - **Management MCP** (admin tools), ou
    - **Proxy** (uma connection), ou
-   - **Gateway** (agregação).
-3. O Mesh autoriza, carrega credenciais, faz proxy para o MCP upstream e registra monitoring.
+   - **Hub** (agregação).
+3. O Mesh autoriza, carrega credenciais, faz proxy para a Conexão upstream e registra monitoring.
 
 

apps/docs/client/src/content/pt-br/mcp-mesh/connect-clients.mdx

@@ -13,21 +13,21 @@ Para um client falar com o Mesh, ele precisa de:
 
 ## Recomendações práticas
 
-- Use um **Gateway** como endpoint principal do seu time (ele vira o “surface” curado/estável).
-- Comece com poucas connections e um gateway simples; aumente a curadoria conforme o número de tools crescer.
+- Use um **Hub** como endpoint principal do seu time (ele vira o "surface" curado/estável).
+- Comece com poucas connections e um Hub simples; aumente a curadoria conforme o número de tools crescer.
 
 ## Onde encontrar os endpoints
 
 No Mesh, você encontra:
 
-- **Gateways** → URL do gateway (o endpoint recomendado para clients)
-- **Connections / MCP Servers** → URL de proxy da connection (útil para debug/isolamento)
+- **Hubs** → URL do Hub (o endpoint recomendado para clients)
+- **Connections / Conexões** → URL de proxy da connection (útil para debug/isolamento)
 
 ## Dica: debug rápido
 
 Se uma tool falhar, use:
 
 - **Monitoring** para ver o erro e o payload, e
-- execute novamente via gateway vs connection para confirmar se o problema é de agregação ou do upstream.
+- execute novamente via Hub vs connection para confirmar se o problema é de agregação ou do upstream.
 
 

apps/docs/client/src/content/pt-br/mcp-mesh/mcp-gateways.mdx

@@ -1,16 +1,16 @@
 ---
-title: MCP Gateways
-description: Gateways agregam e curam tools de múltiplas connections em um único endpoint MCP
+title: Hubs
+description: Hubs agregam e curam tools de múltiplas connections em um único endpoint MCP
 icon: Share2
 ---
 
-## O que é um Gateway?
+## O que é um Hub?
 
-Um **MCP Gateway** é um “MCP virtual”: ele expõe um único endpoint MCP que agrega tools/resources/prompts de múltiplas **connections**.
+Um **Hub** é um "MCP virtual": ele expõe um único endpoint MCP que agrega tools/resources/prompts de múltiplas **connections**.
 
 ## Estratégias de exposição de tools
 
-Gateways também controlam **como as tools são expostas** (útil quando o surface cresce).
+Hubs também controlam **como as tools são expostas** (útil quando o surface cresce).
 Essas estratégias vêm por padrão:
 
 ### Passthrough (baseline)
@@ -34,14 +34,14 @@ Essas estratégias vêm por padrão:
   - **GATEWAY_RUN_CODE** (executa JS em um sandbox que pode chamar tools)
 - Objetivo: reduzir overhead de exposição em superfícies grandes movendo parte do trabalho para um runtime controlado.
 
-## O Default Gateway (criado automaticamente por org)
+## O Default Hub (criado automaticamente por org)
 
-Toda organização nova recebe um **Default Gateway**:
+Toda organização nova recebe um **Default Hub**:
 
 - **Strategy**: `passthrough`
 - **Mode**: `exclusion`
 - **Exclusões padrão**: a connection interna **Mesh MCP** (tools de administração) e a connection da **Store/Registry** são excluídas por padrão
-- **Comportamento**: todo o resto entra automaticamente — então, conforme você conecta MCP servers, esse endpoint vira o gateway “com todas as tools da org”
+- **Comportamento**: todo o resto entra automaticamente — então, conforme você conecta Conexões, esse endpoint vira o Hub "com todas as tools da org"
 
 Esse é o endpoint que muitos times usam como a superfície MCP principal da organização.