From ae1f66928b0391b696102d3dbdd2529574acdd4a Mon Sep 17 00:00:00 2001 From: Ben Lambert Date: Tue, 16 Sep 2025 11:18:10 +0200 Subject: [PATCH] Apply suggestion from @freben MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Fredrik Adelöw Signed-off-by: Ben Lambert --- plugins/mcp-actions-backend/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugins/mcp-actions-backend/README.md b/plugins/mcp-actions-backend/README.md index 99e364a8ce..4b4dad153b 100644 --- a/plugins/mcp-actions-backend/README.md +++ b/plugins/mcp-actions-backend/README.md @@ -108,7 +108,7 @@ Set the `MCP_TOKEN` environment variable with this token, and configure your MCP > [!CAUTION] > This is highly experimental, proceed with caution. -You can configure both the `auth-backend` and install the `auth` frontend plugin in order to enable [Dynamic Client Registration](https://modelcontextprotocol.io/specification/2025-03-26/basic/authorization#dynamic-client-registration) with MCP Clients. +You can configure the `auth-backend` and install the `auth` frontend plugin in order to enable [Dynamic Client Registration](https://modelcontextprotocol.io/specification/2025-03-26/basic/authorization#dynamic-client-registration) with MCP Clients. This means that there is no token required in your MCP settings, and a token will be given to a client that requests a token on your behalf. When adding the MCP server to an MCP client like Cursor or Claude, a popup that requires your approval will be opened in your Backstage instance, which is powered by the `auth` plugin.