From 7d0ee56db1ee8e09598fda98f1db219a4902d245 Mon Sep 17 00:00:00 2001 From: maliming Date: Tue, 11 Aug 2026 17:07:14 +0800 Subject: [PATCH] Add the default condition to the generated VS Code configuration --- docs/en/studio/model-context-protocol.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/studio/model-context-protocol.md b/docs/en/studio/model-context-protocol.md index c74e09d3e0..17a25ccb2c 100644 --- a/docs/en/studio/model-context-protocol.md +++ b/docs/en/studio/model-context-protocol.md @@ -83,7 +83,7 @@ You can run `abp help mcp-studio` at any time to see the available options and t ### Generating Config Files from ABP Studio -The `app`, `app-nolayers` and `microservice` templates already contain a `.vscode/mcp.json` file, so a solution created from one of them works with VS Code without any extra configuration. +By default, the `app`, `app-nolayers` and `microservice` templates create a `.vscode/mcp.json` file, so a solution created from one of them works with VS Code without any extra configuration. > The endpoint is not authenticated. It only listens on `localhost`, but any local process can call it, and a connected client can read the monitoring data, build the solution, run the configured tasks and start or stop applications and containers. Only configure MCP clients you trust, and do not forward or expose the endpoint.