| FMRS | 39 / 100 · D | 80 / 100 · B | 76 / 100 · B |
|---|
| Reliability | 4 / 20 | 14 / 20 | 13 / 20 |
|---|
| Security and permissions | 6 / 20 | 16 / 20 | 14 / 20 |
|---|
| Maintenance | 8 / 20 | 17 / 20 | 18 / 20 |
|---|
| Documentation | 9 / 20 | 15 / 20 | 17 / 20 |
|---|
| Setup experience | 12 / 20 | 18 / 20 | 14 / 20 |
|---|
| Best for | - Developers who want to manage Home Assistant from AI-powered IDEs like Cursor, VS Code, or Claude Code.
- Users who want to build and iterate on automations or dashboards using AI while retaining manual control.
- Those who need robust, predictable API access to Home Assistant rather than SSH or ad-hoc scripts.
| - Developers using fast-moving frameworks/libraries worried about the AI suggesting stale code
- Scenarios wanting zero-config documentation lookup
| - Teams that want an AI assistant to directly operate on GitHub repos and collaboration workflows
- Users already in the GitHub Copilot ecosystem who want a zero-deployment remote option
|
|---|
| Not for | - Users who do not want to install the HA Vibecode Agent add-on or do not want extra custom components inside Home Assistant.
- Users who need direct REST API or WebSocket access to Home Assistant without the intermediary agent.
- Beginners who are not comfortable installing Node.js locally or using MCP protocol.
| - Looking up internal/private codebase documentation (Context7 targets publicly published open-source libraries)
- Cases needing very high coverage of obscure, niche libraries (coverage depends on what Context7's platform has indexed)
| - Scenarios where you don't want the assistant to have write access to repos (enable only read-only toolsets)
- Environments with strict network isolation for private repos that can't reach the official remote endpoint
|
|---|
| Required permissions | - Requires access to the local file system (to run Node.js and npx).
- Requires network access to the Home Assistant agent's port (usually 8099).
- Requires environment variables HA_AGENT_URL and HA_AGENT_KEY for authentication.
- The agent itself uses Home Assistant's SUPERVISOR_TOKEN to access internal APIs.
| - Usable without an API key (subject to a free-tier rate limit); CONTEXT7_API_KEY is an optional credential for higher quota
- Read-only documentation lookup — no code execution or local filesystem access involved
| - A personal access token (PAT) or OAuth App token; effective scope depends on the token's own permissions
- Enabling toolsets like actions/issues/pull_requests grants write access — request tokens on a least-privilege basis
|
|---|
| Risks and side effects | - Storing the Agent Key in mcp.json may be leaked if committed to git.
- AI-generated actions may modify or delete configurations, potentially causing data loss, though Git versioning mitigates this.
- Relies on a custom agent running inside Home Assistant, which could introduce security vulnerabilities if exposed.
- May inadvertently affect production environments if not configured carefully.
| - The free tier has limited quota — high-frequency use may hit rate limits
- Documentation content comes from Context7's platform index, so its accuracy and freshness depend on that platform's crawl cadence
| - Write toolsets (creating/merging PRs, triggering workflows) can cause accidental changes if the token is overscoped — try a read-only toolset first
- In hosted mode, credentials travel via the Authorization header — make sure the client-to-api.githubcopilot.com connection is trusted
|
|---|
| Supported clients | Claude Desktop, Cursor, VS Code | Claude Code, VS Code, Cursor, Cline, Amp | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, JetBrains, Zed, Amp |
|---|
| Tools | 7 | 2 | 15 |
|---|