From bdbd4132a0d8a7a2abcbd95945281961c642b744 Mon Sep 17 00:00:00 2001 From: cybermanhao <324677869@qq.com> Date: Mon, 16 Jun 2025 22:25:23 +0800 Subject: [PATCH 1/2] merge from main --- plugin-tutorial/faq/venv-not-same-path/venv-not-same-path.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/plugin-tutorial/faq/venv-not-same-path/venv-not-same-path.md b/plugin-tutorial/faq/venv-not-same-path/venv-not-same-path.md index 92160ba..53cc616 100644 --- a/plugin-tutorial/faq/venv-not-same-path/venv-not-same-path.md +++ b/plugin-tutorial/faq/venv-not-same-path/venv-not-same-path.md @@ -10,13 +10,13 @@ 在连接选项中,您需要调整执行目录到虚拟环境所在的位置: -![MCP 连接选项界面](image-2.png) +![MCP 连接选项界面](./image-2.png) ### 2. 修改执行命令 同时,需要相应地修改执行命令: -![修改执行命令示例](image.png) +![修改执行命令示例](./image.png) ### 3. 直接指定解释器路径 From 9284c1c1b76885bfc818719da3c924c12c9103ec Mon Sep 17 00:00:00 2001 From: cybermanhao <324677869@qq.com> Date: Mon, 16 Jun 2025 22:58:20 +0800 Subject: [PATCH 2/2] =?UTF-8?q?=E8=A7=84=E8=8C=83=E5=8C=96=E5=9B=BE?= =?UTF-8?q?=E7=89=87=E8=B7=AF=E5=BE=84=E4=B8=8E=E5=91=BD=E5=90=8D?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- plugin-tutorial/faq/help.md | 2 +- .../image.png => images/after-path-changed.png} | Bin .../image-2.png => images/before-path-changed.png} | Bin .../{venv-not-same-path => }/venv-not-same-path.md | 4 ++-- 4 files changed, 3 insertions(+), 3 deletions(-) rename plugin-tutorial/faq/{venv-not-same-path/image.png => images/after-path-changed.png} (100%) rename plugin-tutorial/faq/{venv-not-same-path/image-2.png => images/before-path-changed.png} (100%) rename plugin-tutorial/faq/{venv-not-same-path => }/venv-not-same-path.md (88%) diff --git a/plugin-tutorial/faq/help.md b/plugin-tutorial/faq/help.md index 6878a2c..fee8a28 100644 --- a/plugin-tutorial/faq/help.md +++ b/plugin-tutorial/faq/help.md @@ -13,7 +13,7 @@ MCP connection failure can have multiple causes. Here are some common situations A mismatch between the virtual environment (venv) and the entry file path is one of the common reasons for connection failure. -For detailed solutions, please refer to: [Configuration Guide](./venv-not-same-path/venv-not-same-path.md) +For detailed solutions, please refer to: [Configuration Guide](./venv-not-same-path.md) --- diff --git a/plugin-tutorial/faq/venv-not-same-path/image.png b/plugin-tutorial/faq/images/after-path-changed.png similarity index 100% rename from plugin-tutorial/faq/venv-not-same-path/image.png rename to plugin-tutorial/faq/images/after-path-changed.png diff --git a/plugin-tutorial/faq/venv-not-same-path/image-2.png b/plugin-tutorial/faq/images/before-path-changed.png similarity index 100% rename from plugin-tutorial/faq/venv-not-same-path/image-2.png rename to plugin-tutorial/faq/images/before-path-changed.png diff --git a/plugin-tutorial/faq/venv-not-same-path/venv-not-same-path.md b/plugin-tutorial/faq/venv-not-same-path.md similarity index 88% rename from plugin-tutorial/faq/venv-not-same-path/venv-not-same-path.md rename to plugin-tutorial/faq/venv-not-same-path.md index 7ab3bb5..0e57a26 100644 --- a/plugin-tutorial/faq/venv-not-same-path/venv-not-same-path.md +++ b/plugin-tutorial/faq/venv-not-same-path.md @@ -10,13 +10,13 @@ When using OpenMCP, you may sometimes encounter situations where the virtual env In the connection options, you need to set the execution directory to where the virtual environment is located: -![MCP Connection Options Interface](./image-2.png) +![MCP Connection Options Interface](./images/before-path-changed.png) ### 2. Modify the Execution Command At the same time, adjust the execution command accordingly: -![Example of Modified Execution Command](./image.png) +![Example of Modified Execution Command](./images/after-path-changed.png) ### 3. Directly Specify the Interpreter Path