From de7958e79af8801cf6a3e51258ba21da2e30f672 Mon Sep 17 00:00:00 2001 From: Allen Porter Date: Thu, 17 Jul 2025 22:20:20 -0700 Subject: [PATCH] Remove a known limitation for MCP Server (#40051) Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- source/_integrations/mcp_server.markdown | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/source/_integrations/mcp_server.markdown b/source/_integrations/mcp_server.markdown index 034f5cbeacf..937b44650c5 100644 --- a/source/_integrations/mcp_server.markdown +++ b/source/_integrations/mcp_server.markdown @@ -16,7 +16,7 @@ related: ha_quality_scale: silver --- -The [Model Context Protocol](https://modelcontextprotocol.io) is an open protocol that standardizes how applications provide context to LLMs. The **Model Context Protocol Server** (MCP) integration enables using Home Assistant to provide context for MCP LLM Client Applications. For example, you can expose your Google Tasks To-do list as a tool for Claude Desktop. +The [Model Context Protocol](https://modelcontextprotocol.io) is an open protocol that standardizes how applications provide context to LLMs. The **Model Context Protocol Server** (MCP) integration enables using Home Assistant to provide context for MCP LLM Client Applications. For example, you can control your lights from Claude Desktop, or expose your Google Tasks to-do list as a tool. Controlling Home Assistant is done by providing MCP clients access to the Assist API of Home Assistant. You can control what devices and entities it can access from the {% my voice_assistants title="exposed entities page" %}. @@ -186,7 +186,6 @@ subset of MCP features: | Sampling | ❌ | | Notifications | ❌ | -Home Assistant does not yet provide built-in tools that can fetch device state. ## Troubleshooting