From 98b6a4f9d748db374c1651b9350d732c23ea3083 Mon Sep 17 00:00:00 2001 From: Allen Porter Date: Mon, 17 Mar 2025 14:38:45 -0700 Subject: [PATCH] Update MCP server Assist API documentation now that the stateless API is implicitly used (#38019) --- source/_integrations/mcp_server.markdown | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/source/_integrations/mcp_server.markdown b/source/_integrations/mcp_server.markdown index 95d031b5e83..d5ff3723b2e 100644 --- a/source/_integrations/mcp_server.markdown +++ b/source/_integrations/mcp_server.markdown @@ -35,10 +35,8 @@ The integration provides the following configuration options: {% configuration_basic %} Control Home Assistant: - description: The API to use to expose tools over the Model Context Protocol. It is recommended - to use **Stateless Assist** which is a version of the **Assist** API where the - prompt does not contain any state information. Clients can only control or - provide information about entities that are [exposed](/voice_control/voice_remote_expose_devices/) to it. + description: If MCP clients are allowed to control Home Assistant. Clients can only + control or provide information about entities that are [exposed](/voice_control/voice_remote_expose_devices/) to it. {% endconfiguration_basic %} ## Architecture overview @@ -132,11 +130,6 @@ The [MCP Prompts](https://modelcontextprotocol.io/docs/concepts/prompts) provide inform LLMs how to call the tools. The tools used by the configured LLM API are exposed. -It is recommended to use the **Stateless Assist** API since the prompt does -not contain any state information, which will be incorrect after any actions -are performed. - - ## Known Limitations The Home Assistant Model Context Protocol integration currently only supports a