Merge branch 'main' into caozhen/fix-arguments-replace-problem

Author: niechen

.github/workflows/deploy.yml

@@ -19,7 +19,7 @@ concurrency:
 
 jobs:
   validate:
-    uses: ./.github/workflows/validate-manifests.yml
+    uses: ./.github/workflows/test.yml
 
   build:
     runs-on: ubuntu-latest

.github/workflows/semantic-check.yml

@@ -0,0 +1,64 @@
+name: Semantic Version Check
+
+on:
+  pull_request_target:
+    types: [opened, synchronize, reopened]
+
+jobs:
+  semver-check:
+    name: Validate Semantic Version
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      pull-requests: write
+      issues: write
+    
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          ref: ${{ github.event.pull_request.head.sha }}
+          fetch-depth: 0
+          persist-credentials: false
+
+      - name: Install pnpm
+        uses: pnpm/action-setup@v4
+        with:
+          version: 8
+          run_install: false
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 'lts/*'
+          cache: 'pnpm'
+
+      - name: Install dependencies
+        run: pnpm install
+
+      - name: Check Release
+        uses: cycjimmy/semantic-release-action@v4
+        id: semantic
+        with:
+          dry_run: true
+          ci: true
+          extra_plugins: |
+            @semantic-release/commit-analyzer
+            @semantic-release/release-notes-generator
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Comment PR
+        uses: thollander/actions-comment-pull-request@v2
+        with:
+          message: |
+            ## Semantic Version Check
+            
+            ${{ steps.semantic.outputs.new_release_version && '✅ Valid semantic version changes detected!' || '⚠️ No semantic version changes detected.' }}
+            
+            ${{ steps.semantic.outputs.new_release_version && format('Next version will be: **{0}**', steps.semantic.outputs.new_release_version) || 'Please ensure your commits follow the [Conventional Commits](https://www.conventionalcommits.org/) format:
+
+            - `feat: new feature` (triggers MINOR version bump)
+            - `fix: bug fix` (triggers PATCH version bump)
+            - `BREAKING CHANGE: description` (triggers MAJOR version bump)' }}
+          comment_tag: semantic-version-check 

.github/workflows/semver-check.yml

@@ -1,7 +1,6 @@
 {
     "branches": [
-        "main",
-        "master"
+        "main"
     ],
     "plugins": [
         "@semantic-release/commit-analyzer",

.releaserc.json

@@ -1,3 +1,31 @@
+## [1.4.1](https://github.com/pathintegral-institute/mcpm.sh/compare/v1.4.0...v1.4.1) (2025-04-18)
+
+
+### Bug Fixes
+
+* update goose cli client name ([#77](https://github.com/pathintegral-institute/mcpm.sh/issues/77)) ([6b17d94](https://github.com/pathintegral-institute/mcpm.sh/commit/6b17d94f97cf0b4d01ad1f11e8b1abb169afc509))
+
+# [1.4.0](https://github.com/pathintegral-institute/mcpm.sh/compare/v1.3.0...v1.4.0) (2025-04-18)
+
+
+### Features
+
+* **router:** Improve function naming in router ([654872d](https://github.com/pathintegral-institute/mcpm.sh/commit/654872dec5d7588f115bab67a08ac2779e9383f3))
+
+# [1.3.0](https://github.com/pathintegral-institute/mcpm.sh/compare/v1.2.0...v1.3.0) (2025-04-18)
+
+
+### Features
+
+* add share for router ([#74](https://github.com/pathintegral-institute/mcpm.sh/issues/74)) ([e81a852](https://github.com/pathintegral-institute/mcpm.sh/commit/e81a85214f2287acea2b6b667a47a0e7d6f5e462))
+
+# [1.2.0](https://github.com/pathintegral-institute/mcpm.sh/compare/v1.1.2...v1.2.0) (2025-04-17)
+
+
+### Features
+
+* **command:** Add info command and simplify search output ([#73](https://github.com/pathintegral-institute/mcpm.sh/issues/73)) ([27a4443](https://github.com/pathintegral-institute/mcpm.sh/commit/27a44434c5afe72ee1ceec1b2ef2b6b6a1698f5f))
+
 ## [1.1.2](https://github.com/pathintegral-institute/mcpm.sh/compare/v1.1.1...v1.1.2) (2025-04-17)
 
 

CHANGELOG.md

@@ -152,11 +152,15 @@ The Router also maintains persistent connections to MCP servers, enabling multip
 
 For more technical details on the router's implementation and namespacing, see [`docs/router_tech_design.md`](docs/router_tech_design.md).
 
+The Router can be shared in public network by `mcpm router share`. Be aware that the share link will be exposed to the public, make sure the generated secret is secure and only share to trusted users. See [MCPM Router Share](docs/router_share.md) for more details about how it works.
+
 ```bash
 mcpm router status                # Check if the router daemon is running
 mcpm router on                    # Start the MCP router daemon
 mcpm router off                   # Stop the MCP router daemon
-mcpm set --host HOST --port PORT  # Set the MCP router daemon's host and port
+mcpm router set --host HOST --port PORT --address ADDRESS  # Set the MCP router daemon's host port and the remote share address
+mcpm router share                 # Share the router to public
+mcpm router unshare               # Unshare the router
 ```
 
 ### 🛠️ Utilities (`util`)

README.md

@@ -152,11 +152,15 @@ MCPM 路由器作为后台守护进程运行，充当稳定端点（例如 `http
 
 有关路由器实现和命名空间的更多技术细节，请参阅 [`docs/router_tech_design.md`](docs/router_tech_design.md)。
 
+Router可以通过命令`mcpm router share`来将router分享到公网。注意确保生成的密钥没有暴露，并只分享给可信用户。有关分享的更多细节，请参阅[分享](docs/router_share.md)。
+
 ```bash
 mcpm router status                # 检查路由器守护进程是否正在运行
 mcpm router on                    # 启动 MCP 路由器守护进程
 mcpm router off                   # 停止 MCP 路由器守护进程
-mcpm set --host HOST --port PORT  # 设置 MCP 路由器守护进程的主机和端口
+mcpm router set --host HOST --port PORT --address ADDRESS  # 设置 MCP 路由器守护进程的主机,端口和分享的远程服务器
+mcpm router share                 # 将router分享到公网
+mcpm router unshare               # 取消分享
 ```
 
 ### 🛠️ 实用工具 (`util`)

README.zh-CN.md

@@ -0,0 +1,46 @@
+
+# MCPM Router Share
+
+## Introduction
+Your local MCPM Router can be shared in public network and others can connect to your router by the share link and use your configured MCPM Profile. In this document, we will explain how to use it and how it works.
+
+## Create a share link
+
+```bash
+mcpm router share
+mcpm router share --profile <PROFILE_NAME> --address <ADDRESS>
+```
+There will be a share link and a secret. The final share link will be `http://<ADDRESS>?s=<SECRET>&profile=<PROFILE_NAME>`. You can share this link with others and by adding this share link to mcpm client, they can connect to your router.
+
+If address is not specified, the share link will be proxied by our server `share.mcpm.sh`. You can also specify a custom address to share.
+
+If profile is not specified, the share link will use the current active profile. If no active profile found, the user need to specify the profile manually.
+
+To be noted that if your router is not on or your system sleeps, the shared link will not be accessible.
+
+## How it works
+
+We use a fork version of frp from [huggingface/frp](https://github.com/huggingface/frp) to create a tunnel to your local MCPM Router. You can also check the [original frp](https://github.com/fatedier/frp) for more details about frp.
+
+If you want to set up your own frp tunnel, you can either build our docker image from scratch or use our published docker images for frps(server) and frpc(client) by following the instructions below.
+
+In your public server, you can create a frps config following the guide [here](https://github.com/huggingface/frp?tab=readme-ov-file#setting-up-a-share-server). Then start the frps container by:
+```bash
+docker run -d --name frps -p 7000:7000 -p 7001:7001 -v /path/to/frps.ini:/frp/frps.ini ghcr.io/pathintegral-institute/frps:latest
+```
+
+Then you can share the router with your own frp server by specifying the address:
+```bash
+mcpm router share --address <YOUR_ADDRESS>
+```
+
+## Authentication
+There will be a secret token generated for authentication. The user MUST specify the secret token as a query parameter `s=<SECRET>` when connecting to your router. Make sure to keep the secret token secure and only share it with trusted users.
+
+## Unshare
+
+```bash
+mcpm router unshare
+```
+
+This will stop the tunnel and remove the share link.

docs/router_share.md

@@ -35,7 +35,8 @@
         "type": {
           "type": "string",
           "enum": [
-            "git"
+            "git",
+            "npm"
           ]
         },
         "url": {