docs: Rename mock-user-svc to mock-server

Author: iFurySt

docs/configuration/gateways.md

@@ -5,11 +5,11 @@
 以下是一个完整的配置示例，包含了路由、CORS、响应处理等配置：
 
 ```yaml
-name: "mock-user-svc"                 # 代理服务名称，全局唯一
+name: "mock-server"              # 代理服务名称，全局唯一
 
 # 路由配置
 routers:
-  - server: "mock-user-svc"     # 服务名称
+  - server: "mock-server"       # 服务名称
     prefix: "/mcp/user"         # 路由前缀，全局唯一，不可重复，建议按照服务或者领域+模块来区分前缀
 
     # CORS 配置
@@ -30,7 +30,7 @@ routers:
 
 # 服务配置
 servers:
-  - name: "mock-user-svc"             # 服务名称，需要与routers中的server保持一致
+  - name: "mock-server"               # 服务名称，需要与routers中的server保持一致
     namespace: "user-service"         # 服务命名空间，用于服务分组
     description: "Mock User Service"  # 服务描述
     allowedTools:                     # 允许使用的工具列表（为tools的子集）
@@ -203,7 +203,7 @@ tools:
 
 ```yaml
 routers:
-  - server: "mock-user-svc"     # 服务名称，需要与servers中的name保持一致
+  - server: "mock-server"       # 服务名称，需要与servers中的name保持一致
     prefix: "/mcp/user"         # 路由前缀，全局唯一，不可重复
 ```
 
@@ -242,7 +242,7 @@ cors:
 
 ```yaml
 servers:
-  - name: "mock-user-svc"             # 服务名称，需要与routers中的server保持一致
+  - name: "mock-server"               # 服务名称，需要与routers中的server保持一致
     namespace: "user-service"         # 服务命名空间，用于服务分组
     description: "Mock User Service"  # 服务描述
     allowedTools:                     # 允许使用的工具列表（为tools的子集）
@@ -488,7 +488,7 @@ args:
 2. 文件存储：
     - 每个配置单独存储为一个 YAML 文件
     - 类似 Nginx 的 vhost 配置方式
-    - 文件名建议使用服务名称，如 `mock-user-svc.yaml`
+    - 文件名建议使用服务名称，如 `mock-server.yaml`
 
 ## MCP 服务代理配置
 

docs/deployment/docker.md

@@ -41,9 +41,9 @@ docker pull ghcr.io/mcp-ecosystem/mcp-gateway/mcp-gateway:latest
 docker pull registry.ap-southeast-1.aliyuncs.com/mcp-ecosystem/mcp-gateway-mcp-gateway:latest
 
 # Mock User Service
-docker pull docker.io/ifuryst/mcp-gateway-mock-user-svc:latest
-docker pull ghcr.io/mcp-ecosystem/mcp-gateway/mock-user-svc:latest
-docker pull registry.ap-southeast-1.aliyuncs.com/mcp-ecosystem/mcp-gateway-mock-user-svc:latest
+docker pull docker.io/ifuryst/mcp-gateway-mock-server:latest
+docker pull ghcr.io/mcp-ecosystem/mcp-gateway/mock-server:latest
+docker pull registry.ap-southeast-1.aliyuncs.com/mcp-ecosystem/mcp-gateway-mock-server:latest
 
 # Web 前端
 docker pull docker.io/ifuryst/mcp-gateway-web:latest

docs/development/local-development.md

@@ -17,7 +17,7 @@ MCP Gateway 项目由以下几个核心组件组成：
 
 1. **apiserver** - 提供配置管理、用户接口等 API 服务
 2. **mcp-gateway** - 核心网关服务，处理 MCP 协议转换
-3. **mock-user-svc** - 模拟用户服务，用于开发测试
+3. **mock-server** - 模拟用户服务，用于开发测试
 4. **web** - 管理界面前端
 
 ## 启动开发环境
@@ -78,13 +78,13 @@ go run cmd/apiserver/main.go
 
 apiserver 默认会在 `http://localhost:5234` 上启动。
 
-#### 4.3 启动 mock-user-svc
+#### 4.3 启动 mock-server
 
 ```bash
-go run cmd/mock-user-svc/main.go
+go run cmd/mock-server/main.go
 ```
 
-mock-user-svc 默认会在 `http://localhost:5235` 上启动。
+mock-server 默认会在 `http://localhost:5235` 上启动。
 
 #### 4.4 启动 web 前端
 

docs/getting-started/quick-start.md

@@ -73,7 +73,7 @@ docker run -d \
    - 使用配置的管理员账号密码登录
 
 2. 添加 MCP Server：
-   - 复制配置文件：https://github.com/mcp-ecosystem/mcp-gateway/blob/main/configs/mock-user-svc.yaml
+   - 复制配置文件：https://github.com/mcp-ecosystem/mcp-gateway/blob/main/configs/mock-server.yaml
    - 在 Web 界面上点击 "Add MCP Server"
    - 粘贴配置并保存
 

i18n/de/docusaurus-plugin-content-docs/current/configuration/gateways.md

@@ -5,11 +5,11 @@
 Nachfolgend finden Sie ein vollständiges Konfigurationsbeispiel, das Routing, CORS, Antwortverarbeitung und andere Einstellungen umfasst:
 
 ```yaml
-name: "mock-user-svc"                 # Proxy-Dienstname, global eindeutig
+name: "mock-server"             # Proxy-Dienstname, global eindeutig
 
 # Router-Konfiguration
 routers:
-  - server: "mock-user-svc"     # Dienstname
+  - server: "mock-server"       # Dienstname
     prefix: "/mcp/user"         # Routenpräfix, global eindeutig, kann nicht wiederholt werden, empfohlen zur Unterscheidung nach Dienst oder Domäne+Modul
 
     # CORS-Konfiguration
@@ -44,7 +44,7 @@ Die Router-Konfiguration wird verwendet, um Anfrageweiterleitungsregeln zu defin
 
 ```yaml
 routers:
-  - server: "mock-user-svc"     # Dienstname, muss mit dem Namen in servers übereinstimmen
+  - server: "mock-server"       # Dienstname, muss mit dem Namen in servers übereinstimmen
     prefix: "/mcp/user"         # Routenpräfix, global eindeutig, kann nicht wiederholt werden
 ```
 

i18n/de/docusaurus-plugin-content-docs/current/deployment/docker.md

@@ -41,9 +41,9 @@ docker pull ghcr.io/mcp-ecosystem/mcp-gateway/mcp-gateway:latest
 docker pull registry.ap-southeast-1.aliyuncs.com/mcp-ecosystem/mcp-gateway-mcp-gateway:latest
 
 # Mock-Benutzerdienst
-docker pull docker.io/ifuryst/mcp-gateway-mock-user-svc:latest
-docker pull ghcr.io/mcp-ecosystem/mcp-gateway/mock-user-svc:latest
-docker pull registry.ap-southeast-1.aliyuncs.com/mcp-ecosystem/mcp-gateway-mock-user-svc:latest
+docker pull docker.io/ifuryst/mcp-gateway-mock-server:latest
+docker pull ghcr.io/mcp-ecosystem/mcp-gateway/mock-server:latest
+docker pull registry.ap-southeast-1.aliyuncs.com/mcp-ecosystem/mcp-gateway-mock-server:latest
 
 # Web-Frontend
 docker pull docker.io/ifuryst/mcp-gateway-web:latest

i18n/de/docusaurus-plugin-content-docs/current/development/local-development.md

@@ -17,7 +17,7 @@ Das MCP Gateway-Projekt besteht aus den folgenden Kernkomponenten:
 
 1. **apiserver** - Bietet Konfigurationsmanagement, Benutzeroberfläche und andere API-Dienste
 2. **mcp-gateway** - Kern-Gateway-Dienst, behandelt MCP-Protokollkonvertierung
-3. **mock-user-svc** - Simuliert Benutzerdienst für Entwicklungstests
+3. **mock-server** - Simuliert Benutzerdienst für Entwicklungstests
 4. **web** - Management-Interface-Frontend
 
 ## Starten der Entwicklungsumgebung
@@ -77,13 +77,13 @@ go run cmd/apiserver/main.go
 
 apiserver wird standardmäßig unter `http://localhost:5234` gestartet.
 
-#### 4.3 mock-user-svc starten
+#### 4.3 mock-server starten
 
 ```bash
-go run cmd/mock-user-svc/main.go
+go run cmd/mock-server/main.go
 ```
 
-mock-user-svc wird standardmäßig unter `http://localhost:5235` gestartet.
+mock-server wird standardmäßig unter `http://localhost:5235` gestartet.
 
 #### 4.4 Web-Frontend starten
 

i18n/de/docusaurus-plugin-content-docs/current/getting-started/quick-start.md

@@ -73,7 +73,7 @@ docker run -d \
    - Melden Sie sich mit den konfigurierten Administrator-Anmeldedaten an
 
 2. Neuen MCP-Server hinzufügen:
-   - Konfigurationsdatei kopieren: https://github.com/mcp-ecosystem/mcp-gateway/blob/main/configs/mock-user-svc.yaml
+   - Konfigurationsdatei kopieren: https://github.com/mcp-ecosystem/mcp-gateway/blob/main/configs/mock-server.yaml
    - In der Web-UI auf "Add MCP Server" klicken
    - Konfiguration einfügen und speichern
 

i18n/en/docusaurus-plugin-content-docs/current/configuration/gateways.md

@@ -5,11 +5,11 @@
 Below is a complete configuration example, including routing, CORS, response handling, and other settings:
 
 ```yaml
-name: "mock-user-svc"                 # Proxy service name, globally unique
+name: "mock-server"             # Proxy service name, globally unique
 
 # Router Configuration
 routers:
-  - server: "mock-user-svc"     # Service name
+  - server: "mock-server"       # Service name
     prefix: "/mcp/user"         # Route prefix, globally unique, cannot be repeated, recommended to distinguish by service or domain+module
 
     # CORS Configuration
@@ -30,7 +30,7 @@ routers:
 
 # Server Configuration
 servers:
-  - name: "mock-user-svc"             # Service name, must be consistent with the server in routers
+  - name: "mock-server"               # Service name, must be consistent with the server in routers
     namespace: "user-service"         # Service namespace, used for service grouping
     description: "Mock User Service"  # Service description
     allowedTools:                     # List of allowed tools (subset of tools)
@@ -203,7 +203,7 @@ Router configuration is used to define request forwarding rules:
 
 ```yaml
 routers:
-  - server: "mock-user-svc"     # Service name, must be consistent with the name in servers
+  - server: "mock-server"       # Service name, must be consistent with the name in servers
     prefix: "/mcp/user"         # Route prefix, globally unique, cannot be repeated
 ```
 
@@ -242,7 +242,7 @@ Server configuration is used to define service metadata, associated tool list, a
 
 ```yaml
 servers:
-  - name: "mock-user-svc"             # Service name, must be consistent with the server in routers
+  - name: "mock-server"               # Service name, must be consistent with the server in routers
     namespace: "user-service"         # Service namespace, used for service grouping
     description: "Mock User Service"  # Service description
     allowedTools:                     # List of allowed tools (subset of tools)
@@ -488,7 +488,7 @@ Gateway proxy configuration can be stored in the following two ways:
 2. File storage:
     - Each configuration is stored separately as a YAML file
     - Similar to Nginx's vhost configuration
-    - The file name is recommended to use the service name, such as `mock-user-svc.yaml`
+    - The file name is recommended to use the service name, such as `mock-server.yaml`
 
 ## MCP Service Proxy Configuration
 

i18n/en/docusaurus-plugin-content-docs/current/deployment/docker.md

@@ -41,9 +41,9 @@ docker pull ghcr.io/mcp-ecosystem/mcp-gateway/mcp-gateway:latest
 docker pull registry.ap-southeast-1.aliyuncs.com/mcp-ecosystem/mcp-gateway-mcp-gateway:latest
 
 # Mock User Service
-docker pull docker.io/ifuryst/mcp-gateway-mock-user-svc:latest
-docker pull ghcr.io/mcp-ecosystem/mcp-gateway/mock-user-svc:latest
-docker pull registry.ap-southeast-1.aliyuncs.com/mcp-ecosystem/mcp-gateway-mock-user-svc:latest
+docker pull docker.io/ifuryst/mcp-gateway-mock-server:latest
+docker pull ghcr.io/mcp-ecosystem/mcp-gateway/mock-server:latest
+docker pull registry.ap-southeast-1.aliyuncs.com/mcp-ecosystem/mcp-gateway-mock-server:latest
 
 # Web Frontend
 docker pull docker.io/ifuryst/mcp-gateway-web:latest