Phoenix MCP
Provides scoped, least-privilege access to Home Assistant entities, with per-client tokens, capabilities, rate limits, optional expiry, built-in auditing, instant token revocation, a per-entity semantic safety layer (MESA), and a catalog of 131 tools for reading, controlling, and authoring Home Assistant configuration.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Phoenix MCPTurn off the living room lights and set the thermostat to 68."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Phoenix MCP
Phoenix MCP gives your AI agents scoped, least-privilege access to Home Assistant. Each client gets its own token, limited to exactly the entities you allow, with its own capabilities, rate limit, and optional expiry. Auditing is enabled by default and configurable per outcome, any token can be revoked instantly, and the per-entity semantic safety layer (MESA) can make a device confirm-only or off-limits by its nature, no matter what permissions a token is granted.
Phoenix MCP runs entirely inside Home Assistant, with no extra process, no cloud dependency in the core server, and no setup beyond the Phoenix MCP panel (the optional Agent Chat, voice, and AI Task features send conversations to the model provider you configure, unless you point them at a local Ollama). It works with the MCP clients you already use (Claude Code, Cursor, ChatGPT/Codex, Gemini, and others), or you can skip installing a client altogether and chat from inside Home Assistant itself. Either way, a guided setup takes you from a new token to a working agent in minutes, backed by a catalog of 148 tools for reading, controlling, and authoring your configuration. The panel is available in English, Simplified Chinese, and Japanese, following your Home Assistant profile language by default.
Documentation
The full documentation, including the tool reference, permissions, capabilities, MESA, and the admin API, is at leecaochang.github.io/phoenix-mcp. The panel's help links point there.
New here? Start with the Quick start: it creates your first token, grants it one device, then lets you choose whether to chat from inside Home Assistant or connect an external agent, in a few minutes either way.
Related MCP server: Home Assistant MCP Server
Requirements
Home Assistant 2025.2.0 or later.
One Phoenix MCP instance per Home Assistant. No Python dependencies beyond what HA ships.
Install via HACS
In HACS, open Integrations, then the top-right menu, and choose Custom repositories.
Enter
https://github.com/leecaochang/phoenix-mcpand select Integration as the category, then click Add.Find Phoenix MCP in the HACS integration list, install it, and restart Home Assistant.
Prefer to install by hand? Copy the custom_components/phoenix_mcp folder into your Home Assistant config directory under custom_components/phoenix_mcp, then restart.
Set up
Go to Settings > Devices & services > Add integration and search for Phoenix MCP. Click through the single-step config flow, then open the Phoenix MCP panel in your sidebar. The Quick start takes it from there.
Issues and feedback
Report issues at github.com/leecaochang/phoenix-mcp/issues.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseBqualityDmaintenanceProvides tools for AI assistants to interact with smart home devices through Home Assistant, allowing operations like checking entity states and calling services.31073MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to control and monitor Home Assistant smart home devices through natural language interactions. Supports device control, entity state monitoring, history access, and automation generation with both MCP protocol and standalone HTTP REST API modes.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Home Assistant smart home devices through natural language. Control devices, manage automations, query entity states, and retrieve historical data across your home automation system.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with Home Assistant to control smart home devices, query entity states, and manage automations using natural language. It provides over 90 tools for comprehensive system management, including dashboard configuration, service execution, and automation debugging.MIT
Related MCP Connectors
SaaS intelligence for AI agents. 5 unified tools cover 1,000+ services with 91-96% token savings.
Runtime permission, approval, and audit layer for AI agent tool execution.
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/leecaochang/phoenix-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server